Agent Sandboxesagentsandboxes.org
Sandbox profile · Local / OS-level

Container Use

Answer in brief

Experimental Apache-2.0 MCP server and CLI from Dagger that gives each coding agent a fresh container on its own git branch, for review with log, diff and terminal before you merge, apply or delete. An experimental, git-centred way to give each local coding agent its own container and branch; best suited to parallel agent work you review before merging.

By the Agent Sandboxes editors · Updated

Overview

Container Use, from Dagger, "gives your coding agents sandboxed dev environments to work in, so they can run safely in parallel". It is an open-source MCP server that also works as a CLI (container-use or cu): you add container-use stdio as an MCP server to Claude Code, Cursor, Goose, Codex, Gemini CLI or another MCP-compatible agent, and each agent session creates a fresh environment from your current branch. An environment combines a container, built with Dagger on Docker from a configurable base image (Ubuntu 24.04 by default) plus setup and install commands, with a dedicated git branch that records every change and command.

You review work with container-use log, diff, terminal or checkout, then merge it, apply it as staged changes, or delete the environment. Secrets are configured as references (1Password, environment variables, HashiCorp Vault or files), resolved inside the container and stripped from logs and outputs. The README carries an "experimental" stability badge and says the project "is in early development"; the latest tagged release is v0.4.2 (August 2025), while the repository continues to receive commits.

Notable

  • README badge: stability experimental; "This project is in early development and actively evolving"
  • Latest tagged release v0.4.2 (19 August 2025); repository still active
  • Secret references are resolved inside the container and stripped from logs and command output

Container Use specifications

AttributeDetails
IsolationA container per environment, built and run through Dagger (Docker required), paired with a dedicated git branch via Git worktrees; each command runs "inside a NEW container within the environment"
DeploymentLocal / OS-level
Open sourceYes (Apache-2.0)
SDKs and interfacesCLI, MCP server
Cold start (vendor claim)Not documented
Max session lengthNot documented
PersistenceEach environment's changes and command history are tracked on its own git branch and survive across chats; an agent can resume an existing environment by its ID with the container state reused; an environment_checkpoint MCP tool saves an environment's current state as a container image to a registry destination
GPUNot documented
NetworkingBackground commands and services can expose ports, returning an environment-internal and a host-external address; egress policy is not documented
PricingFree (Apache-2.0)
Free tierFree
ComplianceNot documented
RegionsNot documented
Company headquartersNot documented

Facts from Container Use’s public documentation, verified November 18, 2026. Performance numbers are vendor claims.

Strengths and trade-offs

Strengths

  • You want to run multiple coding agents on one repo without them overwriting each other's work
  • You want to review agent work with ordinary git branches, diffs and merges
  • You want to drop into an agent's live container to debug when it gets stuck
  • You use any MCP-compatible agent rather than one specific vendor

Trade-offs

  • Labelled experimental; no tagged release since v0.4.2 in August 2025
  • Requires Docker and Git on the host; isolation is a container rather than a VM
  • Network egress controls are not documented

Good fit for: Running several coding agents in parallel on one repository, each in its own container and branch, and reviewing their work with git before merging.

How Container Use compares

SandboxCompany HQIsolationOpen sourceSelf-host / BYOCCold start (vendor)Max sessionSnapshots / pauseGPUSDKs
Container UseNot documentedDagger containerYesNo / NoNot documentedNot documentedYes / Not documentedNot documentedCLI, MCP server
Docker SandboxesUnited StatesMicroVMNoYes / NoNot documentedUntil removed (local)Yes / YesYessbx CLI, TypeScript (cloud), REST API (cloud)
agents-sandboxGermanymicrosandbox microVMYesNo / NoNot documentedNot documentedNot documented / Not documentedNot documentedCLI
MinimalNot documentednamespaces or libkrun microVMYesNo / NoNot documentedNot documentedNot documented / Not documentedNot documentedCLI, MCP server
nonoNot documentedLandlock / SeatbeltYesNo / NoNot documentedNot documentedYes / Not documentedNot documentedCLI, Rust, Python, JavaScript/TypeScript, Go
OpenHands RuntimeUnited StatesDocker containerYesYes / Not documentedNot documentedNot documentedNot documented / Not documentedNot documentedPython, JavaScript/TypeScript, REST API
Agent SafehouseNot documentedsandbox-exec (Seatbelt)YesNo / NoNot documentedNot documentedNot documented / Not documentedNot documentedCLI

Head-to-head: Agent Safehouse vs Container Use

See all Container Use alternatives →

Frequently asked questions

What is Container Use?
Experimental Apache-2.0 MCP server and CLI from Dagger that gives each coding agent a fresh container on its own git branch, for review with log, diff and terminal before you merge, apply or delete. An experimental, git-centred way to give each local coding agent its own container and branch; best suited to parallel agent work you review before merging.
How does Container Use isolate code?
Container Use documents its isolation as: A container per environment, built and run through Dagger (Docker required), paired with a dedicated git branch via Git worktrees; each command runs "inside a NEW container within the environment".
Is Container Use open source?
Yes (Apache-2.0).
How much does Container Use cost?
Free (Apache-2.0) Check the official pricing page for current rates.
Does Container Use support snapshots or pause and resume?
Snapshots: yes. Pause and resume: not documented. Each environment's changes and command history are tracked on its own git branch and survive across chats; an agent can resume an existing environment by its ID with the container state reused; an environment_checkpoint MCP tool saves an environment's current state as a container image to a registry destination.
What are the alternatives to Container Use?
Common alternatives include Docker Sandboxes, agents-sandbox, Minimal, nono, OpenHands Runtime, Agent Safehouse. See Container Use alternatives for a full comparison.

Sources

  1. container-use.com
  2. container-use.com/quickstart
  3. container-use.com/environment-workflow
  4. container-use.com/environment-configuration
  5. container-use.com/secrets
  6. container-use.com/agent-integrations
  7. github.com/dagger/container-use
  8. github.com/dagger/container-use/blob/main/mcpserver/tools.go
  9. github.com/dagger/container-use/releases
  10. dagger.io/privacy-policy

Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 18, 2026. Confirm anything that matters in the provider’s own documentation.

Cite this page

Agent Sandboxes. (2026). Container Use. agentsandboxes.org. Last reviewed November 18, 2026. https://agentsandboxes.org/sandboxes/container-use/