Ross ROSS = Recommend OSS · open-source software intelligence for agents

dagger/container-use

Development environments for coding agents. Enable multiple agents to work safely and independently with your preferred stack. observed · 2026-08-28

github.com/dagger/container-use · homepage · Go · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

66/100

  • Activity 98
  • Release rhythm 44
  • Longevity 33
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 3
  • age_days: 467
  • days_rel: 379
  • days_push: 16
  • n_releases_24m: 14

Full methodology

Adoption not part of the score

4021 stars · 201 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

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

cli-tool · maturity experimental

mcp agent-framework container-runtime developer-tools cli developer-tools windows cli cross-platform coding-agents sandboxed-environments git-worktrees parallel-agents dagger mcp-server ai-agents containers automation macos linux docker

4 sources

Member repositories

RepositoryRoleHealth v2
dagger/container-usemain66

For agents

markdown · JSON · MCP: product_card(name="dagger/container-use")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem