This article was originally published on avinashsangle.com.
Anthropic launched Claude Managed Agents in beta on April 8, 2026. It's a hosted service that runs long-horizon Claude agents in Anthropic's infrastructure - sandboxed, persistent, and integrated with MCP servers out of the box.
If you're choosing between Managed Agents and the Agent SDK, the short answer is:
- Pick Managed Agents for multi-hour production workloads
- Pick the Agent SDK when you need full control over the runtime
Here's the breakdown after digging through the docs and API.
TL;DR
- Managed Agents = Anthropic runs the agent harness, sandbox, and runtime for you (hosted, beta)
- Agent SDK = you run the same engine yourself, with full control over infrastructure
- Pricing: standard token rates + $0.08 per session-hour of active runtime + $10 per 1,000 web searches
- Early adopters: Notion, Rakuten, Asana - focused on long-running enterprise workflows
- Beta header required:
managed-agents-2026-04-01
The Core Difference
Think of it like this:
- Managed Agents = Vercel (hosted, opinionated, pay-per-use)
- Agent SDK = self-hosted Next.js (you run it on your infra)
Same underlying engine. Different operational trade-offs.
Managed Agents handles the agent loop, sandboxed code execution, file system access, web browsing, persistent sessions, and checkpointing for you. You send a prompt, connect your MCP servers, and the agent runs - even for hours - without you maintaining any of that runtime infrastructure.
The Agent SDK exposes the same engine for self-hosted runtimes. You get local file access, private network connectivity, custom tool execution, and full runtime control. No session-hour charges - just token costs.
Pricing
Managed Agents pricing on top of standard Claude API rates:
- $0.08 per session-hour of active runtime
- $10 per 1,000 web searches
- Idle time is free - sessions can wait for input without billing
For a 2-hour research task, you're looking at roughly $0.16 in compute plus token costs. For zero infrastructure management, that's a strong tradeoff for production workloads.
When to Pick Which
Pick Managed Agents when:
- You have multi-hour production workloads (research, batch processing, monitoring)
- You need sandboxed code execution out of the box
- Web browsing + MCP integrations matter
- You don't want to build or maintain agent infrastructure
Pick Agent SDK when:
- You need local file access (working against repos)
- Private network access required
- Custom tool execution logic
- You want predictable token-only costs without session-hour pricing
- Development and debugging - the SDK lets you inspect everything
What You Get Out of the Box with Managed Agents
- Sandboxed containers with code execution, file system, and web access
- Sessions can run for hours with checkpointing for fault tolerance
- MCP server support - any MCP server you've built for Claude Desktop or Claude Code can be configured for a Managed Agent session
- Built-in web browsing and search
Beta Status
Managed Agents is currently in beta. All endpoints require the beta header:
anthropic-beta: managed-agents-2026-04-01
The official Anthropic SDKs set this automatically when you use the beta namespace. Some features like multi-agent orchestration remain in limited research preview.
The Bigger Picture
Notion, Rakuten, and Asana are early adopters - all using Managed Agents for enterprise workflows where the agent needs to run for extended periods, integrate with internal tools via MCP, and survive infrastructure failures.
This is Anthropic moving up the value chain: instead of just selling the model, they're selling the complete runtime that wraps it. For teams without dedicated AI infrastructure, that's a meaningful shift.
Read the full deep-dive with code examples, pricing math, and a decision flowchart on the original post: Claude Managed Agents vs Agent SDK on avinashsangle.com.
Top comments (0)