Skip to content

dagger/container-use

v0.4.2 Feature

This release adds 2 notable features for engineering teams evaluating rollout.

Published 9mo Developer Productivity
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Summary

AI summary

Improved lock granularity fixes hanging cu list commands and added experimental --single-tenant stdio mode.

Full changelog

container-use v0.4.2

This is a mostly a patch release, but a feature or 2 snuck in. Notably:

  1. Improved lock granularity around export -- fixes issues with cu list and other commands hanging while an agent is running a tool.
  2. Added container-use stdio --single-tenant, an experimental mode intended for use with claude code or other CLI based agents. This mode locks each MCP server process to a single environment, reducing the tokens needed for each toolcall and improving subtask performance and accuracy. To try this out, add the --single-tenant flag to your agent's MCP server configuration block.
  3. version --system shows versions of our dependencies
  4. Environment creation can now take a git ref, so you can prompt "starting from $branch_or_sha, do task" and expect the agent to no longer be concerned with what you've got in your local checkout

Download the pre-compiled binaries from the assets below.

Changelog

  • 53d2d5c8b3837e5e9335013b5070fa0bd39f84e1: Fix linter (#268) (@cwlbraa)
  • 301e9474f8fb91c7cd8a051f6cbf996ad52a42f1: add awesome claude code badge to readme, fixes #255 (#267) (@cwlbraa)
  • 2c98c9d57114ebf610b8d601b6ab7c35baa72014: avoid holding locks during Export (#274) (@cwlbraa)
  • 57d84dea0ef65fbc3e44571e30a23eb485f1ccb6: better manual test instructions (#269) (@cwlbraa)
  • 95ad536448a0176987f28fb346bdb289c071099a: feat: add system info to version --system (#266) (@grouville)
  • 3dafb4fb39a1ce55a73944506f28bfeb9e668f75: feature: allow agent to specify a git ref for environment creation -- this makes it easier to multitask across multiple branches (#273) (@cwlbraa)
  • 6c5dff050b092073edad1d371d9bed3757cd5814: fix agent linter instructions so linter output matches CI (#276) (@cwlbraa)
  • 4fdd1b55de879f28c91b223505a83267f0040f12: fix explanation parameter description (#264) (@cwlbraa)
  • 518146732278d6374f3aadb1cdfc1472e006cbb9: fix permissions tests when not running as root (#265) (@cwlbraa)
  • 9932cd49c1fe03abc42b6fd19638ec5c5cb66c03: single tenant mode: lock an mcp process to a single environment (#246) (@cwlbraa)

Full Changelog: https://github.com/dagger/container-use/compare/v0.4.1...v0.4.2

View diff on GitHub

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Share on X Share on Bluesky

Track dagger/container-use

Get notified when new releases ship.

Sign up free

About dagger/container-use

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/model/infra stack.

All releases →

Related context

Beta — feedback welcome: [email protected]