MIT VS Code extension that embeds the DSH web UI, manages the `dsh web` lifecycle, relays DSH's token auth on loopback, and bridges editor actions into the panel.
DSH integration
Native runtime
Author-claimed
Safety audit
Unaudited
Last verified
2026-11-20
License
MIT
01What can it help you accomplish?
Talk to the DeepSeek Harness agent beside your code instead of in a terminal or a browser tab
The full DSH web UI embedded in the left sidebar or the right secondary side bar, with the service started or reused for you
VS Code users who spend the day in the editor and do not want another window for the agent
Keep DSH's mandatory browser sign-in working inside a cross-site webview
The one-time launch URL exchanged for a 30-day session cookie and served through a loopback relay, so the iframe is not stuck on a login page or a 401
Anyone on DSH 0.1.2 or newer whose embedded panel would otherwise ask for a sign-in it cannot complete itself
Make the embedded DSH page behave like an editor citizen instead of a trapped iframe
Clickable file paths, external links in the system browser, working copy buttons, restored undo/redo, and image fallback for models without vision
Developers who click file paths, copy code blocks and paste screenshots out of the agent panel all day
02How to install into DeepSeek Harness
Prerequisites
- The `dsh` CLI on your PATH — installed from DeepSeek Harness — or DSH Desktop on Windows
- VS Code ≥ 1.91, from the README's development requirements; Node.js ≥ 22 is only needed to build the extension from source
Installation steps
- 01
Install from the Marketplace: `code --install-extension Fengze233.dsh-vscode-panel`
- 02
Or download the latest `dsh-vscode.vsix` from Releases, run `Extensions: Install from VSIX...` in VS Code, then reload the window
- 03
Click the DSH whale in the left Activity Bar or the right Secondary Side Bar — the extension starts (or reuses) `dsh web` and signs the panel in
$ dsh web
Verify the integration
- The status bar shows the live service state: running / starting / stopping / failed / stopped
- `DSH: Show Logs` prints the detected `dsh` path, its source and version
- Bridge check: the DSH panel DevTools console should print `[dsh-vscode-bridge] handshake ok, v0.4.4, imageFallback=true`
Rollback
- Uninstall the extension: VS Code runs its `uninstall` hook, which removes the marked `cordis.patch.yml` entry and the bridge directory
- Or run `DSH: Uninstall Bridge` to remove the bridge package and restore `cordis.patch.yml` while keeping the extension
03DSH integration and capability boundaries
Wraps the official `dsh web` service in a VS Code webview: owns the service lifecycle, relays DSH's one-time-token auth on loopback, and installs its `dsh-vscode-bridge` client plugin into the DSH profile
Service lifecycle management
`dsh.profile`, `dsh.port`, `dsh.launchPreference` (`auto` / `npm` / `desktop`) and `dsh.autoStart`→a reused or newly started `dsh web`, with a temporary switch to the first free port when the configured port is taken
closing the last window stops only the service the extension started itselfAuth relay
the one-time launch URL printed by `dsh web`→a session cookie kept in extension private storage and served to the iframe through a loopback relay on a random `127.0.0.1` port
the relay holds a 30-day session, so any local process that finds the random port can drive that sessiona service started outside VS Code needs one paste of its launch URLBridge into the embedded DSH page
the DSH user profile under `$DSH_HOME/profiles/<dsh.profile>` (default `~/.dsh/profiles/web`)→file jumps, external links in the system browser, clipboard copy, undo/redo and image fallback inside the panel
writes a marked `# dsh-vscode-bridge: begin/end` block into `cordis.patch.yml` and a bridge directory in the user profile — never into the DSH installationforce-reinstalls whenever the bundled version or its `client.js` content differsImage fallback for non-vision models
an attached image plus an open workspace folder→the image cached under the workspace root and sent as a file-path reference the model can read with an image tool
temporary images are deleted after use; leftovers are purged by `DSH: Clean Up Image Cache`Remote scenarios
`dsh.remote.enabled` plus the extension installed on the remote host→SSH Remote, Dev Containers and Codespaces run `dsh` on the remote and tunnel the panel; WSL needs no tunnel
04Who is it for? When not to use it?
Good for
- VS Code users who spend the day in the editor and do not want another window for the agent
- Anyone on DSH 0.1.2 or newer whose embedded panel would otherwise ask for a sign-in it cannot complete itself
- Developers who click file paths, copy code blocks and paste screenshots out of the agent panel all day
Not for
- The loopback relay listens on `127.0.0.1` only, but it holds a 30-day session: any local process — including another local user — that finds the random port can drive that DSH session. The README states this exposure and compares it to an unauthenticated DSH ≤ 0.1.1 service on `127.0.0.1:3080`.
- DSH Desktop runs the `desktop` profile while VS Code uses `web` by default: sessions and settings are shared under `~/.dsh`, but plugins are installed per profile, so DSH plugins must be installed into the `web` profile to appear in the VS Code panel.
- If the model API is only reachable through an HTTP/HTTPS proxy, the proxy variables must reach the `dsh web` child process — set `dsh.useEnvProxy: true`, or inject `NODE_OPTIONS=--use-env-proxy` together with `HTTPS_PROXY` / `HTTP_PROXY` through `dsh.env`.
05Compatibility, maintenance and safety notes
- The loopback relay listens on `127.0.0.1` only, but it holds a 30-day session: any local process — including another local user — that finds the random port can drive that DSH session. The README states this exposure and compares it to an unauthenticated DSH ≤ 0.1.1 service on `127.0.0.1:3080`.
- DSH Desktop runs the `desktop` profile while VS Code uses `web` by default: sessions and settings are shared under `~/.dsh`, but plugins are installed per profile, so DSH plugins must be installed into the `web` profile to appear in the VS Code panel.
- If the model API is only reachable through an HTTP/HTTPS proxy, the proxy variables must reach the `dsh web` child process — set `dsh.useEnvProxy: true`, or inject `NODE_OPTIONS=--use-env-proxy` together with `HTTPS_PROXY` / `HTTP_PROXY` through `dsh.env`.
- Two documented gaps: dragging resources from the VS Code Explorer no longer reaches the webview since VS Code 1.140 (upstream regression, fix still open), and image fallback needs an open workspace folder because files are cached under the workspace root. Remote SSH / Dev Containers / Codespaces also stay off until `dsh.remote.enabled` is turned on.
MIT · actively maintained (latest release V0.4.4, 2026-11-08)
06Frequently asked questions
How do I get DSH into VS Code?
Install `Fengze233.dsh-vscode-panel` from the Marketplace or run `code --install-extension Fengze233.dsh-vscode-panel`; a `.vsix` from Releases works through `Extensions: Install from VSIX...`. The prerequisite is the `dsh` CLI on your PATH, or DSH Desktop on Windows. Then click the DSH whale in the Activity Bar — the extension starts or reuses `dsh web` and signs in for you.
Why does the panel show a login page or a 401?
DSH 0.1.2 introduced mandatory browser authentication. For a service the extension started itself, sign-in is automatic. If you started DSH outside VS Code (systemd, a terminal), the extension cannot read that log, so it shows a one-time sign-in page: paste the launch URL from that service's log once and the session lasts up to 30 days — a restart does not require pasting again.
It says dsh not found — what now?
Install the `dsh` CLI (`npm i -g @deepseek-ai/dsh`) or DSH Desktop and make sure the command is on PATH. With `dsh.launchPreference: auto` the extension prefers npm and falls back to Desktop; if Desktop lives in a custom directory set `dsh.desktopCommandPath`, and for wrapper scripts set `dsh.executablePath`. `DSH: Copy Logs` prints the detected path, source and version.
My DSH plugins don't appear in the VS Code panel — why?
DSH Desktop uses the `desktop` profile while VS Code uses `web` by default. Sessions and settings are shared under `~/.dsh`, but plugins are installed per profile, so install the plugin into the `web` profile (or point `dsh.profile` at the profile you want to use).
Does this expose my DSH session to the network?
No. The extension only accepts loopback addresses (`127.0.0.1` / `localhost` / `[::1]`) and the relay is not exposed to the network. The README does note that the relay holds a 30-day session, so any local process that finds its random port could drive that session — the same exposure as an unauthenticated DSH ≤ 0.1.1 service on loopback.
07Related DSH workflows
ds-harness-remote
by liguobao
Lets authorized desktop, web, and Android clients operate a remote Harness host.
dsh-windows-mcp
by hellohub1212
Windows desktop automation for DeepSeek Harness: the in-box MCP client bridge mounted against CursorTouch/Windows-MCP, with an off-by-default Computer Use switch and an in-app dependency installer.
dsh-desktop
by anywhere-labs
Modern desktop client for the DeepSeek Harness (dsh) plugin ecosystem. Everything is a plugin — even the desktop shell itself.
dsh-go
by ccch1mneyyy
Run DeepSeek Harness on your phone and remotely control your desktop from a native Android app.
08Data and sources
Click the whale and get the full DSH web UI beside your code — the extension starts or reuses `dsh web`, handles DSH's o…
Works with **DSH 0.1.2 and newer**, including its browser authentication (auto sign-in, no manual step).
**Install / uninstall transparency.** The bridge is installed into `$DSH_HOME/profiles/<dsh.profile>` (default `~/.dsh/p…
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-11-20. Found an error? Submit a correction.
Best DeepSeek Harness Plugins
Twelve plugins worth installing first — picked from the whole catalog, across every category.
