Introduction

DeepSeek Harness (DSH) provides a Web-based interactive interface for managing workspaces and agents. In real-world development, developers often need to jump directly from the Web interface to the local development environment, such as opening a project directory in an editor or navigating to that directory in a terminal.

The dsh-open-in plugin solves this pain point. It does not require building any tools on the DSH side; instead, it acts as an integration layer that invokes locally installed launchers (such as VS Code, Windows Terminal, or File Explorer) through the Web interface.

What It Is

dsh-open-in is a DSH plugin developed by maintainer NevermindZZT.

It does not provide new agent capabilities or tools. Its only responsibility is: when you have already opened a workspace in the DSH Web interface, it allows you to launch external programs directly from the sidebar menu using your configured command-line arguments, passing the current workspace directory to those programs.

Core Features

The plugin has the following capabilities:

  1. Configurable targets
    You can add, edit, or remove targets in Settings. Each target contains a unique identifier, display label, execution command, argument list, and platform restrictions. Configuration can be saved in persisted user settings, and deployment-level overrides can also be provided via cordis.yml.
  2. Menu integration
    The plugin automatically adds an overflow menu to each actual “workspace” row in the DSH Web interface. Menu items are generated based on the targets you have configured (for example, “Open in VS Code” or “Open in File Explorer”).
  3. Automatic platform adaptation
    Built-in targets (such as explorer and terminal) automatically adapt to the host platform. For example, on Windows they may invoke wt -d, while on macOS they invoke open -a Terminal. You can also manually override the default behavior.
  4. Host program launch
    The plugin launches the configured executable on the host in detached mode. It only sends the target ID and directory path; the host program decides how to handle that path.
  5. No build required
    The plugin includes precompiled library files, so no build step is required after installation.

Installation and Enablement

Installing this plugin requires DSH version 0.1.2-rc.1 or later, and you must use the Web Profile.

Run the following command to add the plugin to your Web Profile:

dsh plugin --profile web add dsh-open-in

After installation is complete, refresh the Web interface. The plugin will be mounted as dsh-open-in. You can verify that the plugin loaded correctly with the following command:

dsh --profile web --dump-config | grep dsh-open-in

Typical Usage

After configuring the plugin, the workflow is as follows:

  1. Find the opened workspace in the Web interface sidebar.
  2. Click the … overflow menu on the right side of that workspace row.
  3. Select the configured target (for example, “Open in VS Code”).
  4. The host program launches immediately and opens that workspace directory as the working directory.

Configure targets in the settings interface:
* Go to Settings → Plugins.
* Find the “Open In” card.
* Add, modify, or remove target rows in the card, then click Save to apply the changes.

Use Cases and Notes

  • Tool dependencies: You must install and configure the tools you want to invoke on your system, and their executables (such as the code command for VS Code CLI and the wt command for Windows Terminal) must be available in the system PATH.
  • Path restrictions: The plugin rejects relative paths and only accepts absolute paths.
  • Permissions and security: The plugin only runs the commands you explicitly configured. It does not provide any tools, skills, or model-visible surface. It acts solely as a host process launcher and directly responds to clicks in the Web interface (without secondary approval).
  • Configuration overrides: Changes made in the settings interface override the default configuration in cordis.yml.

Conclusion

dsh-open-in reflects DSH’s “everything is a plugin” philosophy. Through a minimal approach, it seamlessly connects the Web interface with the local development environment, reducing the tedious operations of copying paths and manually opening applications.

For more information, see the DeepSeek Harness plugin directory or the GitHub repository.