How to Actually Use Claude Code Dynamic Workflows
The video explains Claude Code's new dynamic workflows feature, comparing it to skills, sub-agents, agent teams, and the /goal command. The presenter demonstrates a real workflow that spun up 41 parallel Haiku agents to audit his skills, consuming ~5 million input tokens. He advises careful, targeted use of workflows due to their high token costs.
Summary
The presenter opens by demonstrating a dynamic workflow that spun up 41 parallel Haiku scoring agents to audit all of his Claude Code skills, feeding results into a single Opus synthesis agent. The output was an HTML file ranking skills worst-to-best with improvement feedback. This example consumed approximately 5 million input tokens, though output tokens were minimal, keeping costs somewhat reasonable.
The video then systematically distinguishes between four related but distinct Claude Code features: Skills (reusable recipes or automation prompts), Sub-agents (parallel agents that don't share context with each other but report back to the main session), Agent Teams (a small crew of agents that can communicate with each other, share task lists, and have individual roles), and Dynamic Workflows (Claude writing a JavaScript script that orchestrates many sub-agents in parallel, with all results merged at the end). The key distinction is who holds the plan — in workflows, Claude generates a JS file that drives execution, rather than keeping the plan in the main session context.
The presenter introduces a 'ladder' metaphor: as you move from simple chat → skills → sub-agents → agent teams → dynamic workflows, complexity, functionality, risk, and cost all increase. He also contrasts workflows with the /goal command: /goal is a depth play (looping until a done-equals-true criterion is met), while workflows are a width play (many agents executing simultaneously on a pre-established plan without checking a completion criterion).
On cost, the presenter warns that workflows can be extremely expensive. In one session he burned through roughly half of his $200/month subscription with a single prompt that had agents crawl his entire desktop and repos. He advises bounding scope, naming deliverables explicitly, and assigning sub-agents to the cheaper Haiku model to manage costs.
Practical tips include: using /workflows to monitor running workflows, saving workflow JS files into your project directory (they default to a global location), and invoking workflows explicitly by saying 'set me up a dynamic workflow' rather than just using the word 'workflow' casually. The presenter also mentions the /deep research command as a built-in workflow that runs parallel research agents, votes on claims, and produces a cited report.
Finally, the video introduces 'Ultra Code' mode (/effort max), which combines extra-high reasoning effort with automatic workflow invocation on every prompt — described as the most powerful but most expensive mode. The presenter closes with a one-slide decision framework: quick task → ask Claude; repeatable process → skill; messy side task → sub-agent; small collaborative crew → agent team; run until objective met → /goal; giant parallel job → dynamic workflow.
Key Insights
- The presenter argues that dynamic workflows differ from agent teams in a fundamental architectural way: workflows have Claude generate a JavaScript file that drives execution, meaning the plan lives in the script rather than in the main Claude session context.
- The presenter distinguishes /goal from workflows as a depth-vs-width tradeoff — /goal loops through multiple passes until a done-equals-true criterion is met (potentially 24+ hours), while workflows deploy many agents horizontally on a fixed plan with no completion-checking loop.
- The presenter reports burning through roughly half of his $200/month Claude subscription in a single workflow prompt that crawled his entire desktop and local repos, illustrating how input-token-heavy parallel agent jobs can be extremely costly even when output tokens are small.
- The presenter reveals that 'Ultra Code' mode (/effort max) effectively combines extra-high reasoning effort with automatic workflow invocation on every prompt, meaning it bypasses many permissions and defaults to orchestrating workflows — making it the most expensive available mode.
- The presenter notes that workflow JS files are saved globally by default rather than inside the current project directory, and that users must explicitly instruct Claude to save them inside the project folder (e.g., in .claude/workflows) to keep them organized and reusable per project.
Topics
Full transcript available for MurmurCast members
Sign Up to Access