Claude Blog: When building Agents, when to fold sub-agents into the main loop; progressive disclosure of Skills is often better than multi-expert orchestration
The Claude Blog discusses when to fold sub-agents into the main loop when building Agents, arguing that on the Claude Platform, a single main loop plus on-demand loading of Skills/tools often yields better quality and lower cost and latency across multiple internal comparisons. The article notes that one sub-agent per team plus aggregate orchestration often replicates the organizational chart, bringing problems such as context loss, Frankenprompts, and localized evals; one customer, when comparing a multi-Agent harness with a single loop, found the latter about 2× faster. Sub-agents are recommended only for scenarios such as parallelism, context bloat, or conflicts between tools and instructions, and the article provides a migration path of first building end-to-end evals and folding in one at a time.
The Claude Blog discusses when to fold sub-agents into the main loop when building Agents, arguing that on the Claude Platform, a single main loop plus on-demand loading of Skills/tools often yields better quality and lower cost and latency across multiple internal comparisons. The article notes that one sub-agent per team plus aggregate orchestration often replicates the organizational chart, bringing problems such as context loss, Frankenprompts, and localized evals; one customer, when compari
Matched fieldsBody
