Containerized environments for coding agents. Multiple agents can work independently, isolated in fresh containers and git branches. No conflicts, many experiments. Full execution history, terminal access to agent environments, git workflow. Any agent/mod
Container Use lets coding agents do their work in parallel environments without getting in your way. Go from babysitting one agent at a time to enabling multiple agents to work safely and independently with your preferred stack. See the full documentation.
It's an open-source MCP server that works as a CLI tool with Claude Code, Cursor, and other MCP-compatible agents. Powered by Dagger.
git checkout <branch_name>
to review any agent's work.🦺 This project is in early development and actively evolving. Submit issues and/or reach out to us on Discord in the #container-use channel.
# macOS (recommended)
brew install dagger/tap/container-use
# All platforms
curl -fsSL https://raw.githubusercontent.com/dagger/container-use/main/install.sh | bash
Container Use works with any MCP-compatible agent. The setup is always the same: add container-use stdio
as an MCP server.
👉 Complete setup guide for all agents (Cursor, Goose, VSCode, etc.)
Example with Claude Code:
# Add Container Use MCP server
cd /path/to/repository
claude mcp add container-use -- container-use stdio
# Add agent rules (optional)
curl https://raw.githubusercontent.com/dagger/container-use/main/rules/agent.md >> CLAUDE.md
The container-use
command is also available as cu
for convenience. Both commands work identically:
container-use stdio
(used in documentation)cu stdio
(shortcut)Ask your agent to create something:
Create a hello world app in python using flask
Your agent will work in an isolated environment and give you URLs to view the app and explore the code!