Skip to main content
PathDocs

DeepSeek Harness status: source 0.1.5-alpha.1 vs npm

In short: official source is now 0.1.5-alpha.1, while npm latest / next still resolve to 0.1.2-rc.1 and the alpha channel already publishes 0.1.5-alpha.1. Default npx runs the latest release; new interfaces described here refer to the source build.

Checked 2026-09-09. This is an independent community tutorial site, not an official DeepSeek site.

Verified baseline​

ItemResult
Repositorydeepseek-ai/deepseek-harness
Sourcemaster / 5dda764ed3aa172535a7967b06ff95d9cbfe536a
Commit time2026-09-08 23:25:45, UTC+8
Source version / tag0.1.5-alpha.1 / dsh-v0.1.5-alpha.1
npm channelslatest = next = 0.1.2-rc.1; alpha = 0.1.5-alpha.1
Since the previous site baseline1863 commits after cd5ef8148158
License / maturityMIT; Developer Preview with breaking interface changes
Node requirement^22.19.0 || >=24.0.0 in root package.json#engines
Default Web addresshttp://127.0.0.1:3080; source builds require the printed token launch URL

Version checks use official Git, root package.json, and the npm registry. Features were checked against the 0.1.5-alpha.1, 0.1.3-alpha.2, and 0.1.3-alpha.1 release notes and the corresponding TypeScript implementation.

Breaking changes (read before upgrading)​

ChangeImpactTutorial
Session format upgraded to V3Resuming a supported historical session writes new-format logs and keeps the original files; the system prompt becomes part of message history; legacy PTC events and code preset references migrate automatically. Custom log readers must adapt, and upgraded sessions cannot be read by older versionsUpgrade & migration, Sessions
Plugin Agent APIctx.agent is removed; callers must pass the Agent explicitly. Subagents that can continue a conversation are no longer treated as root sessions for schedulingPlugin anatomy, Subagents
Inbox APIInbox becomes a type interface and no longer exports a constructible runtime class; plugins read and write pending messages through agent.inbox, and hasPending / claim leave the public APISessions, Event system

Source changes and updated tutorials​

ChangeMigration / behaviorTutorial
Dynamic system promptSystem prompts can change without invalidating the KV cache when the configured model explicitly declares supportLLM routing
Experimental right SidebarTabs, split panes, and fullscreen; chat file links and produced files open in the Sidebar, and the Detail panel is removedWeb UI, Client resources
Generic file uploadAny file type mixes with images in one preview area; background uploads support progress, cancel, and resume display across session switches, and the model reads saved paths with existing file toolsAttachments
Outbound proxyAll outbound requests honor HTTP_PROXY, HTTPS_PROXY, ALL_PROXY, and NO_PROXY from the launch environmentEnvironment variables
Workspace files APINew packages/api/workspace-files lets the Web UI and plugins read and write files per workspaceWorkspace files
"Open in app"The Web top bar opens the workspace in an installed editor, IDE, terminal, or file managerWeb UI
Subagent session controlsContinuable subagents support queueing, editing, deleting, single or bulk Steer, and stoppingSubagents
PTC output expansionPTC mode can expand commands and their outputTool execution
Model probingCustom providers' models objects and Anthropic native model lists are supported, backfilling names, context windows, and max output tokens; pi-ai upgraded to 0.85.1LLM routing
Subagent plugin runtimeBuilt-in runtimes for optional subagent plugins upgraded to Codex 0.153.4 and Claude Code 2.1.263; explicit model settings are unchangedSubagents
UI and statsComposer menu layering, placeholder text, and spacing improved; session statistics split into two expandable summaries (turns and speed, exact token usage and cache hits); built-in slash command descriptions localized and updated live with the interface languageWeb UI
Python SDKNew macOS x64 runtime wheel installs and runs the bundled runtime on Intel MacsDrive the harness from a program
FixesSend button and Enter follow the same busy-session setting; the model can no longer resume a goal the user paused; POSIX absolute-path images in assistant messages render; empty messages and blank queue edits are rejected; project-root discovery reports permission/IO errors; fs-ext no longer needs local compilation on macOS/LinuxRelated pages

Official documentation​

Chinese counterparts live alongside these files with the .zh.md suffix.

Choose a distribution channel​

For the published npm release (latest channel):

npx @deepseek-ai/dsh@0.1.2-rc.1 web
npm view @deepseek-ai/dsh dist-tags --json

For the source features described here, use a separate checkout:

git clone https://github.com/deepseek-ai/deepseek-harness.git
cd deepseek-harness
git checkout --detach dsh-v0.1.5-alpha.1
pnpm install
pnpm run build
pnpm dsh web

When upgrading an existing installation across versions, clear the previous build output first (packages/*/* directories without package.json, every lib/, every *.tsbuildinfo); otherwise tsc -b skips artifacts because of stale incremental state. A source tag does not imply npm publication. Query the registry before the next upgrade, and keep SDK clients and runtime versions aligned.

Upgrade checks​

Start with the migration runbook for backups, isolated validation, and rollback. Optional walkthroughs: GitHub PR review and MCP memory.

  1. Back up session data first: the V3 migration keeps the original log files, but upgraded sessions cannot be read by older versions - rollback needs the old binaries plus a copy of the pre-upgrade session directory.
  2. Audit plugins for ctx.agent, Inbox constructors, and hasPending / claim, and adjust per the breaking-change table above.
  3. Migrate old code tool modes, API Proxy imports, and SDK launch options using the linked guides.
  4. Inspect dsh web --dump-config, especially telemetry, WebFetch, model selection, and third-party plugins.
  5. Upstream README / SECURITY state that the project has not been security-audited. Approval, permission presets, and sandbox mechanisms are not a containment guarantee. Start with a test directory without sensitive information and assess plugins and data egress separately.

Follow changes​

Use official Releases for release changes and Discussions for feedback. Our plugin ecosystem is a community directory, not an official endorsement.