DeepSeek Harness v0.1.2-alpha.1
DeepSeek Harness v0.1.2-alpha.1: Agent Teams, PTC & Breaking Changes
- Author
- DeepSeekAgent.io Editorial Team
- Published
- Updated
The official DeepSeek Harness repository gained a dsh-v0.1.2-alpha.1 tag on August 27, 2026. It is a noteworthy pre-release source snapshot, but as of August 28 it is not published to npm and has no full GitHub Release with assets. This article describes code visible at the tag; it does not claim that a stable release has shipped.
Compared with v0.1.1-rc.2, this development line contains broad architectural work. The meaningful story is not the commit count but DSH's movement from an early composable preview toward a more complete agent runtime.
Bottom line
v0.1.2-alpha.1 expands multi-agent operation, remote control, SDKs, session persistence and the Web UI while changing interfaces used by some plugins. General users should wait for an official package. Plugin authors can begin isolated compatibility testing now.
Major changes
Experimental Agent Teams
The source includes Web and CLI profiles for Agent Teams. Persistent teammates, shared tasks and messaging are moving toward a launchable experimental composition. This is not yet a stable default, and lifecycle, recovery and long-running scheduling still need careful testing.
Code Mode becomes PTC
The user-facing code-mode terminology moves to PTC. PTC lets a model generate a program that combines multiple tool calls, reducing model–tool round trips. Older sessions can retain the previous name, so compatibility involves more than a string replacement.
SDK, ACP and model routing
- More independent SDK and ACP application bundles appear.
- TypeScript clients can launch through DSH profiles.
- Python SDK distribution continues to expand.
- Subagents can receive provider, model and allowed-submodel configuration.
Together these changes position DSH as a controllable harness runtime, not only a Web chat surface.
GitHub webhooks
New code can create workspace sessions from GitHub events. That opens a path to issue triage, review and automated repair, while making authentication, input validation and event deduplication more important.
Session and client restructuring
Client modules, remote controllers, session migration and per-session projection caches have changed. The intended benefits include cleaner remote APIs, smaller storage and more reliable cold reads. Plugins tied to old client modules, ApiProxy or old DOM structure may break.
Web security and transport
The tag includes one-time startup tokens, Web-fetch approval, SSRF controls, WebSocket keepalive and HTTP gzip work. These improve defaults but do not replace reverse-proxy authentication, least privilege or third-party code review.
Plugin-author checklist
- Check imports from moved or removed client modules.
- Find dependencies on
ApiProxyor old RPC paths. - Audit fixed DOM selectors used for UI injection.
- Test dependency resolution without assuming global
node_modulesaccess. - Verify old session migration and persistent state.
- Adapt to one-time tokens and the new remote controllers.
Should you upgrade now?
| User | Recommendation |
|---|---|
| General DSH user | Wait for npm or a full Release |
| Plugin author | Test in an isolated profile |
| Agent Teams researcher | Pin the exact tag and record it in results |
| Production operator | Do not switch before session, plugin and authentication tests |
Related reading
- DeepSeek Harness v0.1.1-rc.2 update
- How Agent Teams work
- DSH agent presets versus plugins
- DeepSeek Harness security model
FAQ
Is v0.1.2-alpha.1 officially released?
No. As of August 28, 2026, it is a pre-release tag in the official repository, not a published npm version or a complete GitHub Release.
Why cover an unpublished tag?
It reveals likely architectural direction and gives plugin authors an early compatibility signal. A source snapshot can still change and is not a stability promise.