Docker Sandboxes
Disposable, isolated sandboxes for AI agents like Claude Code, Gemini CLI, Copilot CLI, Codex, OpenCode, and Kiro that need safe, unattended execution.
macOS
$ brew trust docker/tap && brew install docker/tap/sbx
Windows
> winget install Docker.sbx

See it in action
Watch an agent install packages, run Docker, modify configs, and execute unattended. Then dispose of the sandbox in one command.
sbx-demo
Click “Run Demo” to start

Get started
macOS
$ brew trust docker/tap && brew install docker/tap/sbx
Windows
> winget install Docker.sbx
Why sandboxes
Agents do their best work when they have freedom. Sandboxes let them run fast without running wild, so speed and safety stop being a tradeoff.
Capabilities
Each agent runs inside a dedicated microVM with your dev environment and only your project workspace mounted in. Agents can install packages, modify configs, and spin up their own Docker containers. Your host stays untouched. No manual review, no permission prompts, no supervision required.
Network and filesystem controls you define.
Enforceable org-wide with Docker AI Governance.
Hard security boundary from the host.
Disposable by default. Faster than VMs.
Agents can spin up containers within Sandboxes.
Install packages, run services, work unattended.
Claude Code, Gemini CLI, Copilot CLI, Codex, Kiro, OpenCode.
Default –dangerously-skip-permissions Use permissive modes with confidence. In fact, that’s the default.


Gavriel Cohen
Creator of NanoClaw, NanoClaw
Ben Navetta
Engineering Lead, Warp

macOS
$ brew trust docker/tap && brew install docker/tap/sbx
Windows
> winget install Docker.sbx
FAQ
A sandbox is a microVM isolated environment that protects your filesystem and network from agents running inside it.
Out of the box we support Claude Code, Gemini CLI, Copilot CLI, Codex, OpenCode, Kiro. You can also create your own
YOLO mode (--dangerously-skip-permissions) gives agents autonomy with no approval prompts. Essential for speed, but risky without guardrails. Sandboxes make it safe by isolating each agent inside a dedicated microVM.
Sandboxes run fully isolated in microVMs, giving more isolation without paying the full cost of running a VM. This lets them do things that need more permissions safely, like running additional Docker containers.
No.
Installing Sandboxes covers core functionality. For centralized controls across a team such as network policies, filesystem rules, MCP governance: Docker AI Governance.
With Docker Sandboxes, your developers get isolated environments to run agents freely and safely. When your team needs to go further with network access restrictions, filesystem policies, and centralized admin controls, we can help you configure the right setup.
Docker AI Governance adds network access policies, filesystem controls, and org-wide MCP governance: defined once, enforced everywhere.
Talk to us about: