#7373rd of 87 in Coding agents and assistants

container-use

MCP server that gives each coding agent its own container and git branch

Documentation ↗ Website ↗ Repository on GitHub ↗

Stars: 4.1k
License: Apache-2.0
Last commit: Aug 2026
Last release: Aug 2025
Language: Go

Missed the latest GitHub check; these facts may be older.

Overview

Container Use is an MCP server and CLI, written in Go on top of Dagger, that runs each coding agent in a fresh container tied to its own git branch. You add `container-use stdio` (alias `cu`) as an MCP server in Claude Code, Cursor, Goose, VSCode or another MCP-compatible agent. You can review command history and logs, open an agent's terminal, or `git checkout` its branch.

Who it is for: Developers running several coding agents in parallel on one repo

Strengths

Per-agent container and git branch lets several agents run in parallel without conflicts
Full command history and logs, plus a terminal you can drop into to take over
Works with any MCP-compatible agent through one `container-use stdio` entry
Review uses plain git: check out the agent's branch

Weaknesses

README labels it experimental and in early development
Built on Dagger; the README does not say what container runtime it needs
Last tagged release is 2025-08-19, well behind recent commits
Agent rules file is optional but must be appended to CLAUDE.md manually

What it needs

no GPU
Needs Dagger, git, MCP-compatible agent
Models: any model via MCP-compatible agents

Also in Coding agents and assistants

See all 87

Also in Coding agents and assistants
Rank	Project	Score
1	claw-codeRust CLI coding agent harness using Anthropic and OpenAI-compatible APIs194.9k starsMIT	83 out of 100
2	ArchonYAML workflow engine that runs AI coding agents through fixed dev steps23.7k starsMIT	82 out of 100
3	oh-my-openagentTerminal coding agent with multi-model orchestration and git-backed memory70.1k starscustom license	80 out of 100
#4	Open SWELangChain coding agent that plans, implements and reviews pull requests11k starsMIT	80 out of 100
#5	opencodeTerminal coding agent with build and plan modes, plus a desktop app213.8k starsMIT	79 out of 100

How to choose

Check which models it can use: your own keys, local models, or only the vendor's.
See what it may do without asking (edit files, run shell, push) and how you approve.
Prefer agents that work in a branch or worktree you can throw away.

Health

Releases: Not checked
Top contributor: Not checked
Security advisories: Not checked
Package advisories: Not checked
OpenSSF Scorecard: Not checked

Not read for this project yet: each refresh reads the facts of a few projects. Bots and coding-agent accounts are left out of the commit counts. Not part of the score: how we check.

License in plain words

Apache-2.0 Permissive

Use it at work: Yes
Change it and rebrand it: Yes
Sell it or host it for others: Yes

Your part: Keep the notices and mark the files you change. It also grants you the contributors’ patent rights.

A plain summary, not legal advice. Read the license on GitHub ↗ (opens in a new tab)

#73 of 87 in Coding agents and assistants on Archestack, as of 15 Oct 2026.

In your README

The badge updates twice a day.

[![Archestack](https://archestack.com/badge/dagger/container-use.svg)](https://archestack.com/best-of-vibe-coding/projects/container-use/)

How badges work

On your site or blog

A card with the rank, score and signals, in light or dark to match the reader.

<iframe src="https://archestack.com/embed/best-of-vibe-coding/container-use/" title="container-use on Archestack" width="400" height="270" style="border:0;max-width:100%" loading="lazy"></iframe>

Preview the card

Best of Vibe Coding on GitHub

Each review comes from the project's README and facts we check on GitHub. The fix form opens with container-use filled in.