dsh-open-in-vscode: Open Workspace Directories in VS Code from the DeepSeek Harness Web GUI
omdsh-dev/dsh-open-in-vscode
Open DeepSeek Harness workspace directories in VS Code directly from the web GUI.
This DSH plugin adds an "Open in VSCode" menu item to every workspace row in the sidebar, saving you the hassle of switching to a local editor manually.
dsh plugin --profile web add github:omdsh-dev/dsh-open-in-vscode- Category
- Development & Operations
- Platform
- DSH-Plugin
- Author
- omdsh-dev
- Distribution
- Plugin
dsh-open-in-vscode Key Features
dsh-open-in-vscode Repository
dsh-open-in-vscode Repo Summary
dsh-open-in-vscode is a development and engineering plugin (DSH plugin) for DeepSeek Harness (DSH) that lets you open workspace directories in VS Code directly from the DSH web GUI. It solves the hassle of manually switching to a local editor to open a directory when managing multiple workspaces in the browser. By adding an "Open in VSCode" menu item (shown as "在 VSCode 中打开" under the Chinese locale) to every real workspace row in the sidebar, a single click invokes your local VS Code or a configured editor to open that directory. Maintained by omdsh-dev under the MIT license, with the latest update in 2026-08, it currently has 45 stars and 5 forks, making it a lightweight and focused utility.
What core features does the dsh-open-in-vscode DSH plugin support?
The plugin's core feature is a menu item that opens a workspace directory in VS Code. It uses the harness's sidebar.workspaces.row-menu slot when available, and falls back to a scoped compatibility adapter on the public DSH 0.1.0-rc.6 build. Both paths render the same locale-following menu row: "在 VSCode 中打开" under Chinese, "Open in VSCode" under English. Clicking the row closes the menu and calls the host over the strict Typert Remote openInVscode/open, passing the workspace directory. The host half spawns the configured editor CLI on that directory (code <path> by default), detached, so the editor outlives the server.
How do I install the dsh-open-in-vscode DSH plugin?
To install, add the plugin to your web profile. The following command runs pnpm inside the profile and reconciles the bundle layer:
dsh plugin --profile web add https://github.com/omdsh-dev/dsh-open-in-vscode/archive/refs/tags/v0.1.6.tar.gz
After installation, restart the web server (kill -TERM <pid> and wait for exit — never kill -9, as it tears the session zstd log mid-frame), then refresh the page. The host plugin mounts under dsh-open-in-vscode; the client bundle is served at /plugins/dsh-open-in-vscode/client.js. Confirm the installed version with:
dsh plugin --profile web list dsh-open-in-vscode --depth 0
What configuration options does dsh-open-in-vscode have?
The plugin offers two configurable fields, changeable from cordis.yml: command (default code) specifies the executable that opens a directory; the default also probes standard Windows VS Code install locations, while other commands resolve through PATH. args (default []) specifies extra arguments passed before the directory path. A missing executable fails loud with a fix hint; relative paths are refused.
What is the capability boundary of dsh-open-in-vscode?
The plugin does exactly one thing: open a workspace directory in the editor. It adds no tools, no skills, and no settings, and it never reads or writes files itself. The action runs on the host (user gesture) and requires no approval because the user clicked the row. Beyond that, the plugin has no other capabilities.
What about development and licensing of dsh-open-in-vscode?
For development, run pnpm install and pnpm run check (typecheck + lint + test + build; commit lib/ since file: installs run without a build). The layout has the wire contract in one module (src/contract.ts) shared by the host manifest (src/typert.ts) and the client contribution (src/client/remote.ts). The plugin is licensed under MIT.