DeepSeek Open-Sources Super-agent Architecture for Autonomous Cross-Session Tasks
DeepSeek released the open-source prototype of its 'Super-agent' architecture, featuring a dual-layer design to maintain context across platforms and speculative execution, with self-reported benchmarks showing improved task completion times.
Chinese AI company DeepSeek has open-sourced the underlying architecture prototype for its 'Super-agent' personal agent system on GitHub as of October 31, 2026. The solution aims to address common pain points in traditional Coding Agents, such as fragmented context during multi-task collaboration, the need for users to manually switch sessions, and the inability to run continuously over long periods.
The Super-agent employs a dual-layer architecture: an upper-layer Router handles message reception, task allocation, and global context maintenance, while lower-layer Workers are specific Agent sessions executing tasks. This design allows a single development task to seamlessly transition from IM group discussions to GitHub PR reviews without requiring the user to re-explain context. Additionally, the system introduces 'Speculative Execution,' where agents proactively attempt background processing (such as reproducing bugs or organizing meeting materials) upon detecting potential needs, presenting results only if viable solutions are found.
To achieve 24-hour online availability and self-recovery, DeepSeek separated computation, state, and execution environments, introducing an independent Watchdog module to monitor other agents. In a simulated collaborative environment containing approximately 300 messages and 20 work requests, DeepSeek's internal tests showed that Super-agent had a median task completion time of 12.4 minutes and a 95th percentile of 15.7 minutes, outperforming the traditional single-session approach's 29.5-minute 95th percentile.
It is important to note that these performance metrics are based on DeepSeek's internal simulation experiments and have not yet been independently verified. Furthermore, efficiency gains come with increased token costs; disabling the event direct-pass mechanism resulted in a roughly 30% increase in Router decision counts and a 37% increase in read-cache tokens.