DeepSeek's SuperAgent Splits an Agent Into a Full-Time Router and Concurrent Workers — and Alibaba Built Its Own Version
SuperAgent and Flock set a design template for always-on agents that run unattended in production: separate continuity from concurrency, keep a deterministic core around the model, and make tasks outlive sessions. Western teams building long-running agents can adopt these patterns directly instead of rediscovering the same distributed-systems pitfalls.
DeepSeek's SuperAgent architecture solves the core bottleneck of multi-agent work: a single human can only track three to five active sessions. It introduces a two-layer design where a resident Router owns continuity and global memory, while isolated Worker sessions run tasks concurrently; the Router simply routes and reports, never executing. Event-driven triggers, a Fast Path of rules, and subscription direct-pass keep the model out of most decisions and reduce Router load.
The accompanying prototype code (about 16k lines) reveals concrete engineering decisions: a deterministic core that validates model proposals, an Outbox pattern for reliable side effects, external text treated as untrusted data, and a 30-word cap on Router notes to prevent distortion. Alibaba's Flock goes further, hiding sessions entirely behind a Sessionless model, using a Quest as the persistent task object, and growing DAGs organically as work happens. Both systems converge on the same insight: once the model handles single tasks, the remaining problem is reliable scheduling, persistent state, and human accountability.
The Router-Worker split is a direct answer to a fundamental tradeoff: continuity and throughput can't both live in one session, so the design gives each to a different layer.
Centralization in agents doesn't suffer from human bandwidth limits; DSH's stress test shows per-decision latency drops as event rate rises, because batching amortizes reasoning.
The debate between Anthropic and Cognition over multi-agent systems isn't about whether to split, but where the boundary lies: only independently verifiable work should be parallelized.
Agent reliability shifts from model correctness to system recovery; deterministic shells around LLM calls matter more than the model's raw ability.
Alibaba's choice of Channel isolation over a single Resident Router trades continuity for blast-radius control, a deliberate enterprise-oriented tradeoff.
The convergence of SuperAgent and Flock on Ticket/Quest, task chains, and Outbox patterns suggests constraints, not copying, drive agent design.
I agree with this observation about design convergence. Once the various Agent framework patterns converge, what matters is engineering details and context management. This kind of practice review is updated pretty frequently on ai345, and it's convenient for finding Chinese materials.