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 launched a new feature called dynamic workflows, enabling it to assemble and orchestrate its own team of subagents for complex tasks. This development addresses limitations of single-agent approaches and aims to improve handling of high-value, multi-step projects.

Anthropic’s Claude has introduced a new feature called ‘dynamic workflows,’ allowing the AI to automatically assemble and manage a team of subagents tailored to complex tasks. This development addresses longstanding challenges in AI performance on multi-stage projects and enhances the model’s ability to handle high-value work without human intervention.

The feature, part of Anthropic’s ongoing efforts to improve AI orchestration, enables Claude to write and execute small JavaScript programs that create and coordinate multiple subagents. Each subagent can have a specialized role, such as data classification, verification, or synthesis, and can operate in isolation to avoid common AI failure modes like goal drift or bias.

According to Anthropic, this approach is particularly useful for high-stakes, complex tasks that exceed the capabilities of a single agent working within a limited context window. The system can choose different model sizes for different sub-tasks and can resume interrupted workflows, making it adaptable to various scenarios.

While technically sophisticated, the company emphasizes that this feature is not intended for simple tasks such as fixing typos, but rather for projects requiring multiple steps, independent verification, and strategic orchestration — akin to a human team lead managing specialists.

At a glance
reportWhen: announced March 2024
The developmentClaude now dynamically constructs and manages its own team of specialized agents during task execution, marking a significant upgrade in AI orchestration capabilities.
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 Performance in Complex Tasks

This development marks a significant step forward in AI capabilities, enabling models like Claude to manage multi-faceted projects more effectively. By autonomously creating specialized subagents, Claude can mitigate common failure modes such as partial work, bias, and goal erosion. This could lead to more reliable AI applications in research, software development, and enterprise workflows, where complex, layered tasks are common.

However, the increased computational cost and token usage mean this approach may be limited to high-value or critical projects, rather than everyday use cases. The ability to dynamically orchestrate teams also raises questions about transparency and control, as users may have less direct oversight of the process.

Mastering Microsoft 365 Copilot in Teams: End the Meeting Madness: Automate Transcripts, Summaries, and Task Management (Microsoft 365 Copilot Mastery Series Book 3)

Mastering Microsoft 365 Copilot in Teams: End the Meeting Madness: Automate Transcripts, Summaries, and Task Management (Microsoft 365 Copilot Mastery Series Book 3)

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Evolution of AI Orchestration Techniques

Anthropic’s introduction of dynamic workflows builds on prior advancements in modular AI design, including skills packages and looping mechanisms that enable models to delegate tasks over time. This is part of a broader trend toward more autonomous and flexible AI systems capable of managing complex projects without constant human input.

Previous efforts focused on static workflows or hand-coded orchestrations, but the new ‘dynamic’ approach allows Claude to generate custom harnesses tailored to each task, increasing efficiency and adaptability. The feature was developed alongside Claude Opus 4.8, which enhances reasoning and planning capabilities.

This marks the third in a series of innovations aimed at making AI more like a team leader, capable of assembling and managing a team of specialists on the fly, rather than relying on a single agent to handle all aspects of a project.

“This feature allows Claude to write its own orchestration scripts, effectively building a team of agents tailored to complex tasks, which was previously not possible.”

— Thorsten Meyer, AI researcher at Anthropic

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.

Remaining Questions About Implementation and Limitations

It is not yet clear how well this system performs at scale across diverse real-world tasks or how it handles unexpected interruptions. The computational costs and token usage are also unknown, which may limit its applicability outside high-value projects. Further testing is needed to understand its robustness, transparency, and potential risks in deployment.

21 KEYS to AI ORCHESTRATION: How to lead your team to embrace change: A practitioners playbook for leaders Practical strategies to navigate AI implementation foster innovation transform organizations

21 KEYS to AI ORCHESTRATION: How to lead your team to embrace change: A practitioners playbook for leaders Practical strategies to navigate AI implementation foster innovation transform organizations

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Adoption and Evaluation

Anthropic plans to continue testing the feature in various domains, including research, software engineering, and enterprise workflows. They are also likely to explore user feedback and performance metrics to refine the orchestration mechanisms. Broader deployment and integration with existing tools are expected to follow as the technology matures.

AI WORKFLOW AUTOMATION BLUEPRINT SYSTEM: Design Intelligent AI Workflows, Build Automation Systems, Create AI Agents, and Automate Marketing, Sales, Content, and Business Operations

AI WORKFLOW AUTOMATION BLUEPRINT SYSTEM: Design Intelligent AI Workflows, Build Automation Systems, Create AI Agents, and Automate Marketing, Sales, Content, and Business Operations

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 spawn and coordinate multiple subagents, each with specific roles tailored to the task.

What types of tasks benefit most from dynamic workflows?

High-value, multi-step projects that require independent verification, parallel processing, or strategic orchestration are ideal candidates.

Does this increase the cost of running Claude?

Yes, the approach uses more tokens and computational resources, which may limit its use to critical or complex projects.

Is this feature available for all users now?

It is currently in testing and may be rolled out gradually, with broader availability depending on further evaluation.

Are there risks associated with autonomous team-building by AI?

Potential risks include reduced transparency, difficulty in oversight, and unintended bias or errors in complex orchestrations. Ongoing monitoring will be essential.

Source: ThorstenMeyerAI.com

Nothing in this article is financial or investment advice. Cryptocurrency and precious-metal investments carry significant risk — do your own research and consider a licensed advisor.
You May Also Like

Data: The One Thing You Can’t Rent

In 2026, data scarcity and fencing have shifted AI’s competitive edge from compute to proprietary, verified human-made data, reshaping industry dynamics.

A Skill Is a Folder, Not a Prompt: What Anthropic Learned Running Hundreds of Them

Anthropic reveals that effective AI Skills are structured as folders containing instructions, scripts, and assets, transforming organizational workflows.

The clause. How a contractual definition of AGI met the capital built on top of it.

The contractual definition of AGI in the 2019 Microsoft-OpenAI agreement was gradually defused over two amendments, transforming from a doomsday trigger into a procedural checkpoint.

Mac vs GPU Tower for Local LLMs: The Heat-and-Noise Tradeoff

Comparison of Mac Studio M3 Ultra and GPU towers reveals distinct heat, noise, and capacity tradeoffs for local large language model inference.