R132 · Agent architecture › Multi-agent coordination

Fold subagents into the main loop: one agent, progressive disclosure, fewer handoffs

Read the original

multi-agentsubagentsagent-harnessskillscontext-engineering

Source: Anthropic, "Building agents: When to fold subagents into your main agent loop" (Diane Sarkis, claude.com resources, 2026-10-22); highlighted by Ethan Mollick on LinkedIn (2026-11-17), who reads it as a call to rethink many company-built agent harnesses. The article draws on Anthropic's Applied AI team's enterprise deployments. Its comparisons are described, not published as a dataset.

The claim

In many enterprise deployments, a single agent with skills beat both a one-giant-prompt design and an orchestrator-plus-subagents design on quality, often at lower cost and latency per task. One customer saw roughly 2x faster runtime moving from a multi-agent harness to a single loop. Many proposed architectures (intent classifier, fixed multi-step pipeline, user-segment buckets, recommendation branches, orchestrator on top) were doing work the model no longer needs done for it. Often one clear system prompt, four or five thin data tools and firm output guardrails cover most of the use case.

Why multi-agent designs go wrong in large organizations

The common path: each team builds its own agent for its capability, then a platform team puts an orchestrator on top, so the architecture mirrors the org chart (Conway's law). The article names five costs:

When subagents still earn their place

If you do split, divide by context, not by problem type: give each subagent work that needs little from the rest of the system and returns a compact result (independent research paths, components with clean interfaces, black-box verification). Splitting by problem type creates a "telephone game" where each handoff loses fidelity.

Why now

The article's argument is model capability. Since Opus 4.5, models manage far more in one loop than teams expected; current models always think, narrate progress and check their work, which makes some harness elements redundant. Simpler loops also migrate more easily to the next model. Rigid multi-agent structures were often what stopped a new model from doing more of the work.

Tradeoffs

Failure modes to watch

Review checklist

Connections

See R132 on the knowledge map

Part of the Research notes on nowucca.com. Figures and claims are the source's own unless the summary says otherwise.