Back to Flash News

Anthropic Launches Public Beta for Claude Dynamic Workflows Supporting Thousands of Agents

Anthropic has opened the public beta for "Dynamic Workflows" in Claude Managed Agents, where the main agent first writes a plan, then assigns tasks to a large number of agents for parallel execution, and finally aggregates the results, allowing up to 1000 agents to be scheduled in a single run.

Claude Managed Agents is a managed agent service by Anthropic for developers, where agents run directly in the Anthropic cloud environment after developers configure models, tools, and prompts, without needing to build their own loops and sandboxes, supporting long tasks from several minutes to several hours. Previously, it supported a sub-agent mode, where the main agent assigns tasks and reads reports one by one, with a maximum of 25 agents concurrently in a single session.

The dynamic workflow mechanism is different: the main agent writes a program that the server executes in the background in stages, with context and results passed between agents through the program, allowing the main agent to continue conversing with the user and report progress at any time. In a test with a codebase of 116,000 lines embedded with 70 bugs, a single agent found 14, 15, and 27 bugs in three runs, showing significant result variability; however, the workflow found 66 bugs in each of its three runs.

This feature is suitable for tasks that can be broken down, including auditing large codebases, bulk code migration, reading hundreds of contracts, and cross-referencing multiple sources during research. The official documentation provides examples where one or two contracts can be handled directly by agents, and workflows are initiated for parallel reading as the number increases. To enable this, set the multiagent type in agent configuration to multiagent_20261001 (workflows are enabled by default under this type), and instruct Claude to run the workflow, with planning and scheduling handled by it. Relevant commands can be entered directly in Claude Code, and templates are also provided on the platform.

Each agent consumes tokens, and costs rise rapidly when running hundreds to thousands in parallel. Anthropic recommends testing with small-scale tasks before gradually increasing complexity. The documentation suggests setting a "session budget" when creating a session, which automatically pauses the workflow upon reaching the limit, and can be continued by raising the budget; this budget can only be set at creation and cannot be added later. Temporarily defined agents within the workflow default to using the same model as the main agent, and if cheaper models are needed for some tasks, those agents must be created separately and included in the configuration in advance.

This feature is driven by product capability expansion and developer adoption behavior. The flow of funds mainly comes from token fees paid by the calling party, directed towards Anthropic's cloud computing resources. Beneficiaries include enterprise developers needing to handle large-scale parallel tasks (improving efficiency through stability and scale), and Anthropic (increasing revenue through high concurrent usage); the pressure is on cost-sensitive users and the unstable performance of single-agent solutions on complex tasks.

Source: Public Information

ABAB AI Insight

Anthropic previously launched Claude Managed Agents, hosting agent loops, sandboxes, and long sessions in the cloud, allowing developers to run tasks for hours by simply configuring models and tools, and supporting sub-agent dispatching, but limited to a maximum of 25 concurrent agents per session with the main agent needing to process reports one by one. The dynamic workflow now shifts the orchestration logic to be executed as a program on the server, freeing the main agent from round-by-round coordination and moving to phased parallel execution in the background.

In terms of capital and resource pathways, Anthropic absorbs orchestration complexity through managed infrastructure, liberating developers from building their own multi-agent systems and guiding usage towards its cloud. The motivation is to enhance the completion rate and consistency of high-value long tasks, thereby expanding the scale of enterprise-level paid calls; specific actions include opening configuration interfaces (multiagent_20261001) and providing commands and templates, while also constraining uncontrolled consumption through the session budget mechanism.

This is similar to the early cloud computing path of migrating orchestration from user scripts to platform schedulers, such as Kubernetes abstracting container scheduling into declarative resources. Currently, Anthropic is in the stage of expanding from single-agent tools to scalable multi-agent infrastructure, competing for enterprise workflow entry points through managed orchestration rather than just providing basic model inference.

Essentially, this represents a technological substitution and industrial chain reconstruction. Single agents face high variance in results on large-scale decomposable tasks due to context and coordination bottlenecks, while encoding plans as executable programs allows for parallel phase execution and result transmission to become platform primitives, shifting the reliability of complex tasks from model capability to orchestration systems. The mechanism at play is that server-side execution cuts off the context bottleneck of the main agent, allowing scalable parallelism to no longer be limited by single-session interactions, thus transforming what originally required custom engineering multi-agent systems into configurable services.

ABAB News · Cognitive Laws

  1. Orchestration capability determines the scale limit

  2. Parallel variance is replaced by program stability

  3. Token consumption scales linearly with the number of agents