Artificial Intelligence
Anthropic urges single-agent designs over sub-agents
Anthropic said companies should test whether one agent with on-demand context can replace multiple sub-agents, and said a migration kit on GitHub could help teams assess the change.
- Anthropic said companies should evaluate whether several sub-agents can be consolidated into one primary agent that fetches context when needed.
- The company said its single-agent approach often delivered better quality, lower cost and lower latency, and said one comparison ran about twice as fast.
- Anthropic said newer models including Opus 4.5, Opus 5.5 and Fable 5.1 could handle complex plans in a single loop.
- Anthropic published a migration kit on GitHub and said sub-agents still made sense in some cases, including parallel work and context-window limits.
- The article said a Vals study found no quality gains from scaling agent teams and quoted OpenAI developer Eric Provencher as doubting agent swarms.
Anthropic recommended that companies check whether they could replace several specialist sub-agents with one lead agent that loads context only when needed. It said newer models, beginning with Opus 4.5 and including Opus 5.5 and Fable 5.1, could manage complex plans directly and could reduce cost and waiting time.
The company said its advice came from enterprise deployments examined by its Applied AI team. In one example, it said a customer-facing system used a dozen specialist sub-agents, which made brand consistency harder to maintain and increased latency.
Anthropic said some multi-agent designs still had a place when a single agent's context window degraded, when tasks had to run in parallel, or when tool selection became unreliable. It also said that on newer models it had cut the Claude Code system prompt by more than 80 percent because skills and tools could now be loaded only when needed.
To help teams change architectures, Anthropic released a migration kit on GitHub that walked users through identifying existing patterns, comparing alternatives and checking the result. The company also said teams should keep skill libraries from growing too large and warned that tool selection tended to worsen beyond 30 to 50 tool definitions.
The article said Anthropic's view aligned with recent research. It cited a Vals study that found no quality improvement from larger agent teams and quoted OpenAI developer Eric Provencher as questioning the value of agent swarms.
Named in this story
People
- Eric Provencher
- questioned the value of agent swarms
Companies
- Anthropic
- recommended that companies consider moving from sub-agents to one primary agent
- GitHub
- hosted Anthropic's migration kit
- Vals
- produced a study Anthropic cited on agent teams and quality
- OpenAI
- was named in a comment from its developer Eric Provencher
Organisations
- Applied AI team
- at Anthropic found single agents often outperformed other designs in enterprise deployments
Products and systems
- Opus 4.5
- one of the newer models Anthropic said can manage complex plans directly
- Opus 5.5
- one of the newer models Anthropic said can manage complex plans directly
- Fable 5.1
- one of the newer models Anthropic said can manage complex plans directly
- Claude Code
- had its system prompt cut by over 80 percent, according to Anthropic
How the source tells it
The article is a technical advisory in a mildly promotional register, leaning on Anthropic's own terminology and performance claims.
- vendor boosterism the piece foregrounds the company's self-assessment and performance comparisons as the main basis for the recommendation