Anthropic's Applied AI team says many enterprise agents should fold subagents into one loop

Anthropic says that across several enterprise deployments it compared, "a single agent with skills frequently outperformed both the one-prompt-for-everything design and the subagent design on quality," often at lower cost and latency. It lists the failure modes it sees in large organizations: subagent sprawl, a system prompt every team adds to, and evals tuned to each team's own subtask. It still recommends subagents for parallel work, for fresh context windows, and when a single loop degrades from context bloat or tool confusion.

The article gives a migration order: build a small end-to-end eval first, then fold in one subagent at a time and keep it only if the folded version scores worse. It also warns that folding one subagent into another lowered latency but broke a process that had been passing. The evidence is the vendor's own and is not quantified: it cites one unnamed customer that saw "a roughly 2x faster runtime" with a single loop, and says it cut Claude Code's system prompt by over 80%, with no data in the article.

Why it matters: The practical part is the procedure, not the headline claim: fold one subagent at a time against a fixed eval, run each task more than once, and compare which tasks flipped rather than the average score. Treat the performance claims as Anthropic's position until someone publishes numbers.