Claude Code Dynamic Workflows: How 100 Agents Research, Write, and Build in One Session

Claude ships features faster than anyone can track.

Within 8 months, it’s pushed out major updates including Skills, MCP servers, plugins, connectors, cowork, routines, and model upgrades.

After a while you stop looking.

For new drops, I usually let it settle into how I already work, and trust it will find its place when it matters. Most features do, so I let them slide.

But this one caught me off guard.

I had asked Claude to research about MCP servers. A normal Tuesday. It spun up 101 agents and ran them for 13 minutes, 723 searches and page-reads, before it handed me anything. 75 of these agents were fact-checking, each trying to prove a finding wrong.

Claude invoked a the dynamic workflow with deep-research, completely caught me off guard

I was not expecting that. That is not my usual workflow. So I stopped the research and took the feature apart instead.

What it ran is called a dynamic workflow. Claude had reached for a built-in one, deep-research, on its own.

This article goes through what happened: what a dynamic workflow is, what those 100 agents actually did, what it means for your work, and how to take the same pattern into workflows of your own.

What’s inside:

• What dynamic workflows are in Claude Code
• What 100 agents do in one workflow run
• Why dynamic workflows change how you work with AI
• How a dynamic workflow is built
• How to build your own workflow without the feature
• When a dynamic workflow is worth the tokens
• One more thing I found in the binary
• By the end: a workflow pattern you can run on your own research, writing, or analysis, with or without the feature built-in