記事一覧に戻る
What Are Claude Managed Agents? The Era of Production-Ready AI Agents Has Arrived

What Are Claude Managed Agents? The Era of Production-Ready AI Agents Has Arrived

ZenChAIne·
AI AgentClaudeAnthropicManaged Agents

Introduction

On April 8, 2026, Anthropic launched Claude Managed Agents in public beta — a suite of composable APIs that provide fully managed infrastructure for building and deploying AI agents at scale. The promise: go from prototype to production in days, not months.

Instead of building your own agent loop, tool execution sandbox, state management, and credential vault, developers get all of this as a managed service. Anthropic claims a 10x improvement in development speed, and early enterprise adopters suggest the number is more than marketing.

Key Takeaways

  • Claude Managed Agents provides fully managed infrastructure for AI agents — sandboxing, state management, and tool execution
  • The "Brain vs. Hands" architecture decouples inference from execution, reducing TTFT by up to 90%
  • SDKs available in 7 languages, with session-based pricing ($0.08/hour + token costs)
  • Notion, Rakuten, Asana, and Sentry mentioned as early adopters

Why Do We Need Managed Agents Now?

The biggest bottleneck in production AI agents is not model capability — it is infrastructure. Running agents in production requires building and maintaining several complex subsystems.

  • Sandboxed execution: Isolated containers for safe code execution
  • State management: Persistent sessions that survive disconnections
  • Credential management: Secure storage and injection of OAuth tokens and API keys
  • Tool integration: Connections to external services (GitHub, Slack, Jira, etc.)
  • Observability: Action logs, tracing, and debugging for agent behavior

Building these from scratch takes months of engineering. Managed Agents abstracts this entire layer into an API, letting developers focus on what their agents should do rather than how to run them safely.

How Does the "Brain vs. Hands" Architecture Work?

At the core of Managed Agents is what Anthropic's engineering team calls the "Brain vs. Hands" architecture. By fully decoupling the inference engine (Brain) from the execution environment (Hands), the system achieves both scalability and performance.

Three Core Components

ComponentRoleCharacteristics
SessionAppend-only event logDurable state store. Survives disconnections
HarnessAgent loop executionStateless. Horizontally scalable
SandboxIsolated execution containerDisposable. Provisioned on demand

In traditional architectures, inference must wait for container provisioning. With this decoupled design, Claude begins inference immediately upon pulling pending events from the session log, while container provisioning happens in parallel.

According to Anthropic's engineering blog, this design change reduced p50 TTFT (time to first token) by approximately 60% and p95 TTFT by over 90%.

Tool execution is abstracted to a simple interface: execute(name, input) -> string. The Harness knows nothing about tool implementation details, and the Sandbox knows nothing about inference. This loose coupling is what enables horizontal scaling.

Security Model

The security design deserves attention. OAuth tokens and credentials are stored in a dedicated vault outside the Sandbox. MCP tool calls are routed through a secure proxy. Repository access tokens are injected only during Sandbox initialization and are inaccessible to generated code.

What Are the Four Core Concepts?

The Managed Agents API is structured around four core concepts.

Agent

A reusable, versioned configuration bundle that combines the model, system prompt, tools, MCP servers, and skills. Created once, referenced by ID.

typescript
const agent = await anthropic.beta.agents.create({
  model: "claude-sonnet-4-6",
  name: "code-reviewer",
  system: "Review code for security vulnerabilities and performance issues.",
  tools: [{ type: "agent_toolset_20260401" }],
});
// Note: Requests require the "managed-agents-2026-04-01" beta header

Environment

A container template defining pre-installed runtimes (Python, Node.js, Go, etc.), network access rules, and mounted files.

Session

A running instance that combines an Agent and an Environment to execute a specific task. Sessions can run for hours and persist state across disconnections.

Event

Messages exchanged between your application and the agent — user instructions, tool results, and status updates streamed via SSE in real time.

