dsh-open-in
从 DSH Web 图形界面在可配置的启动器中打开工作区目录（VS Code / 文件资源管理器 / Windows Terminal / 任意命令行界面）。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-open-in@0.2.0Open In 以 dsh-open-in 发布，当前版本为 0.2.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
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", …).
targets array — each target has id, label,
command, args, an optional platforms allowlist and an enabled
switch. Shipped defaults: vscode, explorer, terminal.open on macOS / xdg-open on Linux; terminal → wt -d /
open -a Terminal / gnome-terminal --working-directory). Any explicit
customization is authoritative.0.1.2-rc.1 or newer (web profile).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.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.2.0.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
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.
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.
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
| Key | Default | Meaning |
|---|---|---|
targets[].id | — | Stable 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[].command | per target | Executable that opens a directory, resolved through PATH. |
targets[].args | per target | Extra arguments passed before the directory path. |
targets[].platforms | [] | Platform allowlist (win32/darwin/linux); empty = every platform. |
targets[].enabled | true | Disabled 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).
| Action | Where | Approval |
|---|---|---|
| Open a workspace directory in a configured launcher | Host (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.
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.
MIT