Introduction

When managing multiple workspaces via the Web interface in DeepSeek Harness (DSH), the common practice is to note down the directory path and then switch to a terminal or file manager to manually open the editor. This step can easily disrupt the workflow, especially with long paths or numerous workspaces.

The dsh-open-in-vscode plugin described below integrates this step directly into the sidebar: an additional item is added to the overflow menu (…) of each workspace row. Clicking it opens the corresponding directory in your local VS Code (or the configured editor CLI). The plugin is maintained by the community contributor omdsh-dev, categorized as a client-side plugin, and has approximately 54 stars and 6 forks on GitHub.

What It Is

dsh-open-in-vscode is a client + host combination plugin for DSH: the Web interface handles displaying the menu item, while the DSH host process invokes the local editor command.

It addresses the transition issue of “jumping from the Web GUI to the local IDE.” It does not introduce new tools, skills, or model-callable settings, nor does it read or write workspace files themselves.

Core Functionality

Sidebar Menu Entry

The plugin primarily uses the sidebar.workspaces.row-menu extension slot provided by DSH. On the public DSH version 0.1.0-rc.6, if the native slot is unavailable, it falls back to a compatibility adapter layer. The menu items rendered via both paths are identical and follow the interface language:

  • Chinese environment: 在 VSCode 中打开 (Open in VSCode)
  • English environment: Open in VSCode

Invocation Chain After Click

After the user clicks the menu item, the client closes the menu and calls openInVscode/open via TypeRoot Remote, passing the current workspace directory to the host. The host then launches the configured editor CLI (default: code <path>) in a detached manner, ensuring the editor process remains independent of the DSH service.

Capability Boundaries

Operation Execution Location Approval Required
Open workspace directory after user click Host (triggered by user gesture) No
Others — The plugin has no tools, no settings namespace, and no model-facing interfaces

Prerequisites

  1. VS Code installed locally, or an editor CLI on the PATH capable of opening directories. The default code command on Windows detects common installation paths; on macOS, you must first install the VS Code shell command or configure it to use another executable.
  2. DSH version 0.1.0-rc.6 or newer. Native workspace row menu extension points are supported from version 0.1.0-rc.6 onwards; earlier versions are not supported by the plugin.

Installation and Enabling

Add the plugin in the Web profile (this executes pnpm within the profile and coordinates 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

Restart the Web service (send kill -TERM <pid> to the process and wait for it to exit—do not use kill -9 to avoid interrupting session zstd logs), then refresh the page. The host plugin mounts under dsh-open-in-vscode, and the client bundle is provided by /plugins/dsh-open-in-vscode/client.js.

Confirm the installed version:

dsh plugin --profile web list dsh-open-in-vscode --depth 0

The current release version is v0.1.6, with the MIT license.

Configuration

You can adjust the following fields in cordis.yml:

Key Default Value Description
command code The executable used to open the directory. On Windows, it probes standard VS Code installation locations by default; other commands are resolved via PATH.
args [] Additional arguments passed before the directory path.

If the executable does not exist, the plugin will clearly report an error and provide a fix prompt; relative paths are rejected.

Typical Usage

After completing the installation and restart steps above, open the DSH Web interface, locate the target workspace in the sidebar, click the … on the right side of that row, and select 在 VSCode 中打开 (or Open in VSCode in the English interface). Your local VS Code should launch and open the workspace directory.

If you use compatible CLIs like Cursor or VSCodium, you can change command in cordis.yml to the corresponding executable name and, if necessary, pass additional arguments via args.

Applicable Scenarios and Notes

Who It’s For

  • Developers who frequently switch workspaces in the DSH Web interface and prefer continuing edits in their local IDE.
  • Teams looking to reduce repetitive operations of “copy path → terminal code.”

Before Use, Please Note

  • The plugin runs with the current DSH host process user permissions; it’s recommended to review the GitHub source code and MIT license before installation to ensure its behavior aligns with your deployment policy.
  • The plugin only opens workspace directories already visible in DSH; it does not provide file read/write, remote execution, or other automation capabilities.
  • The DSH ecosystem follows an “everything is a plugin” philosophy; the SkillHub Directory Page is a community-maintained site and has no official affiliation with DeepSeek or High-Flyer.

Links

  • Directory page: https://www.skillhub.cn/plugins/omdsh-dev/dsh-open-in-vscode
  • GitHub: https://github.com/omdsh-dev/dsh-open-in-vscode