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

Claude has launched a new feature called dynamic workflows, enabling it to create and orchestrate multiple agents on the fly for complex tasks. This innovation aims to address limitations of single-agent approaches in high-stakes scenarios.

Claude has introduced a new feature called dynamic workflows, allowing the AI to automatically build and coordinate a team of agents on the fly for complex tasks. This development enhances its ability to handle high-value projects that require multiple specialized sub-tasks, addressing previous limitations of single-agent workflows.

The feature, part of Anthropic’s ongoing advancements, enables Claude to generate small JavaScript programs that orchestrate a team of agents, each with a focused brief and possibly different model configurations. This process is initiated when a user requests a workflow or uses the keyword ‘ultracode.’

Under the hood, Claude writes and executes these custom scripts, which can spawn agents for various orchestration patterns such as classify-and-act, fan-out-and-synthesize, adversarial verification, generate-and-filter, tournament, and loop-until-done. These patterns mirror traditional team management techniques, like routing tasks, parallel processing, independent review, and managing a team of AI agents.

Anthropic emphasizes that this approach is especially useful for complex, high-stakes tasks, where single-agent execution often leads to issues like incomplete work, bias, or goal drift. The system can decide which model to use for each subtask, whether to run agents in isolated environments, and whether to manage your AI project team effectively, making it highly adaptable.

At a glance
breakingWhen: announced in recent updates, currently…
The developmentClaude now autonomously assembles and manages a team of agents dynamically to handle complex, high-value tasks, marking a significant upgrade in its operational 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 of Autonomous Agent Team Building

This innovation significantly enhances the capabilities of AI in handling complex, multi-faceted projects, reducing errors caused by agent laziness, bias, or goal drift. It allows Claude to perform tasks previously requiring human oversight or multiple manual interventions, potentially transforming workflows in research, development, and operational settings.

For organizations, this means more reliable, scalable, and adaptable AI-driven processes, especially in areas like code development, fact-checking, research synthesis, and support ticket prioritization. The ability to dynamically assemble specialized subagents could lead to more efficient and accurate outcomes in high-value tasks.

The AI-Driven Software Team: A Practical Guide for Developers, Leaders, and Businesses Preparing for AI in Engineering

The AI-Driven Software Team: A Practical Guide for Developers, Leaders, and Businesses Preparing for AI in Engineering

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Evolution of Multi-Agent AI Systems

Earlier iterations of Claude relied on single-agent workflows, which faced limitations in managing long, complex, or adversarial tasks. Prior developments included static multi-agent setups, where developers manually wired agents together using SDKs. The new dynamic workflow feature automates this process, enabling Claude to generate custom orchestration scripts tailored to each task.

This approach builds on previous research into agent orchestration, looped workflows, and modular AI components. The recent launch aligns with ongoing trends toward more autonomous, adaptable AI systems capable of managing complex projects with minimal human intervention.

“Claude’s dynamic workflows represent a leap in autonomous orchestration, allowing the model to create tailored agent teams for complex tasks in real time.”

— Thorsten Meyer, AI researcher at Anthropic

Design Multi-Agent AI Systems Using MCP and A2A: Engineer your own Python-based agentic AI framework with tool use, memory, and multi-agent workflows

Design Multi-Agent AI Systems Using MCP and A2A: Engineer your own Python-based agentic AI framework with tool use, memory, and multi-agent workflows

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Limitations and Areas Still Under Development

While the feature is now available, it is primarily targeted at high-value, complex tasks and may not be suitable for simple requests such as fixing typos. The extent of its reliability across different domains and its impact on operational efficiency are still being evaluated. Details about potential limitations, such as cost implications due to increased token usage or how well it performs in real-world scenarios, remain under investigation.

Patriola's Guide: Cross AI Workflows: Seamless Multi-AI Tool Orchestration (Patriola's Guide to Claude Book 33)

Patriola's Guide: Cross AI Workflows: Seamless Multi-AI Tool Orchestration (Patriola's Guide to Claude Book 33)

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Upcoming Tests and Broader Deployment Plans

Anthropic plans to expand access to dynamic workflows, gather user feedback, and refine the orchestration patterns. Future updates may include more automated decision-making features, improved resumption capabilities, and broader integration into enterprise workflows. Monitoring real-world use cases will determine how widely this technology is adopted and its potential to reshape AI-driven project management.

AI for Project Managers: A Desk Reference & Field Guide: Use Artificial Intelligence to Streamline Workflows, Automate Tasks, and Make Smarter Decisions with Practical Tools and Ethical Insights

AI for Project Managers: A Desk Reference & Field Guide: Use Artificial Intelligence to Streamline Workflows, Automate Tasks, and Make Smarter Decisions with Practical Tools and Ethical Insights

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 custom JavaScript program that includes logic for selecting appropriate subagents based on the task’s requirements, such as choosing models with different capabilities or isolating agents in separate worktrees.

Can this feature be used for simple tasks?

No, Anthropic advises that dynamic workflows are best suited for complex, high-value projects. For basic requests, a single-agent approach remains more efficient.

What are the main orchestration patterns Claude uses?

Patterns include classify-and-act, fan-out-and-synthesize, adversarial verification, generate-and-filter, tournament, and loop-until-done, each mimicking traditional team management strategies.

Will this increase costs or token usage?

Yes, using multiple agents and dynamic scripts can meaningfully increase token consumption and computational resources, which is a consideration for enterprise use cases.

Source: ThorstenMeyerAI.com

This content is for general information only and is not financial, tax or legal advice. Consult a qualified professional for decisions about your money.
You May Also Like

Uber’s COO says it’s getting harder to justify money spent on tokenmaxxing

Uber’s operations chief Andrew Macdonald states that it is increasingly difficult to justify AI investment costs amid uncertain returns.

How to Reduce Heat and Noise in a High-Power AI Workstation

Learn effective strategies to lower heat and noise in high-power AI workstations, focusing on undervolting, cooling, and airflow management for sustained performance.

Singapore’s Sea logs drop in e-commerce profit as competition intensifies

Sea reports a drop in e-commerce profitability in Q1 2026, highlighting increased market competition. The company’s revenue still grew 46.6% YoY.

Vocal-strain load tracking for working singers

A new vocal load tracking app aims to help professional singers manage vocal health during tours by detecting early signs of strain before hoarseness occurs.