Claude Managed Agents

Overview

Claude Managed Agents is Anthropic’s hosted agent runtime on the Claude Platform: a pre-built, configurable harness that runs Claude as an autonomous agent in managed (or self-hosted) infrastructure. It is a real product in public beta as of 2026—not a rumor, not a rename of Claude Code, and not the same thing as the Claude Agent SDK. Official launch: April 8, 2026 (public beta blog + engineering post). Product home: claude.com/blog/claude-managed-agents. Platform docs: platform.claude.com/docs/en/managed-agents.

Maker: Anthropic. Primary job: let developers define agent configs (model, system prompt, tools, MCP servers, skills) and run long-horizon sessions where Anthropic (or your sandbox) handles the agent loop, tool execution, sandboxing, session persistence, and crash recovery—while your app sends events and streams results over a REST/SSE API.

Anthropic positions Managed Agents next to the Messages API as one of two main build paths: Messages for direct model prompting and custom loops; Managed Agents for long-running and asynchronous agent work without building your own harness, sandbox, and state layer. It is also distinct from Claude Code (interactive coding product) and the Claude Agent SDK (library that runs the Claude Code harness in your process). SDK docs state a common path is prototype with Agent SDK locally, then move production long-running jobs to Managed Agents.

Key features

• Four core concepts — Agent (model, system prompt, tools, MCP, skills; versioned, reusable), Environment (cloud sandbox or self-hosted sandbox config), Session (running instance with durable event log and sandbox workspace), Events (user messages, tool results, status updates; SSE stream).
• Managed harness + infrastructure — Anthropic runs the agent loop: tool routing, prompt caching, compaction-style context handling, and recovery. You do not implement the outer “while tool_use” loop for the hosted path.
• Per-session sandbox — Container workspace for bash, file read/write/edit/glob/grep, code execution. Engineering blog (“Scaling Managed Agents,” Apr 8, 2026) describes decoupling the “brain” (harness) from the “hands” (sandbox/tools) and the durable session log so containers and harnesses are replaceable cattle, not pets.
• Built-in tools — Bash; file operations; web search and fetch; MCP servers to external systems. Custom tools: Claude requests a tool call; your app (or MCP path) executes and returns results.
• Long-running, stateful sessions — Sessions designed for minutes-to-hours of multi-step work; history and sandbox state persist server-side; you can interrupt, steer mid-run, resume after disconnect, and delete sessions via API.
• Vaults & credentials — OAuth and secrets kept outside the sandbox (vault + proxy patterns). Git remotes can be wired with tokens at provision time so the agent never handles raw credentials in the shell.
• Self-hosted sandboxes — Environments can target sandboxes on your infrastructure for VPC, compliance, or data-residency constraints (alongside Anthropic-managed cloud sandboxes).
• Scheduled deployments — Cron-style recurring agent runs with run history, for unattended batch or recurring workflows.
• Memory, multi-agent, dreaming (staged) — Cross-session memory and multi-agent coordination appear in product updates; multi-agent and self-evaluation/outcome loops, plus “dreaming,” are called out as research preview / limited access in launch and follow-on posts—request access via Anthropic’s Managed Agents form where required. MCP tunnels are similarly gated in research preview.
• Observability — Session tracing, tool-call inspection, and troubleshooting surfaces in the Claude Console.
• Claude Platform on AWS — Managed Agents available through direct Claude API and Claude Platform on AWS (feature matrix may differ; check platform docs for session behavior differences).
• Customer production patterns (Anthropic-published) — Coding agents that plan/fix/PR; workspace agents (e.g. Notion Custom Agents alpha); enterprise specialist agents (Rakuten); Asana AI Teammates; Sentry Seer handoff to patch+PR; similar stories from Atlassian, Vibecode, and others on the launch blog.

Pricing

Claude Managed Agents is usage-based: standard Claude Platform token rates for whatever model the session uses, plus a separate session runtime charge. There is no flat monthly “Managed Agents seat” SKU in public docs—you need a Claude API key / Console billing (and whatever enterprise agreement you already have).

