Anthropic：单智能体优于多子智能体
做法与步骤
- Anthropic 的应用 AI 团队在多个企业部署中发现，使用技能的单个智能体在质量上常优于单体提示设计和多子智能体方案。
- 多子智能体架构会导致延迟增加、成本上升，且每次交接都可能造成信息丢失；一个对比中单智能体架构运行速度约快一倍。
- 许多智能体设计沿袭意图检测、固定流水线、用户分群等模式，而新模型（如 Opus 4.5 等）已能自行处理大部分编排工作。
- Anthropic 警告“智能体 Conway 定律”：架构复制组织图，各团队各自发布子智能体，最终导致数百个重叠智能体和互相矛盾的“Frankenprompt”。
- 建议将工作流打包为技能、通过工具搜索按需加载工具，由小型中央团队负责系统提示和整体质量，并指定技能库维护者以防膨胀。
- 子智能体仍适用于单智能体上下文窗口出现可测量性能下降、需并行运行独立上下文任务、或单智能体难以选择工具的场景。
对实践的启示
做 AI 应用时应优先评估单智能体+按需加载上下文的方案，避免盲目堆叠子智能体；迁移需谨慎验证，防止合并后破坏原有流程。
作者承认的反方与局限
Anthropic 承认子智能体在特定场景下仍有必要，并警告盲目合并可能降低延迟却破坏原有工作流程（如支持智能体案例）。
原文摘引
Anthropic found that a single agent with on-demand context often outperforms multi-agent setups in quality, cost, and latency.
Anthropic warns against merging blindly, since in one test with a support agent, folding in a sub-agent did reduce latency but broke a previously working process.
▸ 展开原文全文（20 段，抓取自 The Decoder）
Anthropic says one AI agent beats many subagents now that models can handle complexity alone
Key Points
- Anthropic recommends that companies evaluate whether they can consolidate sub-agents into a single agent that loads context on demand.
- The company's experience shows that many specialized sub-agents can lead to higher latency, rising costs, and information loss at every handoff.
- Anthropic has published a migration kit on GitHub to help teams make the transition.
Anthropic found that a single agent with on-demand context often outperforms multi-agent setups in quality, cost, and latency. The company is releasing a migration kit to help teams evaluate and make the switch.
Anthropic is recommending that companies evaluate whether they can consolidate sub-agents, because a single primary agent that loads context as needed often delivers better results than a fleet of specialized ones. Newer models starting with Opus 4.5, along with Opus 5.5 and Fable 5.1, can manage complex plans directly in a single loop, which can also reduce costs and wait times. In one comparison, Anthropic says the single-agent architecture ran about twice as fast as the multi-agent setup.
The recommendation comes from hands-on experience across multiple enterprise deployments, where Anthropic's Applied AI team found that a single agent using so-called skills frequently beat both monolithic prompt designs and sub-agent setups on quality. One company, for example, had a dozen specialized sub-agents inside its customer-facing agent, which made it hard to keep a consistent brand experience and hurt usability with high latency.
The model can now do much of the orchestration work itself
According to Anthropic, many agent designs follow a familiar pattern with intent detection, a fixed processing pipeline, user segmentation, separate recommendation branches, and an orchestrator sitting on top. Much of that is work the model can now handle on its own for the respective use case.
Anthropic calls it "Conway's Law" for agents. The architecture becomes a copy of the org chart, with each team shipping its own sub-agent until hundreds of overlapping agents pile up with no shared standards. What follows is what Anthropic calls a "Frankenprompt," where every team adds rules to the system prompt that end up contradicting each other. A clean system prompt, four or five lean data tools, and fixed output guardrails cover much of the respective use case, according to the company.
As one example, Anthropic cut the Claude Code system prompt for newer models by over 80 percent, partly because skills and tools now load only when needed. Newer models also comment on their own progress and check their own work, which can make some of the extra control layers unnecessary.
Anthropic says sub-agents still make sense when a single agent's context window shows measurable performance degradation, when multiple tasks need to run in parallel with separate context windows, or when a single agent struggles with tool selection.
For a step-by-step migration, Anthropic has published a migration kit on GitHub that walks teams through a workflow to identify existing patterns, evaluate alternatives, and verify the best approach. Anthropic warns against merging blindly, since in one test with a support agent, folding in a sub-agent did reduce latency but broke a previously working process. The primary agent started answering on its own instead of consulting the right specialist.
Teams should keep skill libraries from sprawling
Instead of giving every team its own agent, Anthropic recommends packaging workflows into skills and loading tools on demand through a tool search. A small central team should own the system prompt and overall quality. Separately, Anthropic notes that the model's tool selection tends to degrade beyond 30 to 50 tool definitions, so designated owners on each team should maintain the skill libraries to keep them from ballooning.
For reference material like guidelines, product specs, or metric definitions, Anthropic recommends knowledge bases that the agent queries only when needed through a search tool. That kind of information can also be embedded as reference files inside a skill. Anthropic advises against fetching context through code and injecting it directly into prompts.
Anthropic's findings are consistent with recent research. A study by Vals found that agent teams can be faster than single agents but don't deliver higher quality. Scaling from ten to 30 or 100 agents brought no quality gains but significantly higher costs, according to the study. OpenAI developer Eric Provencher has also questioned the value of agent swarms, calling them "almost certainly" wasted money.
AI News Without the Hype – Curated by Humans
Subscribe now