Getting Started — Quickstart Guide

Here is the fastest path to trying Managed Agents.

Prerequisites

  • Anthropic API key (from the Console)
  • Node.js 18+ or Python 3.10+

Step 1: Install the SDK

bash
# TypeScript
npm install @anthropic-ai/sdk
 
# Python
pip install anthropic

Step 2: Create an Agent and Run a Session

typescript
import Anthropic from "@anthropic-ai/sdk";
 
const client = new Anthropic();
 
// 1. Create agent
const agent = await client.beta.agents.create({
  model: "claude-sonnet-4-6",
  name: "file-analyzer",
  system: "Analyze files and provide structured summaries.",
  tools: [{ type: "agent_toolset_20260401" }],
});
 
// 2. Start session
const session = await client.beta.sessions.create({
  agent_id: agent.id,
});
 
// 3. Send events and stream responses
const stream = await client.beta.sessions.events.create(session.id, {
  event: {
    type: "user.message",
    content: [
      {
        type: "text",
        text: "Analyze the current directory structure and summarize key findings.",
      },
    ],
  },
  stream: true,
});
 
for await (const event of stream) {
  if (event.type === "text_delta") {
    process.stdout.write(event.delta);
  }
}
// Note: The SDK automatically includes the "managed-agents-2026-04-01" beta header

Step 3: Interactive Testing with the CLI

bash
# Install the Anthropic CLI
brew install anthropics/tap/ant
 
# Run agent interactively
ant agent run --agent-id $AGENT_ID

Managed Agents is currently in public beta. Rate limits are set at 60 requests/minute for creation endpoints and 600 requests/minute for read endpoints. Check the official documentation for the latest limits before production use.

How Much Does It Cost?

Managed Agents billing has two dimensions.

1. Token Costs (Same as Standard API)

ModelInputOutput
Claude Sonnet 4.6$3/MTok$15/MTok
Claude Opus 4.6$5/MTok$25/MTok

2. Session Runtime ($0.08/hour)

Billed per session runtime, measured to the millisecond. Only time spent with status running counts — idle time waiting for user input or tool confirmation is not charged.

Real-World Cost Example

From Anthropic's official documentation: a 1-hour coding session with Claude Opus 4.6 consuming 50K input + 15K output tokens:

  • Input tokens: $0.25
  • Output tokens: $0.375
  • Runtime: $0.08
  • Total: $0.705

According to a BuildFastWithAI review, typical 4-6 hour agent sessions cost $1.50-$3.50 including model costs.

How Are Enterprises Using It?

Several major companies shared their adoption stories alongside the public beta launch.

  • Notion: Engineers and knowledge workers delegate tasks within their workspace. Multi-agent coordination enables dozens of tasks running in parallel
  • Rakuten: Specialist agents deployed across product, sales, marketing, and finance teams, integrated with Slack and Teams. Each agent took approximately one week to develop
  • Asana: Built "AI Teammates" — collaborative agents that work within projects, pick up tasks, and draft deliverables
  • Sentry: Connected a debugging agent to a PR-writing agent, automating the workflow from flagged bugs to reviewable fixes

Anthropic's internal benchmarks show that Managed Agents improved task success rates by up to 10 percentage points over standard prompting loops on structured file generation tasks, with the largest gains on the hardest problems.

Managed Agents vs. Agent SDK — Which Should You Choose?

Anthropic offers two paths for building with Claude: Claude Managed Agents and the Claude Agent SDK. Both share the same Claude models and MCP ecosystem, but they differ significantly in responsibility boundaries and operational models.

  • Claude Agent SDK: A Python / TypeScript library that exposes the same agent loop, tool execution, and context management that powers Claude Code. You import it into your own application, but you are responsible for deployment, scaling, monitoring, and sandboxing.
  • Claude Managed Agents: A fully managed service where Anthropic runs the agent loop, tool execution, runtime, safety, and scaling. No self-hosted infrastructure required.

