DeepSeek Harness Gives Agents Hands, Boundaries, and Memory
The bottleneck in agent tooling has shifted from model intelligence to system boundaries and trust; DSH shows that a runtime which owns session, approvals, and recovery lets one human supervise multiple agents, but only if permissions and contexts are set deliberately.
DeepSeek Harness (dsh) is an agent runtime that equips models with tools, sandbox boundaries, memory, and a plugin system. Its core is an agent loop: the model requests a tool call, the harness executes it in a sandbox, appends the result to an append-only session log, and feeds the updated history back to the model. That loop lets a task span dozens of steps instead of one reply.
The architecture splits into six layers: session (memory), loop (advancement), tools (execution), sandbox/approval (safety), context (cost), and delivery (landing). Profiles stack plugins via YAML patch files, so users can disable or reconfigure components without waiting for official releases. A headless mode runs the same kernel inside CI.
A separate super-agent prototype, open-sourced as dsh-superagent-prototype, separates Router (decides) from Worker (executes), makes workers stateless and replaceable, uses chained retrieval to treat the context window as a cache, and adds an independent watchdog session. Reported p95 completion time dropped from 29.5 to 15.7 minutes across a batch of tasks. The practical sections also cover permission modes, 256 auto-retry turns, and the hard rule that chat replies stay under 100 words.
The line between a toy and a tool for agents is whether the user specifies acceptance criteria rather than intentions.
Shifting session management into the system reassigns the human role from operator to spec-setter, so the bottleneck moves from attention span to specification clarity.
Router design depends on a bounded context from work-group boundaries like repos and PRs, so workflow structure substitutes for model reasoning about access.
The 100-word IM cap treats agent output as a communication design problem, not just a model capability problem.
Making workers stateless and replaceable means parallelism is limited by compute rather than instance count, which is a bigger architectural leverage than the p95 improvement suggests.
The Harness layer is done right; the remaining pitfalls are basically all in the accounting. When we integrated DeepSeek ourselves, the three most troublesome things were: retries must be recorded per attempt, cache hits need to be separately tagged, and second requests after truncated output shouldn't be double-counted. If these three aren't itemized, the end-of-month reconciliation always comes up short. Later, several domestic models used the same key through one gateway, and with details exported by business line, reconciliation could be closed within half an hour. We can chat about details in private.