DeepSeek's super-agent release is a rulebook before it is a repository

DeepSeek's Harness team published two things on 31 October and only one of them is code. The first is a repository called dsh-superagent-prototype, MIT licensed, created that morning and carrying a single commit. The second is an essay about agent design, published in Chinese on WeChat, which most English-speaking readers have met as a machine translation. The repository is the artefact anyone can run. The essay explains what DeepSeek thinks it is building.

One commit, two audiences

GitHub's API records exactly one commit on the default branch, 6337fc8, "feat: add the dsh-superagent research prototype", authored as DeepSeek Harness Team. No tags, no releases. The description repeats the essay's title; the repository reads as an appendix rather than a launch.

The README opens with a disclaimer unusual in its directness: "Research prototype for reference only, not an official DeepSeek product." Then it goes further. The code "grew out of our team's day-to-day development work, with much of the engineering done by coding agents", and readers should "treat it as research code, not production-ready software. It may still contain bugs, and its coding style and engineering practices may be inconsistent."

The provenance split matters: the code is on GitHub in English. The essay is on WeChat, in Chinese, with no English version from DeepSeek; readers outside China work from translated X threads and a third-party rendering at offloop.org. That is an asymmetry, not a scandal: the code travels, the reasoning arrives second-hand.

What the thing actually does

The prototype is "a proactive coding agent for one GitHub repository, packaged as a bundle for DeepSeek Harness". It listens to GitHub and, optionally, Feishu. When someone allowed asks it for work, it opens a work item, works on it in its own agent session and directory, and answers in the original conversation, typically with a pull request. A web panel shows what needs a person.

Installation is agent-mediated: you point your own coding agent at SETUP.md. pnpm check runs typecheck, tests and build. The documentation is numbered as a sequence rather than a manual — 000 Philosophy, 001 Domain model, 002 Authorization, 003 Execution, 004 Prompts, 005 Panel, 006 Deployment, 007 Architecture, 008 Cookbook — which reads like an internal design corpus pushed in the order it was written.

The Harness product page lists DeepSeek-V41-Flash as the model driving the harness; nothing in the repository argues for another choice.

The philosophy is the product

000-philosophy.md is the part most likely to outlive the release. Its opening claim is a budget: "Every part of the project is judged by the attention it costs." Behaviour follows. The agent "acts only when asked, or when a written rule allows it." It "speaks only when a person must act or can use a result", "confirms a request once and names what it will do", and "stays quiet while it works." When it needs something, it "asks one concrete question at a time, in a structured form, so the question reaches the person instead of staying inside a long report." It "stops by impact, not by effort". And it "reports honestly. A draft is marked unfinished, a failure is reported as a failure, and a limit is never bypassed to avoid asking."

Read together, they describe an agent optimised for a resource that is not compute. Yujia Qiao of the Harness team writes that "one person can usually keep track of only three to five active Sessions at a time", and concludes that "the ceiling for a single task is set by model capability; the ceiling for multiple tasks is set by human attention." If that holds, throughput is not a model problem and no context window fixes it; it is a supervision problem, and the philosophy is a supervision policy.

Four properties, five modules

The essay names four properties a super-agent needs.

Property	Meaning
Continuity	One agent across IM, GitHub and comments, with no "does session X know Y?"
Efficiency	Answers quickly while several complex tasks run in parallel
Proactivity	Observes events and acts on written rules, staying quiet otherwise
Persistence	Always online in real work environments, recovering from its own exceptions

Sections 2 through 6 describe the machinery: a two-layer architecture balancing continuous interaction against concurrency, event-driven operation, human-centered interaction, separation of compute, state and environments, and a Watchdog for persistent operation and recovery. The essay also describes an internal instance carrying one task across IM and GitHub that "continuously monitors feedback in public group chats, proactively identifies root causes, and submits fix Pull Requests even when nobody @mentions it."

The gap between the essay and the code

DeepSeek is explicit that the published repository is not that instance. "We have adapted it for publication, so it is not identical to our internal version or the implementation described in Exploring Super-agent Design", the README says, and then the sentence that matters to anyone reading the essay as a specification: "Some designs discussed in the article are directions for future development and are not implemented in this prototype."

So the release is a philosophy, a domain model and an adapted prototype, in that order of completeness. No benchmark numbers, no comparison, and no account of how much of the internal system survived adaptation. On r/singularity it drew roughly 780 points and about 17 comments within a day: wide sharing, thin argument, significance recognised before anyone had anything to test.

Proactivity buys silence as well as focus

The awkward question sits inside the principle DeepSeek states most proudly: "take as little human attention as possible, and give as much value as possible." As a constraint that is defensible: attention is the bottleneck the essay identifies, and an agent that interrupts for every decision is worse than no agent. But the rule is equally good at hiding failure. An agent that stays quiet while it works, reports only what a person can act on, and stops by impact rather than effort has few surfaces on which to fail visibly. Silence is indistinguishable from idleness, and nothing here tells them apart.

The philosophy sees the risk in one direction. Its operator section warns that "the agent comments, opens pull requests and messages people under accounts your team sees every day. Every message it sends costs your colleagues' attention, and you are responsible for it." That assigns liability clearly, to the human, and no metric to the agent: no budget of interruptions, no logging rule an operator could audit quiet periods with, no definition of the value half of the sentence. A constraint on behaviour rather than a measurable target is good culture and weak evaluation.

One guardrail deserves more attention. Proactive work starts in a mode that only records what the agent would have done: shadow mode, borrowed from observability practice. Run the policy, log the decisions, ship nothing. For an agent commenting under your team's accounts it is the right default, and the most concrete safety decision here.

What the release is worth

For teams running coding agents, the reusable part is the document set rather than the bundle. The authorization, execution and panel documents answer questions most agent projects answer by accident, and the operator section is a better deployment warning than any vendor's acceptable-use page. Anyone copying the code should copy the sequencing too: narrow allowed list first, proactive work recorded only, volume ruled out — "Do not use it to produce volume. Mass pull requests, broadcast messages and busywork cost the team more than they give."

For DeepSeek, the release establishes vocabulary ahead of any product: super-agent, attention budget, watchdog. A category named in public, with a reference implementation attached loosely enough that nobody can hold the company to it.

The test is whether the internal claims survive outsiders. DeepSeek says an instance of this design finds root causes in group chats and opens fix PRs unprompted; nobody outside can verify it, and the published code is explicitly not it. Until someone reproduces the proactive loop on a repository they own, the defensible reading is that DeepSeek published a rulebook, an adapted implementation and an argument, and that the argument is the strongest of the three.