Agent
An agent definition bundles the model, system prompt, tools, MCP servers, and skills you want to reuse.
Use this page when you need a compact explanation of the hosted runtime, the core concepts, and the workloads that match Managed Agents best.
Last updated
2026-04-12
Anthropic’s overview keeps the product grounded in four primitives. That mental model is enough to start.
An agent definition bundles the model, system prompt, tools, MCP servers, and skills you want to reuse.
An environment defines the hosted container template, including packages, files, and network access rules.
A session is the running instance that performs a task, streams events, and keeps a durable event history.
Events are the messages and tool updates your application sends and receives while the session works.
This split is the fastest way to understand where Managed Agents ends and your application begins.
| Dimension | What you own | What Anthropic owns |
|---|---|---|
| Build and runtime responsibilities | You define the agent configuration, environment settings, session creation, user events, and how your app consumes outputs. | Anthropic provides the hosted harness, session model, event persistence, and managed container runtime. |
| Operational responsibilities | You decide the task, guardrails, custom tools, and product UX around the agent. | Anthropic handles the underlying service that runs the agent loop, tool execution flow, and session lifecycle primitives. |
Anthropic explicitly recommends Managed Agents for long-running tasks, cloud infrastructure, minimal infrastructure burden, and stateful sessions.
Use it for long-running work that benefits from built-in tool access and a durable session log.
Use it when you want Anthropic-managed cloud infrastructure instead of building your own harness and sandbox.
Do not use it just because the task is “agentic.” If you only need a short request-response loop, start smaller.
Do not confuse it with Claude Code if the real user is a human developer in an IDE or terminal.
This explains why the product exists instead of simply telling you that Claude can already use tools.
The engineering post is helpful here: Anthropic describes Managed Agents as a service designed to keep the interfaces around Claude stable even as the underlying harness changes. That is why the docs focus on sessions, sandboxes, and events instead of exposing every implementation detail.
These questions help reset expectations before a team jumps into implementation.
No. Anthropic treats the Messages API and Managed Agents as two different build paths: one gives you direct prompting access, the other gives you a pre-built configurable agent harness on managed infrastructure.
Not by default. Anthropic documents access as enabled by default for API accounts, but features such as outcomes, multiagent, and memory are still research preview.
These pages are the shortest path to the next question most teams hit.
Use this guide to build the first working Managed Agents session without mixing up agents, environments, sessions, and event streams.
Open pageUse this comparison when the real choice is between Anthropic-managed infrastructure and a programmable SDK stack you operate yourself.
Open pageUse this page to separate a hosted agent service from the developer-facing Claude Code product.
Open pageUse the waitlist if you want the next update without checking the docs every week.
Waitlist
Get a short email when this guide adds new examples, API changes, or managed-agents implementation notes.