TL;DR
Anthropic has introduced dynamic workflows in Claude Code, letting Claude write JavaScript orchestration code that spawns and coordinates subagents for complex tasks. The confirmed feature is meant for high-value work such as large refactors, research, fact checking and security review; costs, safeguards and real-world reliability remain less clear.
Anthropic has introduced dynamic workflows in Claude Code, a feature that lets Claude generate and run task-specific orchestration code to coordinate multiple subagents inside one complex job, according to a June 2 Claude blog post by Thariq Shihipar and Sid Bidasaria. The development matters because it moves Claude Code beyond a single-agent pattern and toward temporary, role-based agent teams for work that is broad, adversarial or judgment-heavy.
In the system described by Anthropic and summarized by Thorsten Meyer AI, a dynamic workflow is a JavaScript harness that Claude writes for a task. The harness can spawn separate subagents, assign focused briefs, wait for results at a barrier, and merge structured outputs into a final answer or code change.
The reported patterns include classify-and-act routing, fan-out-and-synthesize work, adversarial verification, generate-and-filter selection, tournament-style judging and loop-until-done spawning. Anthropic frames these as reusable moves that Claude can compose when a task has many parts or needs independent review.
The company also places limits around the use case. Thorsten Meyer AI, citing Anthropic’s caveat, says dynamic workflows use meaningfully more tokens and are aimed at complex, high-value tasks, not routine edits. The practical distinction is cost and control: a workflow may produce stronger coverage, but it can also expand quickly if budgets and stop conditions are loose.
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.
Why Agent Teams Matter
For developers and AI teams, the appeal is coverage across large tasks. A single agent working in one context can stop early, favor its own prior answer or lose parts of the original instruction over time, according to the Thorsten Meyer AI analysis. Separating work into clean subagent contexts and adding independent verification could help on jobs where missing one branch of work has a real cost.
The impact is not only technical. If dynamic workflows become common, teams using Claude Code may need to manage token budgets, model routing, permissions and audit trails as part of normal AI-assisted work. The feature shifts some responsibility from prompt writing to workflow management, where bad scope or weak guardrails can create higher bills or unreliable results.
AI workflow automation tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Claude Code’s Agent Arc
The July 1 analysis from Thorsten Meyer AI presents dynamic workflows as the third part of a loose Claude Code sequence: skills package organizational knowledge, loops govern delegation over time, and dynamic workflows coordinate subagents within one job. That framing is the author’s, while the mechanics and use cases are attributed to Anthropic’s Claude blog.
Anthropic’s original post, dated June 2, 2026, is the underlying source for the feature’s mechanics. Thorsten Meyer AI points readers to code.claude.com/docs for documentation and describes the feature as recent and still evolving.
“A harness for every task: dynamic workflows in Claude Code”
— Thariq Shihipar and Sid Bidasaria, Anthropic
subagent orchestration software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Costs And Limits Remain
The available reports do not settle how broadly dynamic workflows are available, what default controls limit excessive spawning, or how teams should compare token spend with quality gains. It is also not yet clear how consistently Claude will choose the right number of subagents for real production tasks.
Evidence is still thin on outcomes. Anthropic and Thorsten Meyer AI describe use cases including research, migrations, ticket ranking and security checks, but the source material does not provide benchmark results, failure rates or customer adoption figures.
AI task management platform
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Developers Test The Pattern
Teams using Claude Code are likely to test dynamic workflows on bounded, high-value jobs first: a sample refactor, a limited fact-checking pass or a security review subset. The immediate work is setting token caps, stop conditions, model choices and structured output formats before allowing broader runs.
For workflows that read untrusted public content, Thorsten Meyer AI highlights a quarantine pattern: agents that read that material should be kept away from high-privilege actions, with a separate agent doing the action step. A careful rollout would pair that separation of duties with logging, human review and cost reports.
AI code orchestration tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
What are dynamic workflows in Claude Code?
Dynamic workflows are task-specific orchestration programs that Claude writes and runs inside Claude Code. According to Anthropic’s blog, they can spawn and coordinate subagents so a larger job can be split into focused parts.
Who announced the feature?
The underlying announcement came from Anthropic in a June 2, 2026 Claude blog post by Thariq Shihipar and Sid Bidasaria. Thorsten Meyer AI covered the feature in its July 1, 2026 AI Dispatch.
Are dynamic workflows for everyday coding tasks?
No. Thorsten Meyer AI, citing Anthropic’s caveat, says the approach uses more tokens and is aimed at complex, high-value work. A small typo fix would normally be better handled by one agent or a direct edit.
Why use multiple agents instead of one?
The aim is to reduce single-agent failure modes: stopping early, grading its own output and losing the original goal during long tasks. Separate subagents can work in parallel and an independent reviewer can check the result, according to the reported workflow patterns.
What risks should teams watch?
The main risks are token cost, runaway spawning, weaker controls around tool use and overreliance on agent self-management. Teams should set budgets and stop rules, keep permissions narrow and review high-impact outputs before use.
Source: Thorsten Meyer AI
