Claude Code now writes its own orchestration script and runs up to 1,000 subagents
Alongside Opus 4.8, Anthropic opened a research preview of dynamic workflows in Claude Code, and it is the quietly radical part of the day. You mention the word workflow in a prompt, Claude writes a JavaScript orchestration script on the fly, and then it spins up a fleet of coordinated subagents, up to a thousand in parallel, that the script launches in order, with conditional logic and loops, keeping intermediate state in variables that live outside the conversation.
The shift here is that the plan moves from prose into code. Until now an agent plan was a paragraph it tried to follow. A script is not a paragraph. It has control flow, it can branch, it can retry, it can hold state across hundreds of agents and guarantee stage two does not start until stage one actually finished. That is the difference between an agent that intends to do things in order and one that provably does.
The proof of concept is loud. Jarred Sumner used dynamic workflows to rewrite Bun, the JavaScript runtime, from Zig to Rust, generating roughly 750,000 lines of code in eleven days while keeping 99.8 percent of the existing test suite green. Rewriting a production runtime in a different language in under two weeks is not a demo, it is a preview of what a single engineer with a thousand subagents looks like.
There is a competitive read too. For months the interesting startups were the ones orchestrating fleets of coding agents, Emdash, cmux, KanBots, Runtime, all building the control layer on top of the model. Anthropic just absorbed that layer into the platform. Orchestration was the third-party opportunity, and the platform owner walked in and built it in. It is on by default for Max and Team, admin-gated on Enterprise, and a manual toggle in config for Pro.
Link: anthropic.com/news/claude-opus-4-8
← Back to all articles
The shift here is that the plan moves from prose into code. Until now an agent plan was a paragraph it tried to follow. A script is not a paragraph. It has control flow, it can branch, it can retry, it can hold state across hundreds of agents and guarantee stage two does not start until stage one actually finished. That is the difference between an agent that intends to do things in order and one that provably does.
The proof of concept is loud. Jarred Sumner used dynamic workflows to rewrite Bun, the JavaScript runtime, from Zig to Rust, generating roughly 750,000 lines of code in eleven days while keeping 99.8 percent of the existing test suite green. Rewriting a production runtime in a different language in under two weeks is not a demo, it is a preview of what a single engineer with a thousand subagents looks like.
There is a competitive read too. For months the interesting startups were the ones orchestrating fleets of coding agents, Emdash, cmux, KanBots, Runtime, all building the control layer on top of the model. Anthropic just absorbed that layer into the platform. Orchestration was the third-party opportunity, and the platform owner walked in and built it in. It is on by default for Max and Team, admin-gated on Enterprise, and a manual toggle in config for Pro.
Link: anthropic.com/news/claude-opus-4-8
Comments