Level 06

Teams of Agents

Agents divide, coordinate, or review work across separate contexts. A coordinator can combine their findings, and the agents may use the same model or different models. Coordination adds overhead, and separate reviewers can still make correlated mistakes.

Level 06

Who decides the next stepSeveral agents coordinate, delegate, or review work; they can use the same underlying model.
Techniques

What is at this level

Agents coordinate work

Lead agent and workers

Sourced

A lead agent splits the task and hands parts to other agents.

Agent graphs

Sourced

Describing a team of agents and how work passes between them.

Review and debate

Sourced

Agents that check, or argue with, each other's work.

Upgrade conditions

When something here is not enough

Each line names the failure that justifies moving to a higher level.

Lead agent and workers → Long-running tasks

The task cannot finish inside one bounded team run and has to pick up again across separate sessions.

Agent graphs → Organizations of agents

The roster of agents itself has to change while the work is in progress, not stay fixed for one run.

Review and debate → Always-on assistants

The checking has to run continuously against everything a standing assistant does, not once against one finished draft.

Recipes

Jobs that top out here

Each one needs this level and no higher, and says why.

Level 1 + Level 3 + Level 6

Grade against a rubric, with a second reader

Two independent reviewers apply the same rubric. Disagreements go to the teacher rather than being averaged away.

This example uses level 6
↗
Out there

Named products, tools and models

Names listed 09/19/2026. 223 of 223 registry entries have been checked against the maker's own page; the registry marks the rest as unchecked.

Products that work this way6
  • Claude Code subagentsAnthropic · multi-agent feature of a coding agent
  • Claude ResearchAnthropic · research agent
  • Devin DesktopCognition · coding agent in an editor · formerly Windsurf
  • Grok BuildSpaceXAI · coding agent
  • Grok HeavySpaceXAI · several agents answering one question
  • MuseMeta · always-on agent
Tools for building it10
  • Agent Development KitGoogle · agent framework
  • Agent2Agent (A2A) Protocolopen standard · protocol between agents
  • AutoGenMicrosoft · multi-agent frameworkSuperseded by Microsoft Agent Framework
  • Claude Agent SDKAnthropic · agent framework
  • CrewAICrewAI · multi-agent framework
  • Deep AgentsLangChain · agent harness
  • LangGraphLangChain · graph framework
  • Microsoft Agent FrameworkMicrosoft · multi-agent framework
  • OpenAI Agents SDKOpenAI · agent framework
  • Strands AgentsStrands Agents · agent harness SDK
Frontier

What is still unsolved here

Open problems at this level, what people are trying, and the source each rests on. Read 09/19/2026. This block ages faster than the rest of the page, and nothing in it predicts which approach wins.

Run the workers one at a time and the lead waits on the slowest one and cannot steer any of them mid-task. Run them at once and you take on keeping their results, their state and their errors consistent. Nobody has both.

What people are trying

Anthropic runs subagents one at a time today because it is the easier half to coordinate, and treats concurrent execution as worth having once the coordination problems are handled rather than as something already solved.

  • How we built our multi-agent research system · Anthropic · read 09/19/2026
    But this asynchronicity adds challenges in result coordination, state consistency, and error propagation across the subagents.

    Dated June 2025. It is still the maker's own account of this architecture, and nothing newer from them supersedes it.

Where it bites: Lead agent and workers

When one agent hands a task to another, the authorization to act on it often travels with the task. Passed in band, that credential is visible to every agent in the chain and not only to the one it was meant for.

What people are trying

The Agent2Agent specification asks that a credential be bound to the agent that originated the request, and encrypted when it carries anything sensitive, so only that agent can use it. Its own preference is to deliver credentials out of band rather than through the chain at all.

  • Agent2Agent (A2A) Protocol Specification · Agent2Agent Protocol Project, Linux Foundation · read 09/19/2026
    In-band credential exchange can allow credentials to be passed across chains of multiple A2A agents, exposing those credentials to each agent participating in the chain.

Where it bites: Agent graphs

Asking several models to review the same work looks like several opinions and is not. Their mistakes are correlated, so a panel carries a fraction of the independent judgment its size suggests, and one measurement found nine judges worth about two independent votes.

What people are trying

Measuring a panel against what genuinely independent voting would give, rather than assuming more reviewers means more reliability, and testing whether cleverer ways of combining votes recover the difference. In that measurement they mostly did not.

Where it bites: Review and debate

← Level 05 · Agent loops

Pages at this level last reviewed 09/19/2026. Pages unreviewed for 90 days are flagged for another pass. Markdown version of this page