🧠Anthropic Splits Claude Agents Into Brain, Hands, and Session Log
Your agent containers can finally die without killing the agent
TL;DR
Anthropic's Claude Managed Agents now splits the harness, sandbox, and session log into independent pieces. Failed containers get reinitialized from a standard recipe, and credentials stay out of reach of generated code. If you run long-horizon agents, this is the reliability fix you've been hand-rolling.
Anthropic rebuilt Claude Managed Agents so the parts that run your agent can fail independently. The original design crammed everything into one container. That made debugging a nightmare and recovery worse. If you're building long-running agents, this matters because the failure modes are the real product. The harness, which calls Claude and routes tool calls, now sits outside the container and treats it like any other tool. The sandbox is cattle: when it breaks, you reinitialize it from a standard recipe instead of babysitting it. The session is an append-only log of every event, living outside Claude's context window. Its getEvents() interface lets the brain pull positional slices of history instead of stuffing everything into the prompt. Credentials are never reachable from the sandbox running Claude's generated code, enforced either by bundling auth with a resource or holding it in an external vault. Watch how fast the interfaces stabilize. Anthropic says each piece can be swapped without disturbing the others, which is a promise worth testing against your own infrastructure.

Key Points
The session is an append-only log of every event, kept outside Claude's context window, so history survives even when the harness or sandbox dies mid-task.
Keep reading — it's free
Enter your email to keep reading — plus the best of AI & tech, daily. Free, forever.
Already a member? Sign in
Comments
Be the first to comment