📊 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 AI now creates and manages its own team of specialized agents during task execution. This new feature, called dynamic workflows, aims to improve handling of complex, high-value tasks by orchestrating multiple sub-agents in real time.

Anthropic’s Claude AI now dynamically builds its own team of specialized agents during task execution, a feature called dynamic workflows. This development allows Claude to orchestrate multiple sub-agents on the fly, improving performance on complex, high-value tasks. The capability addresses limitations of single-agent approaches, such as partial work, bias, and goal drift, by enabling more structured and independent sub-processes.

The dynamic workflows feature enables Claude to generate small JavaScript programs that orchestrate sub-agents, each with dedicated roles and context windows. These sub-agents can operate in isolated environments, use different models suited for specific tasks, and communicate through a custom-built harness. This approach simulates a team of specialists working together, which is particularly useful for tasks requiring parallel processing, verification, or competitive approaches.

Anthropic emphasizes that this capability is resource-intensive, using more tokens and being suited for complex, high-stakes work rather than simple corrections. The system can decide which model to deploy for each subtask, and it can pause and resume workflows, adding flexibility. The six orchestration patterns include classify-and-act, fan-out-and-synthesize, adversarial verification, generate-and-filter, tournament, and loop-until-done, mirroring common team strategies for managing complex projects.

At a glance
updateWhen: announced recently, with ongoing develo…
The developmentClaude has introduced a new capability to assemble and coordinate its own team of agents dynamically for complex tasks, marking a significant advancement 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 and Complex Task Management

This advancement represents a significant step toward more autonomous and reliable AI systems capable of managing intricate workflows. By enabling Claude to assemble and coordinate its own team of agents, organizations can tackle more sophisticated problems, such as comprehensive research, multi-step verification, and large-scale automation. This reduces reliance on human oversight for every step, potentially increasing efficiency and accuracy in high-value tasks.

However, the increased resource consumption and complexity mean that this feature is best suited for specialized applications rather than everyday use. It also raises questions about control, transparency, and the potential for unintended interactions among sub-agents.

AI Task Orchestration: Coordinating Complex Agent Workflows. A Comprehensive Guide to Building, Deploying, and Operating Multi-Agent AI Systems

AI Task Orchestration: Coordinating Complex Agent Workflows. A Comprehensive Guide to Building, Deploying, and Operating Multi-Agent AI Systems

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Evolution of AI Orchestration Techniques

Previous iterations of Claude focused on single-agent workflows, which proved limited for long or complex tasks, suffering from issues like partial work, bias, and goal drift. Anthropic’s development of dynamic workflows builds on earlier innovations, such as skills packaging and looping, by introducing real-time agent assembly. The concept aligns with broader trends in AI toward more modular, multi-agent systems capable of handling complex, multi-faceted problems.

This development follows earlier announcements of Claude’s ability to reason about tasks and now extends that capability into real-time orchestration. The feature was enabled by advances in model reasoning, particularly with Claude Opus 4.8, which allows the system to write and run custom JavaScript programs for task management.

“Claude’s ability to build and manage its own team of agents on the fly marks a new frontier in AI orchestration, enabling more reliable and complex workflows.”

— Thorsten Meyer, AI researcher

Limitations and Risks of On-the-Fly Agent Teams

It is not yet clear how well the system performs in real-world, high-stakes scenarios at scale, or how transparent and controllable the interactions among sub-agents remain. The resource costs and complexity could limit widespread adoption, and potential unintended behaviors are still under investigation. Further testing is ongoing to evaluate robustness and safety.

Deployment and Evaluation of Dynamic Workflows in Real Tasks

Anthropic plans to expand the deployment of dynamic workflows across various applications, including research, verification, and automation. Future updates will focus on refining the orchestration patterns, improving efficiency, and establishing best practices for managing complex multi-agent systems. Monitoring and safety assessments will be key to ensuring reliable operation in production environments.

Key Questions

How does Claude build its own team of agents?

Claude writes and runs small JavaScript programs that spawn and coordinate sub-agents, each with specific roles and context windows, effectively creating a team tailored to the task at hand.

What types of tasks benefit most from dynamic workflows?

Complex, multi-step, high-value tasks such as research synthesis, verification, and large-scale automation are most suited, where dividing work among specialized agents improves accuracy and efficiency.

Does this increase resource consumption significantly?

Yes, dynamic workflows use more tokens and computational resources, making them more suitable for specialized, high-stakes applications rather than simple tasks.

Are there risks associated with this approach?

Potential risks include unpredictable interactions among sub-agents, reduced transparency, and higher resource costs. Ongoing testing aims to mitigate these concerns.

What is the next step for this technology?

Anthropic plans to deploy and evaluate dynamic workflows in real-world scenarios, refine orchestration patterns, and develop safety protocols for broader adoption.

Source: ThorstenMeyerAI.com

You May Also Like

Évian and the Fallout: What Europe Actually Wants From Amodei, Hassabis, and Altman

Europe pushes for reliable access, sovereignty, and safety standards from Amodei, Hassabis, and Alt after US AI export controls at G7 summit.

Community volunteer action tracker for local boards

A new volunteer action tracker for local boards is set to be tested as a tool to improve follow-up on community projects, starting with a pilot workflow.

Cuatro De Julio

Independence Day celebrations took place nationwide on July 4th, with increased security measures amid reports of isolated incidents, according to authorities.

Technology Operations Signal Monitor: Explanation Of Everything You Can See In Htop/top On Linux (2019)

A detailed explanation of what the ‘h’ key displays in Linux system monitoring tools like htop and top, and its significance for developers.