Decision Guide

DimensionClaude Agent SDKClaude Managed Agents
Operational responsibilityYou (hosting, monitoring)Fully managed by Anthropic
FlexibilityHigh — full control over the loop and deployment shapeMedium — within the platform's design
Developer experienceTight local feedback loop during developmentHosted environment, great for long-running jobs
Best forEmbedding agent logic into your app and infrastructure / tight iteration while developingShipping to production fast / avoiding infra work / long-running, asynchronous jobs

Because both options use the same Claude models and support MCP, teams can realistically prototype with the SDK and deploy to Managed Agents (or vice versa) as projects mature. The clearest way to decide is to look at (1) your team's operational capacity and (2) how quickly you need to reach production.

How Does It Compare to Competitors?

Here is how the major AI agent platforms compare (this comparison draws on Composio's analysis).

AspectClaude Managed AgentsOpenAI Agents SDKGoogle ADK
Design philosophyOS-level control + managed infraMulti-agent orchestration via handoffsEnterprise graph-based workflows
InfrastructureFully managed by AnthropicSelf-managedVertex AI Agent Engine
OS accessBash, file system, webNone (external tools)None (external connectors)
Model supportClaude only100+ LLMsGemini-optimized, model-agnostic
SDK languages7Python, TypeScriptPython, TypeScript, Java, Go
Key differentiatorDeepest OS access, MCP ecosystemBroadest model access, voice supportA2A protocol, enterprise governance

Claude Managed Agents is available exclusively on the Claude Platform. It cannot be used through AWS Bedrock or Google Vertex AI. Organizations with multi-cloud strategies should factor this constraint into their evaluation.

FAQ

Q. What is the difference between Claude Managed Agents and Claude Code?

A. Claude Code is a CLI tool for interactive coding on your local machine. Managed Agents is a cloud API for running agents autonomously over long periods. They serve different purposes, and Anthropic explicitly prohibits mixing their branding.

Q. When should I use Claude Managed Agents vs. Claude Agent SDK?

A. The Agent SDK is a Python / TypeScript library that lets you embed the agent loop, tool execution, and context management directly into your own application — but you handle deployment and operations yourself. Managed Agents is a fully managed environment where Anthropic handles infrastructure, scaling, and safety. A good rule of thumb: choose the Agent SDK if you want fine-grained control in your own infrastructure or need a tight local feedback loop while developing; choose Managed Agents if you want to ship to production quickly or need to run long, asynchronous jobs. Since both share the same Claude models and MCP support, migrating between them later is practical.

Q. Is migration from the Messages API difficult?

A. The API structure differs, so code changes are required. However, the Agent → Session → Event flow is straightforward, and the SDKs handle Beta header configuration automatically. Anthropic's quickstart guide provides a clear migration path.

Q. What happens if a session disconnects?

A. Session state is persisted in an append-only event log. Reconnecting after a disconnection resumes from exactly where it left off.

Q. Is multi-agent coordination supported?

A. Yes, as a research preview (waitlist required). Agents can spawn and direct other agents for parallel work. General availability timing has not been announced.

Q. Can I run Managed Agents on-premises?

A. Not currently. Managed Agents runs exclusively on Anthropic's cloud platform. For on-premises requirements, building a custom agent infrastructure using the Messages API remains the alternative.

Summary

Claude Managed Agents removes the infrastructure barrier from AI agent development. The Brain-Hands architecture, session-based pricing, and 7-language SDK support let developers focus on agent behavior rather than plumbing.

That said, vendor lock-in to the Claude Platform, public beta reliability, and single-model support are real trade-offs. Enterprise teams should weigh these factors against the development speed gains.

As AI agents transition from experimentation to production deployment, managed platforms like this are an inevitable evolution. At ZenChAIne, we will continue to closely watch how this space develops and share our findings with the community.

References