Discussion

• @tobi Tobi Lutke on x

  @dexhorthy ... There is so much alpha still left in harness engineering. That's exactly what we saw with /autoresearch. Codemode DSL for orchestration is brilliant. Great work by the claude team.

• @dexhorthy Dex on x

  someone hit me up about the new “claude dynamic workflows” feature, claiming “see, multi-agent works” But really, the launch of this feature proves the exact point that I made back in June of 2025, along with @walden_yan, @tobi, @karpathy, and many others: Deterministic

• @jarredsumner Jarred Sumner on x

  Dynamic workflows and adversarial code review was part of what made it possible to rewrite Bun in Rust in 6 days.

• @nickadobos Nick Dobos on x

  Claude code's new dynamic workflows update is absurd. Make sure you understand what its doing here. This isn't simply a long running mode like /goal, or a fancy subagent verifier process. This is Claude vibecoding an entire brand new subagent fleet harness on demand RLM on

• @claudedevs @claudedevs on x

  New in Claude Code (research preview): dynamic workflows. Claude writes an orchestration script on the fly, then spins up a large fleet of coordinated subagents in parallel to take on your most complex tasks. Use the word “workflow” in a prompt to get started. [image]

• @daniel_mac8 Dan McAteer on x

  This is amazing. Do this: 1. Set model to Opus 4.8 2. Reasoning effort to /ultracode Enables Claude Code's new Dynamic Workflows. Claude will autonomously detect complex tasks, write an orchestration script, and spawn an agent swarm. [video]

• @adocomplete Ado on x

  Opus 4.8 is awesome but that's expected. The unsung hero of this release for me is dynamic workflows. Claude plans your task, fans it out to tens or hundreds of parallel subagents, verifies their work, and iterates until the results converge into one coordinated answer. [video]

• @_catwu Cat on x

  Excited to share our most powerful new Claude Code feature: dynamic workflows!  Mention “workflow” in a prompt and Claude will dynamically create an orchestration plan that it strictly follows, allowing you to confidently trust that every stage happens in the right order even acr…

• @a1zhang Alex Zhang on x

  In case you're curious about why dynamic workflows are so powerful and the future, read the RLM paper! Opus 4.8 + dynamic workflows in Claude Code is perhaps the first instance of a frontier model seriously trained to be an RLM. I suspect within a year they'll just become the [im…

• @gregisenberg Greg Isenberg on x

  Claude Code just dropped “dynamic workflows” and it's pretty cool. You type “create a workflow” or turn on “ultracode” in the effort menu and it spins up hundreds of parallel agents that check each other's work. The unit of work you can hand off jumps from a file to an entire

• @sidbid Sid on x

  Super excited to finally share Dynamic Workflows in Claude Code!! We built this a couple months ago, and it has slowly become a daily driver for a bunch of people at Anthropic. A few tips for getting the most out of it 🧵 https://x.com/...

• @_catwu Cat on x

  Recently, I used dynamic workflows to catalogue all of our 100s of A/B test flags and find the ones rolled out to 0% or 100% so that we can quickly deprecate the stale ones.  Instead of waiting for Claude Code to investigate each sequentially, dynamic workflows allowed Claude to …

• @noahzweben Noah Zweben on x

  This is one of the most useful and incredible things we've shipped. @bcherny once called it the future. Give it a whirl!!

• @claudeai Claude on x

  Also new in Claude Code: dynamic workflows (research preview). For the hardest tasks, Claude makes a plan, runs hundreds of parallel subagents, and verifies its work before reporting back. Think a migration touching hundreds of files. Read more: https://claude.com/...

• @jarredsumner Jarred Sumner on x

  Dynamic workflows, in my personal opinion, is the state of the art today for reliably using agents to complete medium - large projects. For extra large projects, I especially like using workflows with /loop.

• @bcherny Boris Cherny on x

  We also shipped dynamic workflows in Claude Code (research preview), for tasks too big for one pass. Make sure to default to auto mode so Claude isn't stopping for permissions. It's token-intensive, so save it for your biggest jobs: migrations, refactors, perf optimization,

• @claudedevs @claudedevs on x

  Dynamic workflows are useful for tasks that are too big for a single agent loop, such as service-wide bug hunts, large migrations, or stress-testing a design. They're powerful and can be expensive, consuming a lot of tokens fast. Start with a scoped task to get a feel for it.

• @claudedevs @claudedevs on x

  Dynamic workflows are reusable. Save one as a slash command in your project to share with the team, or in your home directory to use it everywhere.

• @bcherny Boris Cherny on x

  Big migrations and refactors are some of a team's most important work, and the easiest to push off to a “better time” since they'd tie up engineers for a quarter. With dynamic workflows, Claude can now land that kind of work in days or weeks. More: https://claude.com/...

• @rad.gendervibes.online @rad.gendervibes.online on bluesky

  It looks like Anthropic has figured out a generalized harness to do all the huge-volume work they've been talking about (mythos security scanning, bun rewrite, etc.).  —  claude.com/blog/introdu...

• r/accelerate r on reddit

  Claude Opus 4.8 Released