@PierceZhang34: Recently, Anthropic published an engineering blog post that detailed their multi-agent research system. The conclusion is quite striking: using Claude Opus 4 as the main orchestrator and Claude Sonnet 4 as sub-agents, the multi-agent system outperforms a single Claude ...
Summary
Anthropic published an engineering blog post detailing a multi-agent system, using Claude Opus 4 as the main orchestrator and Claude Sonnet 4 as sub-agents. The multi-agent system improved performance by 90.2% over a single Claude Opus 4, while token consumption increased by approximately 15x. It also summarized five collaboration patterns.
View Cached Full Text
Cached at: 06/03/26, 07:48 AM
Recently, Anthropic published an engineering blog post that broke down their multi-agent research system in detail.
The conclusion is pretty striking: using Claude Opus 4 as the lead orchestrator and Claude Sonnet 4 as subagents, the multi-agent system outperformed a single Claude Opus 4 agent by 90.2%.
Not a 10% or 20% improvement — 90%. That number really drives home the massive power of multi-agent systems.
First, let’s walk through how they did it. The architecture is clear: a lead agent decomposes the problem and assigns tasks, while multiple subagents execute in parallel. Each subagent receives a well-defined subtarget, output format, and tool instructions — it’s not just thrown out to let them run wild. For example, in one research task, the lead agent dispatched 10 subagents to research 75 companies, with each subagent handling 7–8 companies, running in parallel, then aggregating the results. A single agent simply couldn’t handle this — the context window would blow up, time would run out, and there’s no parallelism.
But what’s the cost? The multi-agent system consumes roughly 15 times the tokens of a standard single agent. So Anthropic themselves note that upgrading the model quality is more effective than doubling the token budget. More agents aren’t always better — the right architecture combined with the right model is key.
Anthropic also summarized five multi-agent collaboration patterns: Generator-Verifier, Orchestrator-Subagent, Agent Teams, Message Bus, and Shared State.
Complexity isn’t always better. For simple tasks, Generator-Verifier is sufficient; spinning up a full orchestration is just wasteful.
Multi-agent systems do offer a qualitative leap, but only if you’re clear on three things:
- Is the task complex enough to require parallelism?
- Are the boundaries between subagents cleanly defined?
- Are you willing to bear the 15x token cost?
If you can answer yes to all three, it’s worth pursuing.
Otherwise, a strong model with good prompting is enough.
Similar Articles
@Russell3402: https://x.com/Russell3402/status/2056331558223786416
This article delves into the division of labor design in multi-agent systems, including trigger mechanisms, topology structures, and call chains, analyzing the engineering practices of systems such as Codex, Claude Code, OpenClaw, and Hermes Agent.
Athanor: An Agent-Native System for Autonomous Post-Training Research
Athanor是一个开放的智能体原生系统,使四个Claude Opus 5.5智能体在104小时内自主将Qwen3-4B-Base后训练为跨领域通才模型,在开发集和留出集上均达到甚至超越官方指令微调版本,展示了前沿智能体自主进行AI研究的能力。
@RealYDT: Stop blindly using flagship models as grunts to burn through context anymore—Anthropic just rolled out the most hardcor…
Anthropic为Claude Code推出工业级多智能体协作架构:Haiku 5.5作为并行高速子代理处理机械任务,Sonnet 5.5作为主力生成代码,Opus 5.5仅在关键决策点以--advisor身份介入,通过'三权分立'式分层显著降低旗舰模型的上下文与token消耗。
How we built our multi-agent research system
Anthropic details the architecture and engineering principles behind its new multi-agent research system, highlighting how parallel subagents using Claude Opus 4 and Sonnet 4 significantly outperform single-agent approaches in complex research tasks.
@laobaishare: This is some real gold. Anthropic just shared a super handy Claude Code trick. The idea: use Sonnet, Haiku, and Opus 5.5 together, each doing what it does best. Better results and way fewer tokens, because every task goes to the right model. …
Anthropic shared a multi-model collaboration trick for Claude Code: use Sonnet to host the session and write code, Haiku to search files in parallel, and Opus as an advisor for important decisions — improving results while saving tons of tokens.