TL;DR
Anthropic has described dynamic workflows in Claude Code, a capability in which Claude writes JavaScript orchestration code to coordinate subagents for complex tasks. The company frames it as useful for large, parallel or adversarial work, while warning that it can use many more tokens.
Anthropic says Claude Code can now build task-specific teams of subagents through a feature called dynamic workflows, a development aimed at complex coding, research and review tasks where one agent may lose track, stop early or grade its own output too favorably.
The confirmed development is Anthropic’s June 2 Claude Code post, credited in the source material to Thariq Shihipar and Sid Bidasaria, describing dynamic workflows as a way for Claude to write and run a JavaScript harness tailored to the task in front of it.
According to the source material, that harness can spawn subagents, give them separate context windows, coordinate their work and merge their outputs after a barrier step. The listed workflow patterns include fan-out-and-synthesize, classify-and-act, adversarial verification, generate-and-filter, tournament judging and loop-until-done.
Anthropic’s caveat, as summarized by the Thorsten Meyer AI dispatch, is that dynamic workflows use meaningfully more tokens and are intended for complex, high-value tasks. The source material does not frame the feature as a tool for routine edits such as fixing a typo or making a small single-file change.
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.
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.
Claude Code Gets A Manager
The change matters because it moves Claude Code from a single-agent pattern toward orchestrated task teams. If the system works as Anthropic describes, it could help with jobs that benefit from parallel work, independent review or competing approaches, including large refactors, research reports, ticket triage and security review.
For developers and technical teams, the trade-off is cost and control. A workflow that spawns many agents may produce more checked output, but it can also create higher token usage, longer runs and more need for human judgment about when the task is large enough to justify the orchestration.
JavaScript development tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
From Skills To Workflows
The July 1 Thorsten Meyer AI dispatch places dynamic workflows after two related Claude Code ideas: skills, which package organizational knowledge, and loops, which decide how far to delegate over time. Dynamic workflows add a third axis by letting Claude assemble a temporary agent structure inside a single task.
The source material says the feature is meant to address three recurring single-agent failure modes: agentic laziness, where work stops before the job is complete; self-preferential bias, where a model favors its own output; and goal drift, where earlier constraints fade during long tasks. The proposed remedy is separation of work, focused briefs and independent checking.
“A harness for every task: dynamic workflows in Claude Code”
— Thariq Shihipar and Sid Bidasaria, Anthropic
AI workflow automation software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Rollout Details Remain Limited
It is not yet clear from the supplied material how broadly dynamic workflows are available across Claude Code users, what exact limits apply, or how Anthropic measures reliability against single-agent runs. Public evidence is also limited on real-world cost impact and how often the approach reduces errors in production settings.
AI subagent orchestration tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Developers Will Test The Limits
The next milestone is practical adoption: developers will watch Claude Code documentation, examples and user reports to see which tasks benefit from subagent orchestration and which remain better served by a single agent.
Teams considering the feature are likely to start with small pilots, token budgets and clear stop conditions before using workflows on large migrations, broad research tasks or security reviews that require independent verification.
complex coding AI assistants
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
What did Anthropic announce about Claude Code?
Anthropic described dynamic workflows, a Claude Code feature that lets Claude write a task-specific JavaScript harness to coordinate subagents during complex work.
How do dynamic workflows work?
The workflow can spawn subagents, assign focused briefs, wait for their outputs and synthesize the results. The source material says each subagent may have a separate context window and a narrower goal.
Is this meant for everyday coding tasks?
No. The supplied material says dynamic workflows use more tokens and are aimed at complex, high-value tasks, not routine edits or small fixes.
What kinds of work could use this approach?
The source material lists large refactors, deep research, claim-checking, ticket ranking, post-mortems, backlog triage and security pattern review as possible uses.
What is still unknown?
The available material leaves open rollout scope, exact usage limits, cost patterns and whether independent benchmarks will show consistent gains over single-agent workflows.
Source: Thorsten Meyer AI
