When One Agent Isn’t Enough: Claude Now Builds Its Own Team Of Agents On The Fly

📊 Full opportunity report: When One Agent Isn’t Enough: Claude Now Builds Its Own Team Of Agents On The Fly on ThorstenMeyerAI.com — validation score, market gap, and execution plan.

TL;DR

Anthropic’s Claude has introduced a new feature enabling it to dynamically assemble and manage its own team of agents for complex tasks. This development aims to address limitations of single-agent workflows, improving performance on high-value, multi-step projects. The capability is currently in testing and is not intended for simple tasks.

Anthropic’s Claude has introduced a new feature allowing it to build its own team of agents on the fly for complex, high-value tasks. This capability enables Claude to dynamically orchestrate multiple subagents, each with focused roles, to improve performance on multi-step projects. The development addresses known limitations of single-agent workflows, such as partial work, bias, and goal drift.

The feature, called dynamic workflows, is a programming framework where Claude writes and executes small JavaScript programs to spawn, coordinate, and manage subagents. These subagents can be assigned different models, operate in isolated environments, and resume interrupted tasks. The system can automatically decide which model to use for each subtask and how to organize parallel execution.

According to Anthropic, this capability is particularly useful for complex, high-stakes tasks such as code rewrites, research routines, fact-checking, and large-scale data analysis. The workflow patterns include classify-and-act, fan-out-and-synthesize, adversarial verification, generate-and-filter, tournaments, and loop-until-done. These are common organizational strategies used by human teams but are now automated within Claude.

At a glance
updateWhen: announced March 2024
The developmentClaude now autonomously constructs and orchestrates its own team of subagents during complex workflows, marking a significant evolution in AI orchestration.
Claude Builds Its Own Team: Dynamic Workflows — Insights
AI Dispatch · Insights · 1 July 2026

When one agent isn’t enough: Claude now builds its own team on the fly

Skills package what you know; loops decide how far you delegate over time. Dynamic workflows are the third axis — within a single task, Claude writes its own harness and assembles a temporary team of subagents. Think of it as Claude drawing an org chart for one job.

Why one agent grinding alone underdelivers
Agentic laziness
Declares done on partial work — 35 of 50 review items.
Self-preferential bias
Grades its own homework — likes what it already produced.
Goal drift
Loses the original objective across turns, especially after context is summarized.
These are the failure modes of one person doing a huge job alone. The cure is the manager’s: divide the work, give isolated briefs, and have someone independent check it.
The harness — an org chart Claude writes for one task
Orchestrator
Claude writes a JS harness on the fly
▼   fan out   ▼
Subagent
own context · model
Subagent
own worktree
Subagent
focused goal
Subagent
isolated
✕ adversarial verify
✕ adversarial verify
✕ adversarial verify
✕ adversarial verify
▼   barrier: wait for all   ▼
Synthesize
merge structured outputs
→ Result
one verified answer
Each subagent gets a clean context window and can run on a cheaper or smarter model — so no single overloaded context gets lazy, biased, or lost. Resumable if interrupted.
The six moves it composes
Classify-and-actroute by task type (switchboard)
Fan-out-and-synthesizeparallel agents → a barrier merges (map/reduce)
Adversarial verificationa separate agent attacks each result
Generate-and-filterbrainstorm wide, keep only survivors
Tournamentagents compete; pairwise judging > scoring
Loop-until-donespawn until a stop condition, not a fixed count
Where it earns its keep — often away from code
Big migrations & refactors Deep research → cited report Fact-check every claim Rank 1,000 tickets by severity Root-cause post-mortems (“why did sales drop?”) Triage a backlog at scale Design/naming by rubric Model routing
One security pattern to memorize — quarantine: agents that read untrusted public content are barred from high-privilege actions; a separate agent does the acting. Separation of duties for autonomous agents.
The take

The shift is from prompting a worker to commissioning a team — more output, more cost, and a manager’s judgment required. Reach for a workflow when a task is big, parallel, adversarial, or judgment-heavy — and when you can feel a single agent getting lazy, grading its own homework, or losing the plot. Bound it (token budgets, pilot first) — workflows can spawn hundreds of agents and burn far more tokens. For everything else, don’t hire five people to change a lightbulb.

Source: “A harness for every task: dynamic workflows in Claude Code,” Thariq Shihipar & Sid Bidasaria (Anthropic), Claude blog, 2 June 2026. Mechanics, patterns & use cases are Anthropic’s; the “org chart” framing is the author’s. A recent, still-evolving feature. Docs: code.claude.com/docs.
thorstenmeyerai.com

