跪拜 Guibai
← All articles
Backend · AI Programming · Agent

Claude's New Guidance: Ditch Subagents for a Single Agent Loop

By cxuanAI ·
Read original on juejin.cn ↗ Google Translate ↗ Alt translation

Multi-agent orchestration is the default in many enterprise stacks, but Anthropic's measurements show it doubles latency and loses detail to lossy summaries. This guidance hands teams a practical migration path: fold subagents into the main loop, move business logic into Skills and tools, and let one model hold the whole context.

Summary

Anthropic's Applied AI team has been measuring enterprise deployments and now says the common multi-agent pattern, an orchestrator coordinating domain-specific subagents, mostly fails in production. A single agent with a few Skills and four or five lightweight tools, protected by guardrails, beats both universal-prompt and subagent schemes on quality while cutting cost and latency. Their customers measured the single Agent + Loop architecture at roughly twice the speed of multi-agent frameworks.

The mechanism behind this is progressive disclosure: agents see only short descriptions of Skills and tools up front, and load full definitions through Tool Search only when needed. That removes the main reason teams split work across subagents, the context limit, and lets one model keep a coherent global context across the whole task. Claude Code has already cut system prompts for stronger models by over 80% using this approach.

Migration involves merging domain subagents into the main loop, converting prompts into Skills, API calls into MCP tools, and evaluating each merge with end-to-end tests. Ownership moves from agents to Skills and tools, with a core team guarding system prompt quality. Anthropic names the failure modes it keeps seeing: subagent proliferation, patchwork prompts, local unreviewed evals, and lossy summaries between agents, which it diagnoses as Conway's Law and a telephone game.

Takeaways
— Anthropic found that a single agent with multiple skills outperforms both universal-prompt and subagent schemes across enterprise deployments on quality, cost, and latency.
— Tool selection degrades when system prompts expose more than 30 to 50 tool definitions.
— Claude Code cut system prompts for stronger models by more than 80%, including through progressive disclosure.
— Anthropic customers measured the single Agent + Loop architecture as roughly twice as fast as multi-agent frameworks.
— Anthropic recommends a clear prompt plus four or five lightweight tools and guardrails to cover most application scenarios.
— During migration, convert subagent prompts into Skills and API calls into MCP tools, then evaluate with and without the subagent.
— When merging subagents, look at which specific tasks flip results, not just final scores.
— Subagents remain useful for context bloat, parallel disposable tasks, and tool-selection or conflicting-system-prompt cases.
— Anthropic suggests starting multi-agent architecture with generator -> verifier or Orchestrator -> subagent patterns, and dividing boundaries by context not problem type.
Conclusions

The advice to move decisions from harness to model implies the orchestration layer will thin out as model capacity grows, but guardrails still have to live somewhere, and Anthropic puts them inside tools rather than in standalone agents.

Conway's Law critique is the sharpest practical point: when agent boundaries mirror team boundaries, information loss is not a bug in the model but a structural consequence of the architecture.

Anthropic's own toolkit promotion muddies the message, but the underlying claim, that a single loop with progressive disclosure removes the main reason for subagents, is testable with their own eval approach.

Concepts & terms
Subagent
A subordinate agent with its own context window, tools, and instructions, scheduled by a coordinator. Anthropic now suggests folding most subagents into the main loop to avoid lossy summaries and latency.
Progressive disclosure
A technique that shows agents only short descriptions of Skills and tools up front, loading full definitions only when needed, reducing context bloat and letting one agent handle many tasks.
Tool Search
A mechanism for discovering and loading tool definitions on demand, as opposed to putting all tool schemas into the model context. It sits alongside Tool Use, which handles the actual invocation.
Conway's Law
The idea that system architecture mirrors the communication structure of the organization that builds it. In agent design, it shows up as one subagent per team, creating telephone-game information loss.
Harness
The external framework that coordinates model calls, tool execution, and loop control. Anthropic expects many harness components to become redundant as models make more decisions themselves.
Source: juejin.cn ↗ Google Translate ↗ Backup ↗