Component	What you pay	Notes
Model tokens	Per-model input/output (and cache) rates	Same table as Messages API model pricing (e.g. Haiku 4.5, Sonnet 5 / 4.6, Opus 4.x, higher-tier Fable/Mythos when available)
Prompt caching	Standard cache write/hit multipliers	Applies inside Managed Agents sessions
Web search (in session)	~$10 per 1,000 searches + tokens	Same server-tool pricing as platform
Session runtime	$0.08 per session-hour	Metered to the millisecond while status is running only

Runtime metering: Official pricing docs state runtime accrues only while the session is running. Time spent idle (waiting for your next message or a tool confirmation), rescheduling, or terminated does not count. Session runtime replaces separate Code Execution container-hour billing for Managed Agents—you are not double-billed container hours on top of the $0.08/hour SKU.

Worked example (from Anthropic pricing docs): a one-hour coding session on Claude Opus 4.8-class rates with 50k input and 15k output tokens ≈ $0.25 input + $0.375 output + $0.08 runtime ≈ $0.705. With prompt cache hits on most of the input, the same shape can fall near ~$0.525. Tokens still dominate cost on heavy Opus agent loops; the runtime line is small relative to multi-hour Opus sessions but matters at high concurrency.

What does not apply to Managed Agents sessions: Batch API 50% discount, Fast mode premium, Messages-style inference_geo data-residency multiplier as a session field, and partner Bedrock/Vertex-style cloud platform packaging for this product path (Managed Agents is first-party / Claude Platform on AWS oriented—not “drop-in on partner Messages endpoints” in the same way). On Claude Platform on AWS, token + runtime charges convert to Claude Consumption Units (CCUs) like other platform usage.

Limits & gotchas

• Still beta — Endpoints require the Managed Agents beta header; behaviors can change. Treat production designs as API-versioned and pin agent versions for rollouts.
• Not ZDR / not HIPAA-eligible (as of docs mid-2026) — Because sessions are stateful and transcripts persist until you delete them, Managed Agents is not currently eligible for Zero Data Retention or HIPAA BAA coverage. You can delete sessions and uploaded files via API; that is not the same as ZDR. Compliance-sensitive teams must verify current feature eligibility tables before design sign-off.
• Claude-only hosted runtime — This is not a multi-model orchestrator. If you need vendor-neutral agents on your own cluster, look at self-hosted stacks (Agent SDK + your infra, LangGraph/Deep Agents, CrewAI, open “Multica”-style platforms, etc.).
• SDK code ≠ Managed Agents deploy — Anthropic and third-party docs are explicit: Agent SDK runs in your process; Managed Agents is a separate hosted REST product. There is no one-click “push this SDK app to Managed Agents.”
• Research-preview gates — Multi-agent coordination, dreaming, MCP tunnels, and some outcome/self-eval loops may need extra access. Do not plan GA roadmaps solely on preview features.
• Rate limits (org-level, separate from Messages) — Platform rate-limit docs list Managed Agents create endpoints around 300 RPM and read/stream endpoints around 1,200 RPM (verify current table for your tier). Concurrent long sessions still hit model capacity and spend limits.
• Security model is structural, not magic — Engineering blog details why credentials must stay outside the sandbox (prompt injection + code execution). Misconfigured MCP, overly broad tools, or weak vault scoping still create real risk.
• Vendor lock-in on session state — Durable event logs and sandboxes live on Anthropic’s side (or your self-hosted sandbox still under their harness contracts). Export/delete discipline and architecture boundaries matter for exit plans.
• Confusion tax — Naming sprawl (Claude, Claude Code, Cowork, Agent SDK, Managed Agents, Messages API, Console) causes wrong-product purchases. Managed Agents is for productized/cloud agent backends, not “chat with Claude” and not the default interactive coding UX.

Community sentiment

