The DeepSeek Harness team just released dsh-superagent, an MIT-licensed research prototype. DeepSeek dsh-superagent is a proactive coding agent for one GitHub repository. It is packaged as a bundle for DeepSeek Harness. It listens to GitHub and, optionally, Feishu. It turns allowed requests into parallel work items, each in its own agent session. The release shipped alongside a design post, Exploring Super-agent Design: Towards a More Autonomous Agent System.
TL;DaR
- What is it?: A TypeScript bundle, v0.1.0, released as 1 commit under MIT. It uses whatever model the Harness profile is set to.
- Runs on: Your own machine, as a dedicated DeepSeek Harness profile. Needs Node.js 22.19+ or 24+, git 2.32+, Python 3.8+, tmux and GitHub CLI 2.48+.
- Performance: In DeepSeek’s simulation, it finished tasks far faster under a noisy message stream than a single-session agent.
- Best: p95 task completion of 15.7 minutes vs 29.5 minutes for the single-session baseline (about 1.9x faster).
- Worst: Tested only on synthetic messages and simulated tools. Real coding quality was not measured.
What is DeepSeek dsh-superagent?
It is a GitHub agent that waits to be asked. When an allowed person addresses it, it opens a work item, called a Ticket. Each Ticket runs in its own session and directory. Results return to the original conversation, often as a pull request. A local web panel lists only what needs a person.
The README page states the core rule plainly: take as little human attention as possible, and give as much value as possible. The philosophy doc applies it to behavior. The agent confirms once, stays quiet while working, and writes again only with a result, a question or a failure.
Why did DeepSeek build a Super-agent?
DeepSeek team argues that mainstream agents treat 1 session as the basic unit. According to the report, as reported by ifeng, a person can actively follow only 3 to 5 sessions at once. Human attention, not model capability, becomes the bottleneck for multitasking.
How does the Router-Worker architecture work?
The research team describes 2 layers. A long-running Router handles interaction and dispatch. Isolated Worker sessions do the actual work.
In the prototype, that flow is concrete, per the domain model:
- Source → Trigger: GitHub or Feishu produces events.
- Eval: decides whether a batch of Triggers asks for new work.
- Ticket: a unit of authorized work, with an immutable Mandate stating why it may proceed.
- Subscription: later comments on a pull request reach the right Worker without a fresh mention.
The main session runs the dsh-superagent-router preset with a smaller tool set. Each Worker runs dsh-superagent-worker. Shell commands move to the background after 5 seconds, so Workers keep receiving messages, per the execution doc.
Proactive work is gated. The authorization doc defines 3 accept modes: off, observe (default) and auto. In observe, the agent only records what it would have accepted.
The research team also lists ideas beyond the prototype: an external Watchdog, storage and compute separation, and an asynchronous ReAct loop.
