Skip to content
Agents · Oct 29, 2026

Anthropic details managed-agent architecture behind Opus 5.5 launch

Engineering leads describe how Anthropic separates reasoning from execution in its Claude Platform, including sandbox isolation, credential handling, and evaluation workflows.

Trust79
HypeLow hype

1 source · cross-referenced

ShareXLinkedInEmail
TL;DR
  • Anthropic’s Opus 5.5 launch paired model improvements with platform changes to support managed agents.
  • The company separates an agent’s ‘brain’ (session log and harness) from its ‘hands’ (sandboxed execution environment) for reliability and security.
  • Sandboxes run without service credentials and attach them via proxy, limiting exposure if code is compromised.
  • Early access customers run evaluations in their own harnesses, reporting behavior that informs platform refinements.
  • Anthropic highlights memory and multi-agent workflows as areas of experimentation, with safety receiving increased attention.

Anthropic’s Opus 5.5 release was accompanied by platform changes aimed at supporting managed agents, according to Katelyn Lesse and Angela Jiang, heads of Engineering and Product at the company. The episode frames the launch as both a model and an API release, emphasizing improvements in model quality and cost efficiency alongside changes to how developers integrate the API.

The company describes a mental model that distinguishes an agent’s ‘brain’ from its ‘hands’: the session log and harness versus the sandboxed execution environment. This separation allows the harness to persist even if the sandbox fails, improving reliability and enabling lower-latency responses. It also simplifies security by ensuring that generated code runs in an environment without direct access to service credentials, which are attached via a proxy only when needed.

Managed Agents’ architecture isolates untrusted code execution behind strict network and credential controls. Anthropic’s containment write-up outlines the isolation and network policies used across its products, and the guests describe how credentials are held separately and attached through a proxy to the sandbox, limiting the blast radius if code is compromised.

Early access customers evaluate new models in their own harnesses, reporting both formal results and informal impressions. Anthropic values this feedback because it surfaces behaviors in customer environments that internal evaluations may miss. The company reiterates the importance of good evaluations, noting that harness design itself can resemble research when the goal is to measure behavior, inspect failures, and iterate.

The platform’s design also enables experiments in memory and multi-agent workflows. Dreaming, for example, is implemented by having one agent inspect another’s prior work and write memories back, building higher-level behavior from managed-agent primitives. While Anthropic highlights memory and learning as areas of interest, the team says more immediate attention has shifted to safety as model launches become more complex.

The guests emphasize that platform capabilities discussed—such as verifiers, parallel agents, and other strategies—are areas of experimentation rather than committed roadmap items. They also note that keeping the base harness simple allows developers to layer their own verification and orchestration logic on top.

Sources
  1. 01Latent Space — swyx — How Anthropic ships Claude with Claude: Separating the Brain from the Hands
Also on Agents

Stories may contain errors. Dispatch is assembled with AI assistance and curated by human editors; despite the trust-score filter, mistakes happen. We correct publicly — every article links to its revision history. Nothing here is financial, legal, or medical advice. Verify before relying on any claim.

© 2026 Dispatch. No ads. No sponsorships. No paid placement. Reader-supported via Ko-fi.

Built by a person who cares about honest AI news.