Skip to main content
AI agents write and run code. Running that code on a developer’s machine puts it next to SSH keys, environment files, cloud credentials, and the corporate VPN — a large blast radius, no control over what the code reaches on the network, and no record of what the agent actually touched. Agent Sandbox gives that code somewhere safe to run: an ephemeral, isolated workload on your own Kubernetes cluster. Each sandbox is a scoped namespace with no access to developer machines or company secrets, its network egress is governed by policy, and every action is attributed to a developer or agent and logged. When the work is done, the sandbox is stopped or destroyed. It is a native capability of the mogenius platform — provisioned on demand through the UI, CLI, REST API, or SDK, and built on the existing operator, workspaces, RBAC, and audit log. Nothing leaves your infrastructure: sandboxes run on any cloud, on-prem, or air-gapped cluster you already operate.
The Sandboxes area on a cluster, showing running agent sandboxes with inline terminal, SSH, suspend, and delete actions.

Cluster › Sandboxes — the feature's home: installation status, the templates and warm pools that back it, and the agent sandboxes running on the cluster.

Agent Sandbox is built on the Kubernetes SIG agent-sandbox project. There is no proprietary runtime and no lock-in — the operator materializes standard custom resources, and mogenius adds the access, governance, and tooling around them.

​
Two ways to run

Agent Sandbox fits both common agent setups:
  • Agent outside, code inside — the agent runs in your IDE or a CI pipeline and requests a sandbox when it needs to execute something. The generated code runs only inside the sandbox, never on the machine that launched it. A single call creates the sandbox, runs the command, and tears it down.
  • Agent inside the sandbox — the whole agent runs within the sandbox (for example an OpenCode-style CLI), talking to a model through an endpoint you choose, including self-hosted models. Nothing persists beyond the sandbox’s lifetime.

​
How it relates to AI on mogenius

Agent Sandbox sits alongside the rest of the AI capabilities:
  • Agents are autonomous AI workers that watch your cluster and file proposals you review.
  • Agent Sandbox is where agent-generated or otherwise untrusted code executes — an isolated runtime, not an agent itself.
The two are complementary: use Agents to reason about your cluster, and Agent Sandbox to run code safely.

​
Explore

Concepts & architecture

Templates, warm pools, sandboxes, the lifecycle, and the isolation model.

Enable on a cluster

Turn Agent Sandbox on through the Platform Config — the admin’s setup.

Using sandboxes

Create and work with sandboxes from your workspace and the CLI.

SDK

Provision and drive sandboxes programmatically with @mogenius/sandbox.