A workflow run requires user confirmation upfront, and organization admins can manage access and settings, including admin controls for Enterprise customers.

Early user feedback highlights benefits in discovery, review tasks, dead code identification, and surface cleanup opportunities missed by static analysis, improving planning-to-implementation flow and visibility for long-running tasks.

The feature is in research preview across Claude Code CLI, Desktop, VS Code extension, and via Claude API on cloud platforms, with higher token usage and best for scoped tasks.

Use cases include codebase-wide bug hunts, security audits with parallel searches, large migrations across thousands of files, and high-stakes work with multiple independent attempts and adversarial checks to prevent mistakes.

Dynamic workflows enable planning, task distribution, result verification, and iterative refinement until consensus, suitable for complex migrations spanning days, such as porting Bun from Zig to Rust with roughly 750,000 lines of code.

Dynamic workflows are available to Max and Team plan users and via the API, with Enterprise customers able to opt in through admin controls, offering workflow recovery and granular oversight.

Early feedback suggests the tool speeds up time-intensive engineering processes and scales to larger, more complex tasks than before.

There are two ways to start a workflow: ask Claude to create one, or enable the ultracode setting to let Claude decide when to use workflows.

Claude Code’s dynamic workflows are presented as a research preview, with prompts that trigger orchestration plans to ensure correct ordering and reliability.

Anthropic unveiled dynamic workflows for Claude Code, orchestrating large, multi-step coding projects by coordinating parallel subagents that tackle subtasks simultaneously.

Claude Code’s dynamic workflows enable tens to hundreds of parallel subagents, allowing end-to-end handling of complex tasks that would historically take weeks or quarters to complete.

Getting started resources are available by default on certain plans or via the ultracode setting, with documentation and settings pages outlining how to use them.