Implications for AI Workflow Automation

This development represents a significant step in automating complex, multi-step AI tasks. By enabling Claude to autonomously assemble and manage its own team of agents, organizations can potentially handle more sophisticated projects without extensive manual orchestration. It addresses key failure modes of single-agent systems, such as incomplete work, bias, and goal drift, which have limited AI performance in high-stakes environments.

While still experimental, this feature could reshape how AI is integrated into workflows that require layered decision-making, verification, and parallel processing, reducing human oversight and increasing efficiency in complex operations.

AI for Bookkeeping Automation and Workflows: Automate Data Entry, Receipts, Categorization, Reconciliation, and Month-End Reporting Using AI and No-Code Tools, Save Hours Every Week for Bookkeepers

AI for Bookkeeping Automation and Workflows: Automate Data Entry, Receipts, Categorization, Reconciliation, and Month-End Reporting Using AI and No-Code Tools, Save Hours Every Week for Bookkeepers

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Evolution of Multi-Agent AI Systems

Prior to this development, Claude operated mainly as a single-agent system, executing tasks within a fixed context window. Limitations emerged when tasks became lengthy or involved multiple steps, leading to issues like partial completion, bias, and goal drift. Anthropic has been developing techniques to improve this, including skills packages and looping mechanisms, culminating in the new dynamic workflow feature.

This is the third installment in a series of innovations aimed at enabling Claude to better handle complex, multi-step tasks. The capability to write and run custom orchestration scripts marks a shift from static, hand-built workflows to adaptive, self-constructing systems.

“Claude’s ability to autonomously create and manage its own team of agents is a breakthrough in AI orchestration, especially for complex workflows.”

— Thorsten Meyer, AI researcher

Designing Multi-Agent Systems: Principles, Patterns, and Implementation for AI Agents

Designing Multi-Agent Systems: Principles, Patterns, and Implementation for AI Agents

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Current Limitations and Unknowns

It is not yet clear how widely this feature will be adopted outside experimental settings or how it performs in real-world, high-stakes scenarios. Anthropic has cautioned that the system uses more tokens and is designed for complex tasks, not simple fixes like typo corrections. The robustness, safety, and scalability of autonomous team-building remain under evaluation.

Model Context Protocol for LLMs in Action: Build Reliable AI Agents That Access Data, Execute Tasks, and Integrate with Any Platform Without Risk

Model Context Protocol for LLMs in Action: Build Reliable AI Agents That Access Data, Execute Tasks, and Integrate with Any Platform Without Risk

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Upcoming Testing and Integration Phases

Anthropic plans to further test the dynamic workflow capability across diverse use cases, including large-scale research, code development, and data verification. The company may release more detailed guidelines and interface options for organizations interested in deploying this feature. Monitoring performance and safety in operational environments will be key in upcoming months.

The LangGraph Mastery Guide: Orchestrating Multi-Agent AI Workflows for Complex Task Automation

The LangGraph Mastery Guide: Orchestrating Multi-Agent AI Workflows for Complex Task Automation

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

How does Claude decide which agents to create?

Claude writes a small JavaScript program that includes orchestration patterns like classify-and-act or fan-out-and-synthesize, choosing roles based on the task’s structure and complexity.

Is this feature available for all users now?

As of now, the dynamic workflow feature is in testing and is not generally available. It is primarily being evaluated within controlled environments.

What types of tasks benefit most from this capability?

High-value, multi-step tasks such as code rewrites, research synthesis, fact-checking, and large data analysis are the primary focus, where orchestration of multiple agents improves outcomes.

Are there safety concerns with autonomous agent teams?

Anthropic has noted that safety and control are priorities, and the system is designed with safeguards. However, comprehensive evaluation of risks is ongoing.

Source: ThorstenMeyerAI.com

You May Also Like

AmenGate: The Moment Before the Scroll

AmenGate introduces a faith-based prayer lock for iPhone that interrupts phone use with meaningful prayers, aiming to foster mindfulness without shame.

Threlmark: Disk Is the Contract

Threlmark launches a new roadmap method where the roadmap is a plain JSON file on disk, enabling open, interoperable, and durable planning.

The Deploy Button Became the Bottleneck — and Cloudflare Just Bought the Build Step

Cloudflare’s acquisition of VoidZero aims to streamline build-to-deploy workflows, addressing the shift in software development speeds driven by AI coding tools.

IdeaClyst: The Engine That Decides What’s Worth Building

IdeaClyst is launched as an idea engine that transforms rough concepts into validated, targeted product initiatives by analyzing roadmaps and market opportunities.