company · explainer · draft

Anthropic (Managed Agents & capex)

Anthropic’s public systems story is Managed Agents (hosted harness: session, harness loop, sandbox) plus infrastructure investment announcements (e.g. US data centers with Fluidstack). Training fabric, inference edge, ASNs, and CDN maps are not publicly documented — keep them in Known unknowns.

In one sentence. Teaching only what Anthropic has published without inventing Claude API edge diagrams, GPU fabric TE, or rumor-based “lab network” topologies.

Why it exists

Managed Agents virtualizes Session (append-only event log), Harness (model + tool-call loop), and Sandbox (on-demand execution) so agents get isolation without always-on containers (engineering blog + platform docs). Capex announcements name computing investment and partner facilities — not packet-level network design. Cross-link: `/architectures/compute-orchestration/` for general compute abstractions; do not equate them to Anthropic internals.

Visual walkthrough

Walkthrough

Managed Agents: session → harness → model/sandbox

Published product harness path. Capex posts name facilities — training fabric and API edge stay in Known unknowns.

Step 1 / 3
Start / continueAppend eventsCallerSession logHarnessModelSandbox

A Managed Agents session is an append-only log of events. The harness owns the loop that calls the model and routes tool calls.

Control vs data plane

Control plane

Managed Agents control themes: session lifecycle, harness routing of tool calls, sandbox provisioning on demand. No primary discloses a Borg/K8s-equivalent cluster control plane or Internet BGP anycast strategy.

Data plane

Tool/code execution in provisioned sandboxes; model calls inside the harness loop. Training RDMA fabrics and inference serving paths are unpublished.

Request / packet path

North–south

Product/API north–south (CDN, anycast, PoPs, ASN) is a known unknown. Investment posts name Texas/New York Fluidstack facilities at announcement depth — not Front Door–style edge maps.

East–west

East–west inside training or inference clusters is unpublished. Do not invent RoCE/InfiniBand Clos from industry inference.

Scaling & math

Managed Agents posts publish approximate TTFT improvements — product metrics, not fabric oversubscription. Capex dollars are not topology. Reject third-party “OpenAI vs Anthropic network” rumor articles as non-primary.

When it breaks

  • Agent tool execution delayed or unavailable while sandboxes provision.

    Cause. On-demand sandbox provisioning path degraded (as published model: provision via tool calls).

    Mitigation. Treat sandbox provisioning as a dependency of the harness loop; do not invent unpublished scheduler topology.

  • Agent session state incomplete or unreproducible.

    Cause. Session append-only event log unavailable or truncated.

    Mitigation. Session is a published core abstraction — monitor session durability separately from model latency.

  • Cannot debug Claude API edge or training fabric with primary topology docs.

    Cause. No public Anthropic network/CDN/ASN architecture in curated primaries.

    Mitigation. Keep network in Known unknowns; cite only capex + Managed Agents materials.

Misconceptions

  • “Infrastructure investment announcements disclose training fabric TE.” — They name sites/partners at announcement depth, not RoCE/Clos designs.
  • “We can draw Claude’s public CDN/anycast edge from Managed Agents docs.” — Managed Agents is a product harness; edge networking is unpublished.

Reference expression

Primary: Managed Agents engineering blog; Managed Agents platform docs; infrastructure investment announcement. review: draft. Aggressive knownUnknowns are the honesty signal.

Standards & sources

Known unknowns

  • Training cluster network technology (RoCE, InfiniBand, topology, TE) — unpublished.
  • Inference / API edge (CDN, anycast, WAF path, PoPs, ASN) — unpublished.
  • Peering policy and relationship between announced Fluidstack sites and packet-level design.
  • Storage/database choices for Claude consumer products.
  • Chaos/SRE handbooks and multi-region traffic-shift algorithms.

Check yourself

  1. Managed Agents as published virtualizes…

    • Only BGP route reflectors
    • Session, harness loop, and sandbox
    • Jupiter Clos port counts
    • Open Connect OCAs

    Answer: Session, harness loop, and sandbox. Engineering blog: Session / Harness / Sandbox.

  2. Sandboxes in Managed Agents are described as…

    • Always-on for every session forever
    • Provisioned on demand via tool calls
    • Identical to Netflix embedded OCAs
    • FCC Gen2 satellite gateways

    Answer: Provisioned on demand via tool calls. On-demand provisioning is the published theme.

  3. Anthropic public network / CDN / ASN design is…

    • Fully documented like Cloudflare Unimog
    • A known unknowns wall in curated primaries
    • Proven by PeeringDB alone as primary
    • Identical to Azure Front Door VIP rings

    Answer: A known unknowns wall in curated primaries. Phase 7 ship rule: aggressive knownUnknowns.

  4. Infrastructure investment announcements should be read as…

    • Full packet-level fabric dumps
    • Capex / facility narratives — not topology disclosures
    • Proof of unlabeled inference edges
    • Service Fabric 2018 live maps

    Answer: Capex / facility narratives — not topology disclosures. Capex ≠ published network architecture.