Back to News
ProductAI Understanding briefing

Anthropic launches Claude Managed Agents dynamic workflow beta

Anthropic has opened public beta access to Claude Managed Agents, a dynamic workflow feature allowing a main agent to orchestrate up to 1,000 sub-agents. In internal testing, this multi-agent approach detected 66 out of 70 embedded bugs in 116,000 lines of code, significantly outperforming single-agent modes.

4 min readRead the linked source
Source-provided image accompanying Anthropic launches Claude Managed Agents dynamic workflow beta
Source referenceSource recorded
Publisher
eu.36kr.com
Source type
Linked source — primary-source status has not been established.
ContextUnderstand this in 60 seconds

Key terms

API (Application Programming Interface)
A structured way for one software system to send requests to and receive responses from another system.
Memory (Agent Memory)
Stored context an AI agent uses across steps or sessions to improve continuity.
False Positive
An incorrect prediction where a model incorrectly flags a negative case as positive.
Test yourselfAI Agents Quiz

What happened

Anthropic launched the public beta for Claude Managed Agents dynamic workflow on October 10, enabling a primary agent to autonomously write division-of-labor programs and coordinate up to 1,000 sub-agents. Simultaneously, Claude Code Projects expanded its public beta to all Pro and Max users, allowing continuous project-based task management with persistent memory. In a reported test, the dynamic workflow detected 66 of 70 pre-embedded bugs in 116,000 lines of code across three runs, whereas a single agent detected only 14 to 27 bugs per run.

Anthropic released the public beta for Claude Managed Agents dynamic workflow on October 10. This feature allows a main agent to generate a workflow program that defines how multiple sub-agents divide labor, process tasks in parallel, and hand off results. The system supports up to 1,000 agents per workflow, with a current concurrency limit of 64 simultaneous threads. Each agent operates in an independent conversation history but shares the session's files and sandbox environment.

On the same day, Anthropic expanded the public beta of Claude Code Projects to all Pro and Max users who were previously on a waiting list. Projects allows users to submit continuous requirements within a single project conversation. Claude splits these into parallel threads, each with its own context and code copy. The system maintains a project memory that records decisions, requirement changes, and generated files, allowing subsequent tasks to build on previous work without re-explaining context.

Anthropic reported test results comparing a single agent against the dynamic workflow on a codebase of 116,000 lines with 70 pre-embedded bugs. In three consecutive runs, the single agent detected 14, 15, and 27 bugs respectively. The dynamic workflow detected 66 bugs in all three runs. The source notes that Anthropic did not disclose the specific division of labor used in this test, nor did it provide data on time consumption, token usage, or rates.

Pricing for Managed Agents is based on model token usage plus an additional $0.08 per hour for session operation time. Developers can set session budgets, though the source notes that final costs may exceed the budget if in-flight requests complete after the limit is reached. Projects usage consumes the existing plan quota, with parallel threads accelerating quota depletion.

Source details: eu.36kr.com ↗

Why it matters

This release marks a shift from single-agent execution to autonomous multi-agent orchestration, where AI systems manage task decomposition, parallel processing, and result verification without constant human intervention. The significant performance gap in bug detection suggests that coordinated agent teams can handle complex, large-scale code analysis more effectively than isolated instances. However, the lack of disclosed cost and time metrics means the practical efficiency of this approach remains unverified, and the high token consumption of running hundreds of agents could make it prohibitively expensive for routine use.

The launch of Managed Agents represents a structural change in how AI coding tools operate, moving from linear task execution to autonomous orchestration. By allowing the main agent to write the division-of-labor program, Anthropic is delegating workflow design to the AI itself, reducing the need for human-defined pipelines.

The reported bug detection results highlight a potential capability gap between single-agent and multi-agent systems. Detecting over 90% of embedded bugs compared to less than 40% for a single agent suggests that parallelization and specialized sub-tasks can significantly improve code analysis accuracy. However, without cost and time data, it is unclear if this improvement is economically viable for standard development workflows.

The expansion of Claude Code Projects to all Pro and Max users lowers the barrier to entry for project-based AI assistance. The persistent memory feature addresses a common pain point in AI coding: the loss of context between sessions. By maintaining a record of decisions and changes, the system aims to reduce the cognitive load on developers who previously had to manually track progress across multiple AI windows.

Interactive Mechanism

Interactive Mechanism: How It Actually Works

Explore the underlying technology behind this development interactively.

Agent Lifecycle Stage:
1
User Intent & Planning: "Audit customer refund request #4092 and settle payment."
2
Tool Calling: Emits structured JSON call crm_get_transaction(id='4092').
3
Guardrail & Verification:🛡️ Paused: High-value action requires human operator sign-off.
4
Final Settlement: Refund recorded, email receipt dispatched, and audit log stored.
Core takeaway: An AI agent is not just a language model—it is a closed loop of planning, tool invocation, and environment feedback. Production systems require self-healing retries and strict human approval guardrails.
Interactive Concept Check+10 Points
AI Agents Quiz

An agent must create a draft calendar event for Tuesday at 2 p.m. Which evidence would establish the requested result?

What to watch next

Monitor independent benchmarks that measure the cost, latency, and false-positive rates of the Managed Agents workflow compared to single-agent baselines. Watch for enterprise adoption reports to see if the $0.08 per hour session fee and token costs are viable for large-scale deployments. Additionally, observe whether Anthropic adjusts the 64-thread concurrency limit or the 1,000-agent cap as the beta matures.

Independent verification of the bug detection claims is currently absent. The source is a secondary report of Anthropic's test results, and no third-party has replicated the 66/70 bug detection rate. Future benchmarks will be crucial to confirm whether this performance advantage holds in real-world, non-embedded bug scenarios.

Cost efficiency is a major unknown. The $0.08 per hour session fee is modest, but the token consumption of up to 1,000 agents could be substantial. Developers will need to evaluate whether the accuracy gains justify the increased API costs, particularly for large codebases.

The concurrency limit of 64 threads may be a bottleneck for large-scale workflows. Anthropic has stated this number may be adjusted, so monitoring updates to the API documentation and beta notes will reveal if the system scales to handle more parallel tasks.

Related guides & quizzes

Found this useful?