Skip to content

dagger/container-use

v0.0.2 Maintenance

This release keeps dependencies and maintenance posture current for teams operating this tool.

Published 11mo 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

Minor fixes and improvements.

Full changelog

container-use v0.0.2

Download the pre-compiled binaries from the assets below.

Changelog

  • bb6942055b1b0b5a0cecc7a8e0b82dd8bf7a75f1: Adds README instructions for Cursor (#75) (@samalba)
  • 470d7397c4c7496d9780d951dc7c3eed28820c13: document configuring container-use with cline (#72) (@kpenfound)
  • 279639ade9a6f8fc376e2060659f68c04acb632e: environment config (#73) (@aluzzardi)
  • 9df5e5d0b5c8c9481233070614f1b139b21a3314: environment: basic services support (#71) (@aluzzardi)

Full Changelog: https://github.com/dagger/container-use/compare/v0.0.1...v0.0.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]