DeepSeek Harness(dsh) for VS Code

English · 简体中文

A Cursor-like AI coding experience inside VS Code — powered by your own DeepSeek Harness (DSH) agent.

Embeds the full DSH web UI in the VS Code auxiliary sidebar: every window automatically starts and owns a local dsh web service (cwd = current workspace), so your modules, skills, MCP servers, credentials and sessions all just work. On top of that it adds the IDE integration layer:

• Chat in the sidebar: Ctrl+Alt+B opens it; copy/paste/context menu, file jumps and theme following are all native
• Context attachment: right-click a file / selection / folder / Problems to append a compact link to the DSH draft — source text is never pasted, nothing is ever auto-sent
• DSH Changes review: workspace edits pushed by DSH land in a dedicated tree with diff / accept / undo; every write needs explicit approval (on by default)
• @dsh chat participant: type @dsh in the native VS Code chat to talk to your local DSH session with streaming replies — zero Copilot quota (on by default)
• Advanced, opt-in: Ctrl+K / Ctrl+I inline edit, model routing into the VS Code LM picker, MCP consumption, terminal / UI bridges, FIM tab completion — every capability behind an explicit consent switch (FIM tab completion is a POC and was not end-to-end verified in this release, see the table note)

⚠️ Compatibility

The extension reads the installed official DSH package version before launch. Versions before 0.1.2-rc.1 are expected to expose the legacy apiProxy host and native session REST routes; 0.1.2-rc.1+ is expected to expose sessionController, so the bundled integration restores the removed REST surface. The version selects the diagnostic expectation only: live capability negotiation claims whichever service actually exists, keeping forks and prereleases fail-open instead of blocking plugin activation.

Authenticated runtimes (0.1.2-rc.1+) protect the browser surface with a SameSite=Strict cookie that a normal browser tab can hold but a webview iframe cannot (third-party context). Since 1.1.6 the extension automatically embeds such children through a loopback forwarder owned by the extension host (HTTP, SSE and the Typert WebSocket all relayed host-side) — no configuration is needed, and the sidebar works the same on old and new runtimes.

🧪 Release status (1.1.7)

This update: recording DSH changes never steals sidebar focus anymore (multi-window setups stopped auto-opening every sidebar at once), and a freshly scaffolded profile inherits the web profile's module config (dependencies, bundles, patch-layer disables). Full notes in CHANGELOG.md.

Verified this release: sidebar embedding against a real 0.1.2-rc.1 child end to end (index, session create/list, SSE event stream, WebSocket remote channel and workspace list, all through the embed forwarder in a third-party-iframe context); per-window port behavior; full unit suite (776 tests).

Not verified / known gaps:

• A full conversation round-trip against a live model provider from a dev-isolated DSH home (.vscode-test/f5/): UI, workspace tree and model catalog were verified, but prompts require the provider key to be stored in that home (web Models page) or exported — the key vault is per-home.
• Add to DSH Thread timed out once during live F5 testing; the entire message chain (extension → shell → iframe client → reply) was verified correct in a faithful third-party-iframe repro and the timeout did not reproduce. If it recurs, please open an issue with the exact sequence.
• FIM tab completion remains a POC and was not end-to-end verified (unchanged, see the table note).

Roadmap: the next major release restructures runtime boundary management — home/profile selection, runtime version negotiation, child ownership, port/instance discovery, startup URL/token, health checks and installed/dev coordination will derive from one runtime identity across prepare → spawn → authenticated readiness → teardown. Expect internal breaking changes with compatible user behavior.

📦 Install

• Marketplace (recommended): search DeepSeek Harness (publisher Xizhi1024) in the Extensions view, or code --install-extension Xizhi1024.dsh-vs-sidebar
• VSIX: download from Releases → Extensions: Install from VSIX...

🚀 Usage

1. Press Ctrl+Alt+B — the extension starts (or reuses) the local dsh web and loads the UI
2. Select code → right-click Add to DSH Thread; the draft receives a compact file:line link, press Enter to send (Ctrl+Enter / Cmd+Enter inserts a line break)
3. Type @dsh + your question in the VS Code chat — replies stream from your local DSH session
4. Let DSH propose an edit through the bridge: it lands in the DSH Changes view for diff / accept / undo — nothing is written without approval

Common commands (palette, DSH: prefix): New / Switch Session · Open Session History · Restart / Stop Server · Open in Browser · New DSH Instance · Diagnose · Restart Cleanly · Set DSH FIM API Key.

⚙️ Configuration

Full key list in package.json; run DSH: Diagnose for a health summary.

Dedicated profile

The extension launches its DSH child on its own profile (vscode by default), fully separate from the web profile a terminal dsh web uses — separate plugin tree, separate cordis patch layer, separate server instance. When the profile directory does not exist yet, the extension scaffolds it once (manifest with the web app bundles, empty patch layer, pnpm settings). Clean-restart (Restart-Clean) only restarts the extension's own child and never touches a terminal dsh web. To share one profile again, set "dsh.profile": "web" and reload the window.

License

MIT