Claude Managed Agents on Agent Sandbox
Run Claude Managed Agents self-hosted sandbox work items — bash and file tool calls — inside Sandbox pods, with lease hand-off, warm-pool claims, and idle suspend/resume.
Managed agent platforms host the agent loop — model, prompts, session
state, event history — as a service, and delegate tool execution (bash,
file operations, skills) to infrastructure you run yourself through a work
API. Each subdirectory here bridges one platform’s work API to
Agent Sandbox, so every agent session’s
tool calls run in an isolated, warm-pool-claimed, suspend/resume-capable
Sandbox pod.
Platform work API → controller (poll/dispatch) → one Sandbox per session → in-sandbox runner executes tool calls → idle sessions suspended, resumed on the next work item.
A managed-agents bridge needs exactly the properties the Sandbox CRD and
its extensions provide. The mapping is one-to-one:
| Platform need | Agent Sandbox feature |
|---|---|
| One isolated environment per session | One Sandbox (pod-backed, singleton) per session, claimed through a SandboxClaim |
| Low claim latency on every new session | SandboxWarmPool keeps pre-warmed sandboxes ready; a claim binds one in seconds instead of cold-starting a pod |
| Density: idle sessions must not burn nodes | Suspend terminates the pod while keeping the Sandbox object; Resume brings it back on the next work item |
| Session file state must survive suspension | volumeClaimTemplates PVCs are retained across suspend/resume and reattached to the new pod |
| A control channel to the in-sandbox daemon | Apiserver-brokered port-forward (no ingress needed), or the sandbox-router for larger fleets |
| Tenant workloads stay declarative | Everything the bridge owns is a CR: SandboxTemplate, SandboxWarmPool, SandboxClaim |
Every bridge in this directory has the same three moving parts; only the platform protocol differs:
┌─────────────────────┐ platform work API ┌─────────────────────────────┐
│ Managed agent │ ◄───────────────────── │ controller (local process) │
│ platform │ claim/ack/lease, │ ├─ poller loop │
│ (e.g. Anthropic) │ tool results │ ├─ session manager │
└─────────▲───────────┘ │ │ (per-session FIFO) │
│ │ └─ GC loop (idle→Suspend) │
│ tool calls executed, results └───┬──────────────▲──────────┘
│ streamed back by the runner │ Go SDK claim │ port-forward
┌─────────┴───────────┐ POST /work, GET /status │ suspend/ │ (via apiserver)
│ runner (in sandbox, │ ◄──────────────────────────┘ resume │
│ HTTP daemon) │ │
└─────────────────────┘
EnsureReady (claim or resume +
re-establish the port-forward), dispatch the work item, wait for the runner
to report completion, then let the session go idle.What each bridge implements on top of this shape: the platform-specific
work protocol (poll/ack/lease semantics, credentials), the runner
image (platform SDK + shell/tool dependencies), and the manifests
(SandboxTemplate + SandboxWarmPool).
| Directory | Platform | Work protocol |
|---|---|---|
| claude-managed-agents | Claude Managed Agents self-hosted sandboxes | poll → ack → heartbeat lease hand-off to the in-sandbox worker |
SandboxTemplate / SandboxWarmPool / SandboxClaim)
installed — EXTENSIONS=true make deploy-kind on kind.SandboxTemplate.Each bridge’s own README covers its setup, quick start, and protocol details.