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 called ‘dynamic workflows,’ allowing the AI to create and manage its own team of subagents for complex tasks. This development aims to improve performance on high-value, multi-step projects by addressing limitations of single-agent approaches.

Anthropic has introduced a new capability in its AI model, Claude, called dynamic workflows. This feature enables Claude to write and run its own orchestration programs to assemble teams of specialized subagents tailored for complex, high-value tasks, without human intervention. The development addresses known limitations of single-agent workflows and aims to improve performance on demanding projects.

The dynamic workflows feature allows Claude to generate small JavaScript programs that coordinate multiple subagents, each with distinct roles and contexts. These subagents can operate in isolation, using different models optimized for specific tasks, and can be resumed if interrupted. The system employs various orchestration patterns, such as classify-and-act, fan-out-and-synthesize, and adversarial verification, mimicking the structure of effective human teams.

According to Anthropic, this capability is particularly useful for complex, high-stakes projects where a single agent might underperform due to issues like partial work, bias, or goal drift. The feature is built to handle tasks like large code rewrites, extensive research routines, and multi-source fact verification, often outperforming traditional single-agent approaches.

At a glance
updateWhen: announced March 2024
The developmentClaude now autonomously constructs and orchestrates its own team of agents for complex tasks, marking a significant upgrade in AI workflow management.
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 Complex AI-Driven Workflows

This development signifies a major step toward more autonomous and effective AI systems capable of managing intricate projects without constant human oversight. By enabling Claude to build its own team, organizations can potentially handle larger, more sophisticated tasks with greater accuracy and efficiency. It also demonstrates a move toward AI that can better mimic human project management and delegation, which could influence future AI development and deployment strategies.

Amazon

AI multi-agent workflow software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Evolution of AI Orchestration and Workflow Management

Anthropic’s Claude has been evolving through a series of features aimed at improving multi-step reasoning and task delegation. Previously, the model relied on static workflows or manual orchestration, which limited its ability to adapt to complex tasks. The introduction of dynamic workflows completes a trilogy of innovations, emphasizing skills packaging, looping, and now, autonomous team-building. This aligns with broader trends in AI toward more flexible, modular, and scalable systems that can handle high-value, multi-faceted projects.

While static workflows have been used in engineering contexts, the ability for Claude to generate custom harnesses on the fly represents a significant leap, especially for non-technical applications like research, fact-checking, and code refactoring. The feature was shipped alongside Claude Opus 4.8, leveraging recent advances in model reasoning capabilities.

“Claude’s ability to autonomously assemble its own team of subagents marks a new milestone in AI orchestration, enabling more reliable and scalable complex workflows.”

— Thorsten Meyer, AI researcher at Anthropic

Amazon

JavaScript automation tools for AI

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unanswered Questions About Reliability and Limitations

It is not yet clear how well Claude’s self-assembled teams perform across a broad range of real-world tasks or how they compare to human teams in accuracy and efficiency. The scalability of this approach for large-scale enterprise use remains untested, and potential limitations, such as token costs and system robustness, are still being evaluated.

Amazon

AI orchestration platforms

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Deployment and Evaluation

Anthropic plans to conduct further testing of the dynamic workflows feature across diverse applications, including software development, research, and compliance monitoring. They will also gather user feedback to refine the orchestration patterns and improve reliability. Broader adoption and integration into enterprise workflows are expected to follow as the system matures.

Amazon

complex project management AI tools

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 generates small JavaScript programs called workflows that specify how to spawn, coordinate, and manage multiple subagents, each with a focused role and context.

What kinds of tasks benefit most from this feature?

High-value, complex tasks such as large code rewrites, multi-source research, and detailed fact verification are most suited to dynamic workflows.

Are there any limitations or risks?

The system uses more tokens and computational resources, and its performance across diverse real-world scenarios is still being evaluated. Reliability in unpredictable environments remains an open question.

Will this feature be available to all users?

It is currently in the experimental or early deployment phase, with broader availability planned as testing progresses.

How does this compare to static workflows?

Unlike static workflows, which are pre-built and fixed, dynamic workflows are generated on demand by Claude, allowing tailored orchestration for specific tasks.

Source: ThorstenMeyerAI.com

You May Also Like

Single Digits: The April That Closed the Open-Weight Gap

The benchmark gap between open and closed AI models has fallen to single digits in April 2026, reshaping enterprise AI economics and strategies.

Minerva. The opposite path.

Italy’s Minerva LLM, trained from scratch on 2.5 trillion tokens, shows impressive performance but scores just 4.9% on Italian school exams, raising questions on native-language investment.

ALIA. The Spanish answer.

Spain unveils ALIA, a 40B multilingual LLM trained on 9.37 trillion tokens, marking Europe’s largest public AI project with strategic positioning implications.

AI Is the Alibi. The Reorg Is the Signal.

Coinbase’s recent layoffs are officially linked to AI-driven restructuring, but underlying market pressures suggest the true driver is crypto downturn and cost-cutting.