Give every agent and tool its own sandbox and run them at enterprise scale, governed by RBAC and admission policies.
An agent sandbox on Kubernetes limits what an AI agent can reach while it runs in your cluster. That's critical for security, but hardening a pod for every agent costs you scale, leaves you paying for idle infrastructure, and still has the agent and its tools sharing everything inside the pod.
With Cosmonic Control and the open source Cosmonic Agent SDK, agents and tools each run in separate, deny-by-default sandboxes that start with nothing, with many sandboxes sharing one host pod. That means you can run far more agents on far fewer nodes, and everything a sandbox can reach is declared as a line in a manifest your admission policies can check. Each sandbox is tiny, so you can run more than a million Codex agents on a single Kubernetes node.
In this post, we'll explain how sandboxed agents work on your cluster, why a sandbox for each component beats a pod for each special-purpose agent, and how Cosmonic Control ties your sandboxes into the Kubernetes controls you already use.











