R122 · Infrastructure for agents at scale › Agent session hosting and control planes

Agent Substrate: suspend idle agents, resume them on a warm pool

Read the original

agent-sandboxkubernetesagent-runtimesecurityopen-source

Source: agent-substrate/substrate (Apache-2.0, Go, about 7k GitHub stars in November 2026). Surfaced by Charly Wargnier on LinkedIn, who describes it as contributed by Google to the CNCF; the repo itself points to a GKE install guide, Google's Agent Executor as a reference harness, and CNCF Slack channels for the community.

What it is

Agent Substrate is a runtime on standard Kubernetes for very large numbers of sandboxed, mostly idle agents. Its premise: an agent spends most of its life waiting on a model, a tool or a human, yet a sandboxed single-tenant Pod keeps holding CPU, memory and a Pod slot the whole time. Substrate separates the actor (the stateful agent instance) from the worker (a pre-started sandbox Pod). Idle actors are snapshotted out of memory; when a request arrives, the router resumes the actor onto any free worker. The project calls this "actor teleport" and claims 10x to 30x oversubscription, resume under 500 ms, and more than 500 activations a second (the demo multiplexes about 250 actors onto 8 Pods). Its stated north-star targets are 100 ms p95 activation, 1 billion actors per cluster and 1,000 wakeups a second.

It is deliberately a low-opinion runtime, not an agent SDK. Workloads are ordinary OCI images; the README lists ADK, LangChain, Claude Code, Codex, Antigravity and MCP servers as tenants, and kagent 1.0 uses it as its execution layer. It reached 1.0 with a public-API compatibility promise.

Architecture

Tradeoffs

Failure modes to plan for

Review checklist

Connections

See R122 on the knowledge map

Part of the Research notes on nowucca.com. Figures and claims are the source's own unless the summary says otherwise.