Managed Agents: Anthropic Now Runs the Loop, Not Just the Model
Claude Managed Agents moves the agent loop, the sandbox and the session state onto Anthropic's infrastructure. The line nobody reads: it isn't eligible for Zero Data Retention or a HIPAA BAA — and self-hosting the sandbox doesn't buy that back.
- #managed-agents
- #claude-platform
- #sandbox
- #architecture
Sign in to keep reading
Managed Agents: Anthropic Now Runs the Loop, Not Just the Model — Claude Managed Agents moves the agent loop, the sandbox and the session state onto Anthropic's infrastructure. The line nobody reads: it isn't eligible for Zero Data Retention or a HIPAA BAA — and self-hosting the sandbox doesn't buy that back.
Your first guide is free. Sign in with Google or LinkedIn to read the whole library and get new guides as they ship — no cost.
Keep reading
More guides like this one.
Split Your Agents by Context, Not by Job Title
Most multi-agent setups fail because people split the work the way they would split it across a team — planner, coder, tester. Anthropic's own guidance calls that the anti-pattern. Here is the split that works, and the bill you are signing up for.
12 Agent Loops Worth Copying (One of Them Silently Does Nothing)
The obvious loop — /loop 20m /code-review — is a no-op: the bundled reviewer refuses model invocation, so a scheduled fire delivers it as plain text. Here are 12 loops that actually run, grouped by the only thing that distinguishes them, plus the caps that quietly kill them.
Subagents: Spend Tokens Without Spending Your Context
Anthropic's own data says the tokens an agent spends predict most of its performance — but in one session, every token lands in the same window as your plan. Subagents break that link. Here's the three-line file, the defaults that changed, and when to skip them.