The Super-Agent Blueprint: Building an Always-On, Production-Grade AI Agent 🤖

The DeepSeek Harness team published a paper, "Exploring Super-agent Design," describing the architecture behind its internal always-on agent, which monitors team chat, spots untagged bugs, and opens pull requests to fix them. In preliminary tests, the Super-agent design completed tasks about 40% faster at the median than a standard single-session agent, nearly halved the time for the slowest 5% of tasks, and saw per-routing-decision inference time fall by three quarters when load rose 40-fold. The team also found that single-session agents never delegated to subagents in five runs even when prompted to, arguing the fix must be structural rather than prompt-based.

👋 Hey, Linas here Every day, I break down 3 stories shaping the future of FinTech & Artificial Intelligence - plus the money movements and trends worth tracking. First time here? 400k+ FinTech and AI leaders get this daily. Join them: Most AI agents today fail because of the system wrapped around the model . DeepSeek https://linas.substack.com/p/deepseeks-leaked-investor-call has just published a blueprint for fixing that. Today’s coding agents and personal assistants can finish a single task with little supervision. Yet they still live inside one chat session at a time, and the DeepSeek Harness team finds a person can follow only 3 to 5 active sessions at once. So agent productivity is now basically capped by human attention https://linas.substack.com/p/anthropic-employment-report . What is a Super-agent? A Super-agent is a single, always-on AI agent that keeps one continuous memory across every channel, runs many tasks in parallel, acts on events without being prompted, and recovers from failures on its own. The closest thing to this we have today is probably SpaceXAI’s Grok Bot https://linas.substack.com/p/grok-bot-guide , the AI agent product we called the first real AI Agent OS . But the exact term above comes from the DeepSeek Harness team’s paper Exploring Super-agent Design , which was just published. It describes the architecture behind their internal agent, which watches team chat, spots bugs nobody tagged it on, and opens pull requests to fix them. That’s the gap between a demo and a Grok-bot-quality agent https://linas.substack.com/p/how-to-hire-a-grok-bot . You can tag it in any thread, and it answers fast, remembers the whole story, works while you sleep, and never needs a restart. Why this architecture matters First, the numbers that back it up. In DeepSeek’s preliminary tests, the Super-agent design finished tasks about 40% faster at the median than a standard single-session agent , and nearly halved the time its slowest 5% of tasks took. It also got more efficient as traffic grew : when load rose 40-fold, the inference time per routing decision fell by three quarters. Then the delegation result worth remembering. Given a neutral prompt to use subagents when appropriate, a single-session agent never delegated once in five runs . Even a prompt that pushed hard for delegation failed once, so the fix has to be structural . And the best part is that because the design lives in the system around the model and borrows proven ideas from computer systems, it applies whether you build on DeepSeek, Claude https://linas.substack.com/p/how-to-use-claude-opus-5-5 , ChatGPT https://linas.substack.com/p/how-to-use-gpt-6-astra , Grok, or other open-source models i.e., GLM https://linas.substack.com/p/glm-5-3-flash-guide or Qwen https://linas.substack.com/p/qwen3-8-27b-local-guide . Of course, knowing what a Super-agent is and building one are two very different things. DeepSeek’s paper explains the ideas. This blueprint turns them into a hands-on manual, module by module, with everything you need to go from a single chat session to an agent that runs your team’s work around the clock. Here’s what’s inside: - The full architecture diagram , showing how every event moves through the five modules - Build instructions for each module : the Router/Worker multi-agent pattern, event-driven triggers, full-duplex multi-channel interaction, cloud and state separation with Bring Your Own Machine, and the self-healing Watchdog - 30+ checklist items you can turn straight into tickets - The context-engineering trick that lets an agent recall a weeks-old task without stuffing its context window - The experiment data 4 agent designs, head-to-head and what it means for your build - A 4-phase build roadmap with pass/fail gates, from first prototype to a production agent that runs itself - A security baseline for agents that read untrusted input and touch real machines - A one-page cheat sheet : 12 design rules, the systems ideas behind them, and 8 mistakes that will cost you This blueprint is written for founders, AI engineers, and product teams building coding agents, personal assistants, Slack or Discord bots, or any multi-agent system. Everything comes from DeepSeek’s paper. Practical additions on top are marked as Builder’s notes . Below we’re getting really practical: the diagrams, the checklists, the data, and the exact build order. It’s the part you’ll keep open in a tab while you build. Let’s dive in.