This release adds 3 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Summary
AI summaryAdded environment customization with secrets support and new container-use apply command.
Full changelog
container-use v0.3.0
This release focuses on environment customization.
- container-use config provides a way to customize agent environments: changing the base image, setup commands, env vars, etc
- Secrets Management: Environments can now reference secrets. Supported backends are Environment Variables, Files, Vault and 1Password.
- Agents can customize their own environment (for example to install missing tools). Those customizations are ephemeral and can be reviewed (by using
container-use config view) and saved permanently (by usingcontainer-use config import)
Other changes:
container-use applyis now an alternative tocontainer-use merge. It will apply locally changes from an environment without committing.- Experimental
container-use config agentwizard to automate agent configuration (set up MCP server, install rules, etc)
Changelog
- 7e0de4ae58dcad267551ccd76a62d01da6f3cb4c:
cu config agent(#137) (@kpenfound) - 7e267e4b459311563a9abd335a27a7edeba94a03: brew: cleanup cu on uninstall (#205) (@cwlbraa)
- 9f8aed43de60371ed69c203eb0697ee6d57efd19: cli: use charmbracelet/fang (#185) (@aluzzardi)
- 0fe4df39685e16e726fe469fb93ed538cc0b5705: cu apply (#177) (@aluzzardi)
- b4a376abcc9e0d5ea2554b1faa90d62ac267ee0d: cu config: user-defined environment configuration (#202) (@aluzzardi)
- c59918bc9e2e65bd7773e102e08430d2beb2e4e7: ephemeral config changes (#203) (@aluzzardi)
- 6f2521091291e7e08692073ba1fa49d85d4d49f1: upgrade dagger to 18.12 (#215) (@cwlbraa)
Full Changelog: https://github.com/dagger/container-use/compare/v0.2.0...v0.3.0
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
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.
Related context
Related tools
Beta — feedback welcome: [email protected]