Built 26/04/17 09:08commit f8ff6f9
Claude Managed Agents Overview
中文 | English
Summary
This source is Anthropic's product overview for Claude Managed Agents. It defines the public abstraction boundary for the offering: pre-built agent, environment, session, and event primitives for long-running work, plus a managed tool/runtime layer that replaces a user-built harness.
Source
- Raw file: raw/anthropic/Claude Managed Agents overview.md
- Translated raw file: raw/anthropic/Claude Managed Agents overview.zh.md
- Original URL: https://platform.claude.com/docs/en/managed-agents/overview
- Ingest date: 2026-04-13
Key Contributions
- Defines Managed Agents as a hosted alternative to building a custom loop around the Messages API.
- Makes the core public objects explicit: agent, environment, session, and event.
- Clarifies the default value proposition: secure cloud containers, built-in tools, persistent sessions, and minimal user infrastructure.
- Records concrete operational constraints that matter during adoption, including the
managed-agents-2026-04-01beta header and organization-level rate limits. - Shows that Anthropic positions Managed Agents as a long-running and asynchronous execution surface rather than just another prompting endpoint.
Strongest Claims
- Teams that do not want to own the harness, sandbox, and tool-runtime layers can buy those abstractions as a managed service instead.
- The stable product surface is not a raw model call but a set of durable runtime primitives that can outlive one specific implementation.
- Managed sessions matter because long-running agent work depends on persisted files and event history, not just a single context window.
Practical Implications For This Vault
- Treat managed-agent platforms as part of the harness-design landscape, not as a separate category unrelated to agent systems.
- Distinguish between sources about building a harness and sources about buying a hosted meta-harness with stable interfaces.
- Preserve adoption-critical details such as beta headers and rate limits on source pages instead of burying them only in raw docs.