deepseek-harness-for-vscode

DeepSeek Harness for VS Code

English | 简体中文

A native VS Code coding-agent extension powered by DeepSeek Harness. Install the platform-specific VSIX and start working—there is no upstream repository to clone, no Node/npm setup, and no local Harness deployment to manage. Community-maintained 0.6.2 stable extension release, bundling the official @deepseek-ai/dsh@0.2.2-rc.1 package (Typert Remote protocol) and standalone Node 24.22.2. The bundled DSH runtime is a release candidate, and DeepSeek Harness remains a Developer Preview.

This release unifies saved session history with official DSH, groups conversations by their original project folder, adds native MCP management, and fixes duplicate or out-of-order prompts. See the Chinese release notes. Runtime upgrade: Harness now uses session format V4. Supported older logs are migrated on resume into a new generation while their original files are preserved. Old runtimes cannot read the new V4 generation; back up the shared history home (default ~/.dsh) and the private ~/.dsh/vscode/harness-home before upgrading, and do not downgrade an active profile. Third-party plugins using the removed ctx.agent or runtime Inbox APIs need their own compatibility updates. The extension keeps its native VS Code interface rather than embedding the official Web UI.

Startup uses the official runtime package resolver. Only a recognized legacy module conflict triggers one bounded backup-and-repair attempt; ordinary profile packages are no longer moved on every startup or installation. 0.6.2 release update

This update aligns the workbench with DSH 0.2.2-rc.1: One saved-history store: new sessions use the selected shared sessions/ directory, normally ~/.dsh/sessions. Readable legacy histories migrate with their originals retained; an incompatible record no longer switches the extension to a private store. The history panel shows the actual path and migration details. Project-based session management: conversations belong to their original folder across clients. Browse other projects, preview without activating an Agent, and choose Continue here to request native execution ownership. New conversations work directly in the selected folder; existing worktrees retain manual actions. Native changes and titles: per-turn snapshots and diffs use @deepseek-ai/dsh-workspace-changes. Titles are read from native logs and retained across partial or stale metadata updates. MCP management: add, edit, enable, disable and remove stdio or Streamable HTTP servers through More → MCP servers or the command palette. Changes are validated and wait for idle model turns before reloading the Host. Conversation and compatibility fixes: attached editor context no longer duplicates prompts after answers; streamin

Download the VSIX from the v0.6.2 release and reload VS Code after installation. GitHub Actions builds and publishes the four platform packages when the release tag is pushed. Marketplace publication is separate. Release notes are available in Chinese in the changelog. Runtime update policy

The bundled DeepSeek Harness runtime is upgraded selectively, not automatically with every upstream release. We review the actual changes—relevant features, bug and security fixes, and breaking changes—and adopt an update after compatibility adaptation and regression testing, with particular attention to Windows, macOS, Linux, existing conversation history, and plugins. The earlier 0.1.7 native capability audit is tracked in the upgrade audit.

Stability and the upgrade experience for existing users take priority over always bundling the newest version. Releases that still need validation or