AI agents do more than call APIs. They run shells, install packages, read files, and open network connections. Often they act on text they pulled from the internet a minute earlier. So every agent is untrusted code that holds real credentials. OpenShell , started by NVIDIA and now a CNCF Sandbox project , is a runtime for running agents like this safely. OpenShell runs each agent in a sandbox. A trusted supervisor outside the sandbox decides what the agent may reach. You declare four kinds of control in YAML: For Kubernetes admins, a key point is that OpenShell does not bring its own scheduler.

Its Kubernetes backend uses Agent Sandbox , the agents. io Sandbox resource from SIG Apps. Agents show up as Pods, Services, PVCs, Secrets, and NetworkPolicies, which you already know how to run. OpenShell adds what Kubernetes can't see: which agent is calling, which binary made the request, and whether a given POST may leave the cluster. A NetworkPolicy can say "this Pod may reach api. " It cannot say "curl may read issues but not create them. " OpenShell can, and it can change that rule on a running sandbox without a restart.

On Kubernetes, the OpenShell gateway owns every sandbox, and Agent Sandbox turns each one into Pods. The nirmata/demo-openshell repo runs the whole flow on a two-node kind cluster with Kubernetes 1. Its openshell-sandbox-lifecycle. md file describes each step in detail. Note 1: Currently, OpenShell sandboxes can only be created by calling the Gateway API and not via the Kubernetes API. There is an open issue ( openshell/#1719 ) for a Kubernetes OpenShellSandbox CRD, and an operator. Note 2: a Supervisor Pod per agent provides strong isolation, but may not scale well in large environments.

The roadmap includes flexible deployment options (see RFC 0018 ). The gateway creates the Kubernetes objects, and Agent Sandbox creates the agent Pod. The agent Pod has no outbound network access of its own. The supervisor opens the only connection to it, and every request the agent makes goes back over that connection for a policy check. Kyverno checks the Kubernetes objects at admission. OpenShell checks only the Pod settings it needs to stay safe. Which images run, how big a sandbox can get, which credentials it gets, and who can change OpenShell's RBAC are left t