dagger/container-use

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

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 2 minutes ago
Added to GitGenius on September 17th, 2026
Created on May 23rd, 2025
Open Issues & Pull Requests: 62 (+0)
GitHub issues: Enabled
Number of forks: 205
Total Stargazers: 4,049 (+0)
Total Subscribers: 12 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 18.6 hours
Mean response time: 12.1 days
90th percentile: 39.9 days
Tracked items: 80

Most active contributors

Sign in to see contributor activity.

How this project is maintained

96% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 70% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 47
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 375 days
Stale 30+ days: 47
Stale 90+ days: 43

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (27)
  • enhancement (18)
  • good first issue (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Container-use is a tool for provisioning isolated development environments that allow multiple coding agents to work safely and independently.

The tool addresses the challenge of running multiple autonomous agents on the same codebase without interference or security concerns. It creates separate, sandboxed environments where each agent can operate with its own stack configuration, dependencies, and file system state. This isolation prevents agents from conflicting with one another or corrupting shared resources while still allowing them to work toward common goals on the same project.

Teams adopting this tool should consider it when orchestrating multiple coding agents that need to collaborate on a single repository or codebase. It suits projects where agent autonomy and safety are priorities, particularly in scenarios involving automated code generation, testing, or refactoring across parallel workflows. The tool is designed to integrate with existing development stacks rather than impose a specific technology choice, making it adaptable to different project requirements.

The project shows active development with regular commits addressing core functionality and infrastructure improvements. Work spans multiple areas including environment provisioning logic, agent communication patterns, and container orchestration details. The codebase receives consistent attention to both new capabilities and maintenance of existing systems.