Launch-week Hacker News (April 2026, blog + docs threads) and Reddit (r/ClaudeAI, r/ExperiencedDevs) treated Managed Agents as a serious infrastructure move: less “new model,” more “Anthropic will run the agent loop and sandbox for you.” Praise clusters around removing months of sandboxing, credentials, tracing, and long-session reliability work—especially for teams already all-in on Claude quality.

Praise themes: production path for Notion/Asana/Sentry-style integrations; clearer split between Messages vs hosted agents; $0.08/hour runtime seen as fair relative to DIY container fleets; engineering write-up on brain/hands decoupling and TTFT improvements resonated with infra engineers; “10x faster to production” read as development speed, not model IQ (community and Medium explainers stress this).

Criticism / skepticism: product-name fatigue across Claude surfaces; lock-in concerns vs open harnesses; beta + research-preview features not ready for every enterprise checklist; cost opacity when agents thrash tokens; some HN comments that a good model + DIY loop already works for simple agents; open-source “self-hosted managed agents” projects (e.g. Multica comparisons in mid-2026 blogs) positioned as escape hatches for multi-vendor or air-gapped needs.

Who should use it

• Product and platform teams shipping user-facing or internal agents that must run for long periods with auditability, without staffing a full agent-infra team.
• SaaS builders embedding Claude agents (support, coding fix bots, research, document workflows) who want Anthropic-operated sandboxes and session durability.
• Enterprises already standardized on Claude that need scoped permissions, vault-backed MCP, tracing in Console, and optional self-hosted sandboxes—and can accept stateful retention rules.
• Teams past the prototype stage who outgrew local Agent SDK or custom Messages loops on reliability, scale, or ops cost.

Who should not start here: individuals who only need Claude Code in the terminal/IDE; apps that must stay multi-model and fully self-hosted; workloads that hard-require ZDR or HIPAA on the agent transcript path today; simple single-turn chat that the Messages API already covers.

Alternatives

• Claude Code — Interactive coding agent (CLI/IDE/web). Choose for human-in-the-loop software work, not as a multi-tenant hosted runtime API.
• Claude Agent SDK — Same family of tools/loop as Claude Code, in Python/TypeScript on your machines. Choose for local/VPC control and in-process custom tools; not a drop-in Managed Agents deploy target.
• OpenAI / Assistants & agent platforms — Competing model + hosted agent primitives if your stack is OpenAI-first.
• LangGraph / LangChain Deep Agents — Graph orchestration with managed or self-hosted deploy options; better when you need framework-level control and multi-vendor models.
• CrewAI — Multi-agent orchestration library/platform if you want role-based crews and OSS flexibility.
• n8n — Workflow automation with AI nodes when the problem is integrations and pipelines more than long-horizon sandbox agents.
• Devin — End-user autonomous software engineer product vs DIY agent APIs.
• Cursor / GitHub Copilot — IDE-centric coding assistants, not general hosted agent infrastructure.
• Replit / cloud dev agents — Full app-hosting + agent experiences for builders who want the environment and the model together.
• Self-hosted “managed agents” OSS (e.g. Multica-style platforms covered in 2026 comparison posts) — When you need multi-coding-agent fleets on your own infra without Anthropic runtime lock-in.

Verdict

Claude Managed Agents is a real mid-2026 Anthropic product: a beta hosted runtime for long-horizon Claude agents (Agents + Sessions + Environments + Events), priced at standard tokens plus $0.08 per running session-hour. It has not been quietly renamed into Claude Code; it sits beside Code, Cowork, the Agent SDK, and the Messages API as the “Anthropic runs the harness and sandbox” option.

Choose it when shipping production agents faster than you can build secure sandboxes, durable sessions, and ops yourself—and when Claude-only + stateful retention is acceptable. Prefer Agent SDK or open orchestrators when you need full control, multi-model, or compliance features Managed Agents still excludes. Bottom line: honest infrastructure product, strong fit for Claude-centric production agents, still beta with compliance and lock-in trade-offs that matter on the procurement checklist.