Freshness · Independent guide

DeepSeek Harness Latest Version: npm, GitHub and SDK

As checked on 2026-10-04, npm latest and next both point to 0.2.0-rc.2; PyPI publishes 0.1.5rc1; GitHub lists dsh-v0.2.1-alpha.1. The GitHub alpha is a different release from the npm default. The retained Linux HTTP 200 test used 0.1.0-rc.7, so it does not validate either newer release.

Reviewed Oct 4, 2026Developer previewIndependent guide
Evidence status: First-party npm, PyPI and GitHub identities retrieved on 2026-10-04; rc.7 runtime evidence retained separately. Re-check the linked first-party source after a new release candidate.
Track setup progress →

Sharing includes the public link only, without local progress or private configuration.

Start with this command

This is the narrow command relevant to this page. Read the checks below before changing flags, credentials or profile patches.

Public command · no secrets
npm view @deepseek-ai/dsh dist-tags --json
npm view @deepseek-ai/dsh@next version
python -m pip index versions deepseek-harness-sdk
# Snapshot: npm latest 0.2.0-rc.2 / npm next 0.2.0-rc.2 / PyPI 0.1.5rc1

Current DeepSeek Harness release channels

Pin the distribution you actually use. These values come from first-party registry records and the official GitHub release, retrieved on 2026-10-04. A moving dist-tag is not an immutable version.

  1. npm latest: 0.2.0-rc.2, published 2026-09-29.
  2. npm next: 0.2.0-rc.2, published 2026-09-29.
  3. Python SDK: 0.1.5rc1, requires Python >=3.10; its wheel depends on the matching runtime-bin version.
  4. GitHub: dsh-v0.2.1-alpha.1, published 2026-10-03, tag commit 5badb15009ae1756c3afe0ae0cef1faafc290ccc.

Documentation review and runtime verification

The October review uses the fixed 5badb15 GitHub commit. It confirms documented behavior, not an npm installation or paid model request. The archived 0.1.0-rc.7 Linux record remains a separate historical observation: the Web UI returned HTTP 200 on a selected local port. A reachable page alone does not verify model authentication or task completion.

What the newer GitHub alpha changes

The October 3 alpha adds a Web --public-url option for reverse-proxy entry points and an experimental Claude Code Mods compatibility layer. That compatibility layer is an experiment, not a promise that arbitrary Claude Code Mods work. Plugin authors must review the removal of runtime invariant plugins and ./invariant exports, plus changes to the composer statistics extension entries.

  1. These notes belong to the GitHub alpha; do not assume the npm latest package already includes them.
  2. Bundle installation now reports the installed version; replacing a bundle version still requires a profile restart.
  3. Read the target release notes before reusing custom profiles or third-party plugins.

Choose a version and preserve a rollback

Use the install page for the current npm pin, or the Python SDK page for the independent PyPI pin. Record your working version, profile and one baseline task before upgrading. A return to an older executable may also need its compatible profile backup; it does not undo every configuration change.

First-party sources

Open the pinned or retrieved source before acting on a changed release candidate.

Continue by layer

Update DeepSeek Harness: Version Pins and Rollback Checklist
Open guide →DeepSeek Harness Install: Node and Web UI
Open guide →DeepSeek Harness Python SDK: Install and First Run
Open guide →DeepSeek Harness Setup Checklist: Save Your Progress
Open guide →