The design philosophy of DeepSeek Harness (DSH) is “everything is a plugin.” When an agent handles code tasks, it often needs to open the current workspace or a specified path in an editor. Manually switching windows is inefficient. This plugin provides a slash command that directly addresses this need.
What is this¶
This is a client plugin maintained by foxi-ui. Its function is to execute the /vscode command in a DeepSeek Harness conversation, automatically calling the VS Code CLI to open the workspace directory of the current session or any specified path.
Core features¶
- Command
/vscode: Opens the current session workspace. - Command
/vscode <path>: Opens a specified directory (supports spaces). - Automatic VS Code CLI detection: Priority order is environment variables →
PATH→ common installation paths. - macOS fallback: If the CLI is not found, uses
open -a "Visual Studio Code". - Zero runtime dependencies: Uses only Node’s built-in
child_process.execFile, with no shell invocation. - Cross-platform support: Supports macOS / Windows / Linux.
Installation and enabling¶
Prerequisites: dsh plugin works through pnpm, so please make sure pnpm is installed first.
Install command:
dsh plugin --profile web add @foxi-ai/dsh-command-vscode
The plugin declares dsh.bundle; after installation with dsh plugin, it is automatically added to dsh.profile.bundles and activated. It can be used after restarting dsh.
Typical usage¶
Open the current workspace:
/vscode
Open a specified path:
/vscode /path/to/project
/vscode "/path/with spaces"
Customize the VS Code executable path:
export VSCODE_CLI=/path/to/code
Use cases and notes¶
This plugin is suitable for developers who frequently interact with a local code editor during conversations. Before installing, please check the source code and license (MIT). The plugin runs with the permissions of the current dsh process, so ensure the environment is secure.
Short conclusion¶
After the steps above, you can seamlessly integrate DeepSeek Harness with VS Code using a single slash command. For more details, refer to the GitHub repository or community directory.