DeepSeek Harness plugin

dsh-open-in

Open a workspace directory from the DSH web GUI in a configurable launcher (VS Code / file explorer / Windows Terminal / any CLI).

Jump to install

Source facts

Repository
NevermindZZT/dsh-open-in
Latest update
Aug 20, 2026
Category
Development & Runtime
GitHub stars
0
Format
plugin
Catalog evidence
Upstream dsh.bundle evidence
Evidence path
package.json#dsh.bundle
Checked against
0.1.0-rc.8
Upstream check date
2026-08-20

This evidence comes from the upstream catalog. This site has not installed, run, or security-reviewed the plugin.

Install

Start with a prompt that asks an agent to review the GitHub repository and source. Switch to the command if you want to install it yourself.

Copy this prompt into DSH, Codex, or another agent and ask it to review the GitHub repository and source first.

Do not install or run any commands yet. Read this plugin's GitHub repository, README, and relevant source code. Then answer the questions below clearly and directly so I can decide whether it fits my needs:

1. What is this plugin, and what problem does it solve?
2. Who is it for, and what are its typical use cases?
3. How is it used after installation? Include one minimal example.
4. What known limitations or privacy, security, compatibility, or maintenance risks does it have?
5. Give a clear recommendation: recommend, conditionally recommend, or do not recommend, with reasons.

Distinguish statements documented by the repository, inferences from source code, and unknowns. If evidence is insufficient, say so explicitly. Do not guess or simply repeat the README.

GitHub: https://github.com/NevermindZZT/dsh-open-in
Plugin: dsh-open-in
Author: NevermindZZT

Check the source files

Read the README and other files from this plugin directory before installing.

File explorer3 files
README.mdSource · read only

dsh-open-in

!version !license ![GitHub](https://github.com/nevermindzzt/dsh-open-in)

Open a DeepSeek Harness workspace directory in a launcher of your choice — VS Code, File Explorer, Windows Terminal, or any command-line tool you configure — directly from the web GUI. Every real Workspace row in the sidebar gets an overflow menu entry per configured target ("Open in VS Code", "Open in File Explorer", "Open in Terminal", …).

Features

  • Configurable targets: a targets array — each target has id, label,

command, args, an optional platforms allowlist and an enabled switch. Shipped defaults: vscode, explorer, terminal.

  • Settings UI (add / edit / remove): Settings → Plugins → the "Open In"

card edits the targets with a structured form — add a row, change any field, remove a row, Save. Edits write the durable user settings document and apply to the next launch immediately (no restart).

  • Per-platform mapping for built-ins: while a built-in target keeps its

default command line, it follows the host platform automatically (explorer → open on macOS / xdg-open on Linux; terminal → wt -d / open -a Terminal / gnome-terminal --working-directory). Any explicit customization is authoritative.

  • Menu integration, both runtimes: newer DSH runtimes use the native

sidebar.workspaces.row-menu slot; the published 0.1.0-rc.6 (which lacks that slot) is served by a compatibility DOM adapter. Both paths render locale-following rows (中文 / English).

  • Host launch: the configured executable is spawned detached with the

directory as the last argument; the launcher outlives the server. Relative paths are refused, and only configured commands ever run (the client only sends a target id + path).

Prerequisites

  • DSH 0.1.0-rc.6 or newer (web profile).
  • The tools you configure must be installed: VS Code CLI (code) on PATH,

wt (Windows Terminal) on PATH, etc. The Windows default code command also searches the standard per-user/system VS Code install locations.

Install

Add the plugin to your web profile (runs pnpm inside the profile and reconciles the bundle layer). From the npm registry:

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

Or directly from GitHub:

dsh plugin --profile web add github:NevermindZZT/dsh-open-in

Or pin a release tag:

dsh plugin --profile web add https://github.com/NevermindZZT/dsh-open-in/archive/refs/tags/v0.1.1.tar.gz

All paths ship the prebuilt lib/, so git/tarball installs need no build step and no build approval. Restart the web server, then refresh the page. The host plugin mounts as dsh-open-in; the client bundle is served at /plugins/dsh-open-in/client.js.

Verify the layer composed:

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

Configure

Two layers compose the effective targets (highest wins): the user settings document (written by the Settings UI) → the cordis.yml entry (see below) → schema defaults. The Settings card is the recommended path for day-to-day changes; cordis.yml stays the deployment-composition path.

Settings UI

Open Settings → Plugins → "Open In" (the card sits in the configurable plugins tab). Rows mirror the current targets: edit any field, remove a row, or Add target for a new one. Fields: id (unique, non-empty), label (empty = built-in copy), command (executable), args (comma/space separated), platforms (comma/space separated win32/darwin/linux; empty = all), enabled. Invalid rows (empty/duplicate id, empty command) block the Save; Save writes the whole list to the durable settings document and applies immediately.

cordis.yml

Deployment-varying options are validated Config fields editable in cordis.yml (your profile's cordis.patch.yml). Because a patch replaces a row's whole config value, spell out every key you customize:

- update:
    - id: dsh-open-in
      config:
        targets:
          - id: vscode
            label: ''
            command: code
            args: []
            platforms: []
            enabled: true
          - id: explorer
            label: ''
            command: explorer
            args: []
            platforms: []
            enabled: true
          - id: terminal
            label: ''
            command: wt
            args: ['-d']
            platforms: []
            enabled: true
          - id: cursor
            label: 'Cursor'
            command: cursor
            args: []
            platforms: []
            enabled: true
KeyDefaultMeaning
targets[].idStable id; the client references targets by id (must be unique).
targets[].label''Menu label; empty falls back to the target.<id> locale key, then the id.
targets[].commandper targetExecutable that opens a directory, resolved through PATH.
targets[].argsper targetExtra arguments passed before the directory path.
targets[].platforms[]Platform allowlist (win32/darwin/linux); empty = every platform.
targets[].enabledtrueDisabled targets are never listed or launched.

A missing executable fails loud with a fix hint; relative paths are rejected. Targets edited in the Settings UI override the cordis.yml entry entirely (the settings user layer replaces the targets field).

Capability boundary

ActionWhereApproval
Open a workspace directory in a configured launcherHost (user gesture)No — the user clicked the row

The plugin contributes no tools, no skills, and no model-visible surface; it only launches programs the user configured on directories the user already opened in DSH.

Development

pnpm install
pnpm run check   # typecheck + test + build

The prebuilt lib/ is committed; a release only needs a version bump, a build, and a tag.

License

MIT