When One Agent Isn’t Enough: Claude Now Builds Its Own Team Of Agents On The Fly
AIThis post was created with the assistance of artificial intelligence (AI).

📊 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 added a feature called dynamic workflows, allowing it to assemble and coordinate its own team of agents for complex tasks. This development aims to address limitations of single-agent approaches in handling large, multi-faceted projects.

Anthropic’s Claude has introduced a new feature called dynamic workflows, enabling the AI to autonomously assemble and manage a team of agents tailored for specific complex tasks. This development enhances Claude’s ability to handle high-value, multi-step projects more effectively, addressing limitations observed in single-agent workflows.

The feature allows Claude to write and execute small JavaScript programs that orchestrate multiple subagents, each with its own focused brief and context window. These subagents can be assigned different roles, such as dispatchers, specialists, or independent reviewers, to improve task accuracy and efficiency.

According to Anthropic, this approach is particularly useful for complex tasks that involve parallel processing, verification, or iterative refinement. The system can decide which model to deploy for each subtask and whether to run agents in isolated worktrees, preventing interference among parallel processes. The process is dynamic, with Claude capable of resuming interrupted workflows and customizing the harness for specific jobs, such as rewriting code or conducting in-depth research.

At a glance
updateWhen: announced recently, ongoing implementat…
The developmentClaude now dynamically builds and orchestrates its own team of agents during task execution, marking a significant upgrade in its capability to handle complex workflows.
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-Driven Project Management

This development signifies a shift toward more autonomous and scalable AI systems capable of managing complex workflows without constant human oversight. By building its own team of agents, Claude can better handle tasks that require multiple perspectives, verification, and iteration, making it more suitable for high-stakes or high-value applications.

For organizations, this could mean more reliable AI-assisted project execution, reduced need for manual orchestration, and increased capacity for handling large or multi-faceted tasks. However, it also raises questions about control, transparency, and the potential for unforeseen interactions among autonomous subagents.

Building AI Agents for Network Operations: Design LLM-powered NetOps workflows with Python, Ollama, MCP, and tool calling

Building AI Agents for Network Operations: Design LLM-powered NetOps workflows with Python, Ollama, MCP, and tool calling

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Evolution of Multi-Agent AI Capabilities

This is the third major update from Anthropic’s Claude development, following earlier enhancements in skills packaging and loop-based delegation. Previously, single-agent models faced limitations such as agent laziness, bias, and goal drift, especially in long or complex tasks.

The introduction of dynamic workflows addresses these issues by enabling Claude to create task-specific agent teams, each focused on a particular aspect of a project. This mirrors human team management strategies, such as dividing work, independent review, and iterative refinement, but now automated within the AI itself.

While static multi-agent setups were possible through hand-coded harnesses, the new capability allows Claude to generate tailored orchestration programs dynamically, increasing flexibility and efficiency.

“This feature represents a significant step toward autonomous AI systems capable of managing complex workflows without human intervention.”

— Thorsten Meyer, AI researcher

Amazon

multi-agent AI system tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unanswered Questions About Workflow Reliability

It is not yet clear how well Claude’s autonomous team management performs in real-world, high-stakes scenarios. The limits of its ability to coordinate multiple agents without human oversight, especially in unpredictable or adversarial environments, remain to be tested.

Additionally, concerns about transparency, control, and potential unintended interactions among subagents are still under discussion, with no definitive assessments available.

Amazon

JavaScript programming for AI orchestration

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps in Deployment and Evaluation

Anthropic is expected to roll out this feature to select users for pilot testing, focusing on high-complexity projects such as large codebases, research synthesis, and automated verification. Monitoring and evaluating performance, safety, and control will guide further refinements.

Further updates may include improved user controls, transparency features, and expanded capabilities for managing multi-agent workflows across different domains.

Amazon

AI task management platforms

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

How does Claude build its own team of agents?

Claude writes and runs small JavaScript programs called workflows that orchestrate multiple subagents, each with a specific role, to handle different parts of a task.

What types of tasks benefit most from this feature?

Complex, multi-step projects such as code rewriting, research synthesis, verification, and large-scale data analysis benefit most, especially where parallel processing and independent review improve outcomes.

Are there any limitations or risks associated with this approach?

Potential risks include coordination failures, unintended interactions among subagents, and reduced transparency. Performance in unpredictable environments is still being evaluated.

When will this feature be available more broadly?

Anthropic plans to pilot the feature with select users soon, with broader deployment depending on initial testing results and safety assessments.

Source: ThorstenMeyerAI.com

You May Also Like

How AI Could Rebuild the Value of Translation Hardware

AIThis post was created with the assistance of artificial intelligence (AI).AI can…

The Trade-offs Of Using Four Bits In AI Quantization

Analyzing the impact of 4-bit quantization on AI models, including performance loss, benefits, and remaining uncertainties.

DeepSWE – The benchmark that made the models spread out again

DeepSWE, released May 2026, reveals wider gaps among AI coding models, challenging previous benchmark reliability and highlighting measurement flaws.

Speculations Concerning The First Ultraintelligent Machine (1965) [Pdf]

Examining the 1965 speculative paper on ultraintelligent machines, its claims, context, and significance for AI development.