If you haven’t messed with the new dynamic workflows in Claude Code yet, do it this week. It’s the first update in a while that actually changed how I work instead of just making the same stuff a little faster. The short version of what it does: instead of one Claude sitting in a single chat trying to plan the whole task and do it at the same time, Claude writes its own little orchestration script on the fly and uses it to spin up a bunch of separate subagents. Each one gets its own clean context and a small focused job, and Claude coordinates them. So it builds a custom setup for whatever you’re doing instead of forcing every task through the same one chat window. The reason this matters is all the stuff that quietly went wrong on long tasks before. Claude stopping halfway and calling a huge task done when it really did about half of it. It’s also a pretty bad judge of its own work when you ask it to check itself. And on long sessions it slowly loses the thread of what you originally asked, especially after a compaction or two. Splitting the work across separate agents with their own context sidesteps most of that. The example tasks they showed are what sold me. Stuff like: go through my last 50 sessions, find the corrections I keep making, and turn the recurring ones into claude md rules or dig through six months of Slack incidents and find root causes nobody ever filed a ticket for. or hand it a business plan and have separate agents tear it apart as an investor, a customer, and a competitor. The bun folks apparently used it for a big chunk of their Zig to Rust rewrite too. It’s not really a coding feature anymore, it just happens to live in a coding tool. oky here’s the part I actually wanted to talk about. Claude (Opus series) is great at the orchestrating bit. Writing the workflow, planning it, keeping everything coordinated. That’s the part worth paying for. But the blog itself warns you these workflows burn tokens fast once you’re fanning out to a lot of subagents. And that’s where it gets a little silly, because most of those subagents are just doing grunt work. Reading a file, ranking one resume out of a big stack, checking whether a single claim actually holds up. None of that needs Opus. It doesn’t even need Sonnet, which adds up quick when you’ve got dozens of them going at once. So what I started doing is routing the actual worker subagents to cheaper models, with amazing quality as well. DeepSeek V4 Pro, MiniMax M3, Kimi K2.6, that tier. The surprising part is they’re not worse at the grunt work. On the coding and tool-use stuff they’re right there with Sonnet, sometimes a bit ahead, and depending which one you pick they run anywhere from a few times to 10x+ cheaper per token. You keep Claude as the orchestrator and let the cheap models do the bulk of the work underneath it. That combo actually changes what’s worth doing. A workflow that would’ve felt too expensive to run, or way too expensive to leave going on a loop, suddenly isn’t, and you stop rationing it. Didn’t expect a routing decision to shift how much I lean on this, but it has. One practical thing: these longer workflows can run for hours. You probably don’t want to do that on your laptop. There’s a whole category of cloud sandboxes where Claude Code is already configured and running 24/7 - HappyCapy, Zo computer or just a plain VPS if you want to self-host. Anyway. Give dynamic workflows a shot if you haven’t touched them : link for the blog - https://x.com/trq212/status/2061907337154367865 claude code documentation- https://code.claude.com/docs/en/workflows , and if you are using them, try not running everything on Claude. Kind of a cheat code submitted by /u/techiee_
Originally posted by u/techiee_ on r/ClaudeCode