Dsh Open In Vscode

dsh plugin --profile my-profile add github:omdsh-dev/dsh-open-in-vscode

This bundle is not on npm, so it installs straight from git. Its build output is already committed to the repository (or it needs no build at all), so it loads without a build step.

# 1. add the bundle to a profile — --profile my-profile points at $DSH_HOME/profiles/my-profile
dsh plugin --profile my-profile add github:omdsh-dev/dsh-open-in-vscode

# 2. verify: the bundle should show up as a layer in the resolved config
dsh --profile my-profile --dump-config

# 3. boot the profile
dsh --profile my-profile

Pin a commit — github:omdsh-dev/dsh-open-in-vscode#<commit-sha> — if you want the code you reviewed to be the code you keep getting.

Prerequisites

API key

Not required.

Network access

Not required at runtime.

Language

JavaScript — a git install pulls this source, not build output.

Verdict reason

git-only but needs no build

package.json read

package.json

Rules applied from

docs/user/develop/basic/publish.md

Checked at

2026-08-15

Open a workspace directory in VS Code straight from the DeepSeek Harness web GUI: every real Workspace row in the sidebar gains an **Open in VSCode** row inside its **…** overflow menu. - The client half 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 the Chinese locale, **Open in VSCode** under English. - The row's click 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 ` by default), detached, so the editor outlives the server. - VS Code, or an editor CLI on