DSH rc.5 update
DeepSeek Harness v0.2.1-rc.5: Default Install & Thinking Display
- Author
- DeepSeekAgent.io Editorial Team
- Published
- Updated
As checked on November 4, 2026, npm latest and next both point to 0.2.1-rc.5, while alpha points to 0.2.2-alpha.3. GitHub marks rc.5, published October 30, as a pre-release. This article follows official release notes. Local installation and upgrade testing has not been completed.
What changed in rc.5
The official notes list one improvement, better display of thinking content in conversations. They do not provide new model capabilities or performance measurements. The resulting display depends on the selected model, provider integration and conversation content.
The rc.4 fix on the path from rc.3
After rc.3, rc.4 was published on October 28 with a fix for diagnostics leaking into stdout in ACP mode.
For an ACP integration, verify a normal request and an error case in a test environment after upgrading. Check response parsing and ensure diagnostic output does not interfere with the protocol stream. The release notes do not enumerate all affected clients.
Install a pinned version
To reproduce this release, use its complete version:
npx @deepseek-ai/[email protected] web
The unpinned command follows the default npm channel:
npx @deepseek-ai/dsh web
That default can change. Record the actual version and launch command when reproducing issues or upgrading. See the Harness guide for initial configuration.
Is rc.5 a stable release?
GitHub still marks rc.5 as Pre-release, and the version retains its rc suffix. npm latest identifies the default install channel. It does not override the official release designation.
0.2.2-alpha.3 is a separate testing channel with unified review and worktrees, host-level automation and historical Session fixes. Evaluate the features you need and Profile compatibility before switching channels.
Upgrade checks
Back up the Profile, plugin configuration and important Sessions, and record the previous version. After upgrading, verify Session opening, thinking-content expansion and frequently used plugins. ACP users should also verify protocol exchanges.
These are suggested validation steps, rather than reported regressions. For Session-list issues, see the recovery guide.