A Harness for Every Task: Dynamic Workflows (dynamic work orchestration) in Claude Code – How to Solve Complex Tasks with Tailor-Made Multi-Agent Systems
As an AI-native builder, you already know the real bottleneck isn’t raw model intelligence anymore — it’s context, persistence, and the ability to orchestrate work across time and parallel streams. Anthropic’s new dynamic workflows solve exactly this by letting Claude instantly write and run a custom harness (a tailored orchestration layer that defines how agents are spawned, coordinated, verified, and concluded) for your specific task.
This deep dive is written for experienced AI-native developers, architects, and power users who already live in tools like Claude Code, Cursor, or Aider. We’ll break down the concept from Anthropic’s blog post “A Harness for Every Task,” explain the mechanics, showcase powerful patterns, deliver practical examples, and end with key concepts you can immediately apply to your own work.
Claude Code ships with a strong default harness optimized for coding — handling files, tools, iterations, and reasoning in one coherent session. It works incredibly well for most daily tasks because many jobs feel like coding: structured, iterative, and with clear outputs.
But with longer, more ambitious, or high-stakes projects, classic failure modes appear:
Static custom harnesses built via SDKs or scripts were the old workaround — but they’re generic and maintenance-heavy. Dynamic workflows flip the script: Claude generates the precise orchestration for your exact task, on the fly. A harness (orchestration layer) is everything around the model: how the task is broken down, which sub-agents run, what tools they have, how outputs are verified, and when the job is truly done. It turns a single model into a coordinated team.
With dynamic workflows:
~/.claude/workflows
).This isn’t just “more compute.” It’s structural resistance against the common failure modes of long-running agent sessions.
Claude composes workflows from these reusable patterns. Learn them so you can guide the model more effectively:
Classify-and-Act (classify and route) A classifier agent determines the task type and routes it to the right behavior or specialized sub-agent.
Fan-out-and-Synthesize (split wide and merge) Break a big task into many small ones, run them in parallel in clean contexts, then let a synthesizer agent combine the results. Prevents cross-contamination.
Adversarial Verification (opponent-based checking) Every producer agent gets a dedicated “adversary” agent that checks output against a rubric. Kills self-preferential bias.
Generate-and-Filter / Tournament (generate, filter, compete) Create many ideas or solutions, deduplicate, and let them compete through pairwise judging. Excellent for creative or ranking tasks.
Loop-until-Done (iterate until success criteria) Keep spawning agents until a stop condition is met (no new findings, no remaining errors). Perfect for debugging, research, and exhaustive analysis.
These patterns combine beautifully — for example, fan-out + adversarial verification + synthesize.
Coding & Engineering:
Non-Coding Work (often where the biggest wins are):
CLAUDE.md
.Concrete Prompt Example (inspired by Anthropic): “This test fails maybe 1 in 50 runs. Set up a workflow to reproduce it. Form competing theories about the race condition, and don’t stop until one theory survives all the evidence.”
The resulting workflow: Classifier → Fan-out hypothesis generation → Adversarial verifiers/refuters → Loop-until-done.
Benefits:
This represents a natural evolution from prompt engineering to workflow engineering. You no longer design the full system — you design the prompt that makes the system design itself.
Trade-offs: Dynamic workflows mark a shift from “better single agent” to orchestrated agent teams on demand. It’s not just a feature in Claude Code — it’s a new way to think about reliable agentic work.
Try it today: Take a complex task you’re struggling with and add “Use a dynamic workflow…” or the trigger “ultracode”. Watch how Claude designs the perfect harness. Iterate on the prompt, save what works, and level up.
The world isn’t getting simpler. But now we have a harness for every task.
Use it wisely. Further Reading / Primary Source
“A harness for every task: dynamic workflows in Claude Code” by Anthropic (June 2, 2026)
Highly Recommended Video
For a practical, hands-on breakdown of **Ultracode** and dynamic workflows (including live demos and pro tips), watch this excellent video from Chase AI:
[“the most POWERFUL claude code feature in months”](https://youtu.be/6cmi7qyFwEE)
It complements the Anthropic blog perfectly and shows exactly how to start using these capabilities right away.
What complex task are you going to throw at a dynamic workflow first? Drop it in the comments — I’d love to see what you build.