Router
Long-lived. It keeps global context, talks outward, and dispatches work. The essay says it can operate without doing the task itself.
A Router-Worker design for a coding agent that can hold more than one task. The public code is a research prototype, not an official DeepSeek product.
Holds context and talks outward.
Executes in its own session.
Exploring Super-agent Design describes a continuous agent: one voice, several tasks, events from chat and GitHub.
deepseek-ai/dsh-superagent-prototype is a TypeScript bundle for DeepSeek Harness. Its banner says research code, not production software.
The repo says it was adapted for publication, so it is not the internal system and not every idea in the essay.
A single chat coding agent stores memory and does the work in one loop. Unrelated tasks contaminate that loop. A fresh session for every event loses the shared picture, and several sessions may answer the same person. The DeepSeek Harness team says its experience is that a person can actively follow about three to five sessions. That is their observation, not a published study.
Long-lived. It keeps global context, talks outward, and dispatches work. The essay says it can operate without doing the task itself.
One assignment, an isolated context, and the tools to execute. Workers report back so the user hears one voice.
A team lead decomposes one coupled task. The router decides that a task exists and leaves the decomposition inside the worker.
GitHub, and optionally Feishu, produce events. The essay also discusses mail and other channels as direction.
Something has to decide the event asks for new work, not just noise.
Accepted work is a ticket with a reason it may proceed. Each ticket gets its own session and directory.
Later comments, such as on a pull request, can reach the same worker without a new mention.
The prototype’s architecture note says Engine is the only writer of Triggers, Threads, Decisions, Tickets, and Assignments. A command changes those records in one transaction. External work is queued inside the transaction and performed after commit. That is the difference between a chat log and a system of record.
You are the scheduler. Each window is a session you must remember.
The router keeps the relationship across tasks. Workers run apart so one slow command does not freeze the conversation.
The prototype acts when asked, or when a rule the team wrote allows it. Proactivity without a policy is just noise.
Research prototype. Not an official product. Not production-ready.
Essay for the idea. Repository for what you can run. Engine for how state is saved.
A coding agent that can open pull requests needs an authorization model you have actually read.
Public sources, read in November 2026. Projects move. Claims marked as project statements were not remeasured for this deck.