DeepSeek Harness has published v0.1.2-rc.1, the first release candidate in its 0.1.2 series. It is a broad upgrade to the agent workbench, with better visibility into long conversations, more control over subagents and a pair of experimental inspection and browsing tools. The practical headline is not one shiny feature. It is that DeepSeek is making the harness more usable for sustained, tool-heavy work while also widening what it can do by default. That makes the release useful, but it also raises the cost of treating the safety notice as decorative wallpaper.
DeepSeek Watch analysis
What happened
– Better conversation control Full-history turn navigation, expandable token and timing statistics, adaptive content width and queued messages make long sessions easier to operate. – More capable subagents Agents can choose models within authorised limits, while callers can specify provider, model, reasoning effort and maximum output length. – Experimental web tooling Inspector and Web Preview arrive as experimental tools, with public WebFetch enabled by default and SSRF protection noted in the release. – Stronger interoperability ACP support now covers standard session controls, model settings, MCP, permissions and cancellation. – A storage change The optional SQLite Session persistence backend is removed. Existing content remains, but exporting it requires an older version. – The important warning DeepSeek says Harness has not undergone a security audit and that sandboxing, approvals and permissions do not guarantee isolation.
Why it matters
This is the sort of release that changes the feel of an agent system rather than merely adding another button. Better navigation and diagnostics reduce friction; configurable subagents make complex workflows more deliberate; web tooling makes them more exposed to the outside world.
The release candidate label matters too. Teams adopting it should expect to test their own profiles, plugins, persistence and network assumptions before making it the quiet engine room of anything important.
Our read
A substantial and promising upgrade for people already using DeepSeek Harness, especially where long sessions and subagent orchestration are the pain points. Try it in a controlled environment, read the safety notice, and treat public WebFetch as a meaningful policy change rather than a convenience toggle.
What to watch
- Whether the release reaches a stable 0.1.2 without changing the new interfaces.
- How experimental Inspector and Web Preview behave in real workflows.
- Migration paths for users still relying on SQLite Session persistence.
- Whether DeepSeek publishes more detail on the security boundary before wider adoption.
Discussion spark: Does enabling public WebFetch by default feel like a sensible usability improvement, or an unsafe default for an unaudited agent harness?
Sources and evidence
- v0.1.2-rc.1 (3 September 2026, 06:06 UTC)
not affiliated with or endorsed by DeepSeek