# dagger/container-use

Development environments for coding agents. Enable multiple agents to work safely and independently with your preferred stack.

Repository: https://github.com/dagger/container-use
Canonical: https://ross.abutalabs.com/products/container-use
Homepage: https://container-use.com
Language: Go
License: Apache-2.0
License Family: permissive
Last push: 2026-08-17T14:04:50+00:00

## Health v2 (maintenance only)
Score: 66/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 98, release rhythm 44, longevity 33
- inputs: {"age_days": 467, "days_push": 16, "days_rel": 379, "gap_med": 3, "n_releases_24m": 14}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 4021, forks 201 (observed 2026-08-28T04:08:32.549838+00:00)

## What it is
Container Use is an open-source MCP server and CLI tool that gives coding agents sandboxed containerized development environments, powered by Dagger and Git worktrees. It lets multiple agents work safely and independently in parallel, with full visibility into their command history and standard git workflows for reviewing their work.

## Use cases
- run multiple coding agents in parallel without conflicts
- sandbox AI agents so they don't touch my local files
- give Claude Code or Cursor isolated dev environments
- review what an AI agent actually did with full command logs
- intervene and take over an agent's terminal when it gets stuck
- discard failed agent experiments instantly
- use git branches to inspect each agent's work

## When to choose
- you run MCP-compatible coding agents like Claude Code, Cursor, or Goose and want isolated parallel environments
- you want sandboxed agent execution with real-time visibility and git-based review
- you need vendor-neutral agent infrastructure that works with any model or stack

## When to avoid
- you need a production-stable tool - the project is explicitly experimental and evolving
- you don't use Docker or MCP-compatible agents
- you just want a single agent working directly in your repo without isolation

## Facets
- artifact type: cli-tool
- maturity: experimental
- function: mcp, agent-framework, container-runtime, developer-tools, cli
- domain: developer-tools
- platform: windows, cli, cross-platform
- tags: coding-agents, sandboxed-environments, git-worktrees, parallel-agents, dagger, mcp-server, ai-agents, containers, automation, macos, linux, docker

## Member repositories
- dagger/container-use (main) score 66

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:08:32.549838+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T18:23:55.617771+00:00, confidence not recorded.
  - readme: https://github.com/dagger/container-use (fetched 2026-08-28T04:08:32.549838+00:00, sha 5aaf79c7adb7)
  - homepage: https://container-use.com (fetched 2026-08-29T09:16:40.835330+00:00, sha 914d31a72548)
  - site_page: https://container-use.com/quickstart (fetched 2026-08-29T09:16:40.854648+00:00, sha 3b2eb537f388)
  - site_page: https://container-use.com/agent-integrations (fetched 2026-08-29T09:16:40.888050+00:00, sha 468bfdc981a6)
- Data as of 2026-08-30T08:39:29.467469+00:00.