DeepSeek Harness v0.1.2-alpha.2
DeepSeek Harness v0.1.2-alpha.2: Reconnects, Presets & Token Stats
- Author
- DeepSeekAgent.io Editorial Team
- Published
- Updated
On August 30, 2026, DeepSeek released dsh-v0.1.2-alpha.2. This time the release is not only a GitHub source tag: @deepseek-ai/[email protected] is available through npm's alpha channel. The latest and next tags still point to 0.1.1-rc.2, however, so a normal npx @deepseek-ai/dsh web command does not silently move users to alpha.2.
Alpha.2 does not introduce another broad Harness redesign. It makes the alpha.1 line easier to observe and operate: failed connections can retry, active schedules are visible in conversations, plugins and presets are easier to inspect, and completed answers show token usage and elapsed time.
The short version
v0.1.2-alpha.2 is an official pre-release published on GitHub and through npm's alpha channel. It is not a stable release. Pin alpha.2 in an isolated test environment if you need its changes; stay on the default rc.2 line if stability matters more.
Where the release is available
| Check | Status on August 31, 2026 |
|---|---|
| GitHub Release | v0.1.2-alpha.2, marked Pre-release |
| GitHub tag | dsh-v0.1.2-alpha.2 at commit 0a53fb5 |
| Exact npm version | @deepseek-ai/[email protected] is published |
npm alpha | Points to 0.1.2-alpha.2 |
npm latest / next | Still point to 0.1.1-rc.2 |
These commands therefore do different things:
# Uses the default release channel
npx @deepseek-ai/dsh web
# Explicitly tests alpha.2
npx @deepseek-ai/[email protected] web
Availability on npm does not make alpha.2 the default stable upgrade. GitHub still labels it as a pre-release.
What changes in alpha.2
Retry failed connections
The Web interface now exposes connection failures, supports automatic retries, and offers an immediate reconnect action. This gives users of remote DSH deployments, reverse proxies, and unreliable networks a clearer signal than an apparently frozen conversation.
It improves connection recovery; it does not guarantee that every failed interaction can be replayed safely. If a tool may already have run before the UI disconnected, inspect the session record before resending the task.
See active schedules in the conversation header
When the Schedule composition is enabled, active reminders appear in the conversation header. The surface is read-only: it does not create, edit, delete, or acknowledge reminders.
DSH Schedule is a session-local reminder mechanism, not an operating-system notification or hosted job runner. Closing the process or leaving the Session cold stops its in-memory timer. Reopening the original Session can restore persisted reminders and deliver an overdue occurrence.
Inspect plugins and Agent Presets more easily
The plugin list now separates conversation-scoped and global plugins. Users can also select an Agent Preset to inspect its composition and search other presets.
The useful distinction is composition: plugins implement capabilities such as models, tools, storage, and UI surfaces, while a preset assembles plugins into a runnable Agent. The alpha.2 UI improves discovery and inspection; it should not be read as permission to replace the complete tool composition of any running session at will.
Show token usage and elapsed time after answers
Completed answers now show token usage and elapsed time, with additional details available on click. This makes it easier to notice when a long conversation is becoming expensive or a particular task is taking unusually long.
These figures are observability data, not budget enforcement. They do not stop expensive work automatically and do not replace the provider's final billing record.
Process long histories and live messages more efficiently
The release notes call out more efficient handling of long conversation histories and high-volume live messages. It also reduces unnecessary filesystem checks while loading conversations on macOS and Linux. Those changes matter most for sessions containing many tool calls, images, or subagent events.
Report more useful errors
When web_search fails, DSH now reports the effective endpoint and underlying error details. This helps distinguish a broken search service from an endpoint configuration problem or an upstream response failure.
The Remote gateway also gains unified RemoteError wrapping, giving plugin authors a more consistent shape for remote-call failures.
Fix some Node.js 24 startup failures
Alpha.2 fixes startup failures and broken HMR on Node.js 24.0 through 24.11.1. This matters directly to source builds and plugin development. A stable rc.2 environment does not need to move to the entire alpha line for this fix alone.
What plugin authors should check
Alpha.2 restores SessionEvent.ignorable, which alpha.1 removed. That reversal is a useful reminder that event interfaces can still move quickly during the alpha cycle.
At minimum, test:
- Session-event parsing with the restored
ignorablefield. - Remote failures against the unified error wrapper.
- Web UI integrations that depend on the previous plugin list or answer-footer DOM.
- Disconnect, reconnect, and duplicate-message paths around tools with side effects.
- The DSH version range declared in each plugin's
package.json.
Choosing between alpha.1 and alpha.2
| Scenario | Recommendation |
|---|---|
| Regular user | Stay on npm's default 0.1.1-rc.2 |
| Testing the 0.1.2 line | Pin alpha.2; there is little reason to start a new alpha.1 install |
| Plugin compatibility | Keep separate rc.2 and alpha.2 test environments |
| Production deployment | Do not follow the moving alpha tag automatically; pin and verify an exact version |
Alpha.1 introduced the larger changes: Agent Teams, PTC, ACP, subagent model selection, and major client restructuring. Alpha.2 is the follow-up that improves connection handling, observability, preset management, and day-to-day operation.
Should you upgrade now?
If you use the default Web UI through npx @deepseek-ai/dsh web and do not have a connection or Node.js 24 problem, staying on rc.2 is reasonable.
If you develop DSH plugins, test Schedule, rely on long sessions, or need to validate 0.1.2 interface changes, alpha.2 is the better current test baseline. Pin the full version and use a disposable workspace and separate configuration so pre-release migrations do not affect everyday sessions.
Related reading
- DeepSeek Harness v0.1.2-alpha.1: Agent Teams, PTC and compatibility changes
- DeepSeek Harness guide: installation, API key setup, and usage
- Agent Preset vs Plugin: what is the difference?
- DeepSeek Harness security: sandboxes, permissions, and prompt injection
Frequently asked questions
Is v0.1.2-alpha.2 a stable release?
No. It is an official GitHub pre-release and an npm alpha release. npm's latest and next tags still point to 0.1.1-rc.2.
Does a normal npx command upgrade to alpha.2?
No. npx @deepseek-ai/dsh web follows the default release channel. Specify @0.1.2-alpha.2 to test this build, and recheck npm's dist-tags before installing.
Does alpha.2 support Cron jobs?
No. The current Schedule overlay supports delayed, absolute-time, and fixed-interval reminders owned by the original Session. It is not Cron, an operating-system notification, or an external messaging service.