Claude Managed Agents overview – Claude API Docs

Anthropic offers two ways to build with Claude, each suited to different use cases:

Claude Managed Agents provides the harness and infrastructure for running Claude as an autonomous agent. Instead of building your own agent loop, tool execution, and runtime, you get a fully managed environment where Claude can read files, run commands, browse the web, and execute code securely. The harness supports built in prompt caching, compaction, and other performance optimizations for high quality, efficient agent outputs.

Claude Managed Agents is built around four concepts:

Concept	Description
Agent	The model, system prompt, tools, MCP servers, and skills
Environment	A configured container template (packages, network access)
Session	A running agent instance within an environment, performing a specific task and generating outputs
Events	Messages exchanged between your application and the agent (user turns, tool results, status updates)

1. Define the model, system prompt, tools, MCP servers, and skills. Create the agent once and reference it by ID across sessions.

2. Configure a cloud container with pre-installed packages (Python, Node.js, Go, etc.), network access rules, and mounted files.

3. Launch a session that references your agent and environment configuration.

4. 4

   Send events and stream responses

   Send user messages as events. Claude autonomously executes tools and streams back results via server-sent events (SSE). Event history is persisted server-side and can be fetched in full.

5. Send additional user events to guide the agent mid-execution, or interrupt it to change direction.

When to use Claude Managed Agents

Claude Managed Agents is best for workloads that need:

• Long-running execution – Tasks that run for minutes or hours with multiple tool calls
• Cloud infrastructure – Secure containers with pre-installed packages and network access
• Minimal infrastructure – No need to build your own agent loop, sandbox, or tool execution layer
• Stateful sessions – Persistent file systems and conversation history across multiple interactions

Claude Managed Agents gives Claude access to a comprehensive set of built-in tools:

• Bash – Run shell commands in the container
• File operations – Read, write, edit, glob, and grep files in the container
• Web search and fetch – Search the web and retrieve content from URLs
• MCP servers – Connect to external tool providers

See Tools for the full list and configuration options.

Claude Managed Agents is currently in beta. All Managed Agents endpoints require the managed-agents-2026-04-01 beta header. The SDK sets the beta header automatically. Behaviors may be refined between releases to improve outputs.

To get started, you need:

1. A Claude API key
2. The beta header above on all requests
3. Access to Claude Managed Agents (enabled by default for all API accounts)

Certain features (outcomes, multiagent, and memory) are in research preview. Request access to try them.

Managed Agents endpoints are rate-limited per organization:

Operation	Limit
Create endpoints (agents, sessions, environments, etc.)	60 requests per minute
Read endpoints (retrieve, list, stream, etc.)	600 requests per minute

Organization-level spend limits and tier-based rate limits also apply.

For partners integrating Claude Managed Agents, use of Claude branding is optional. When referencing Claude in your product:

Allowed:

• “Claude Agent” (preferred for dropdown menus)
• “Claude” (when within a menu already labeled “Agents”)
• “🔥 Powered by Claude” (if you have an existing agent name)

Not permitted:

• “Claude Code” or “Claude Code Agent”
• “Claude Cowork” or “Claude Cowork Agent”
• Claude Code-branded ASCII art or visual elements that mimic Claude Code

Your product should maintain its own branding and not appear to be Claude Code, Claude Cowork, or any other Anthropic product. For questions about branding compliance, contact the Anthropic sales team.