DevCapsule 0.2.14
Released 2026-09-25. Download and checksums. The first release intended for adopters outside the project.
- Configuration recovery after an upgrade works again. Upgrading to 0.2.12 had broken the recovery of an existing checkout's configuration; 0.2.14 fixes it and enforces the configuration contract from artifact admission through launch.
- Vendor downloads ask once per checkout. Earlier clients installed
vendor downloads other than Claude Code without recording your consent.
0.2.14 asks once for every vendor download. On such a checkout,
project config showlists the decision with its reason; answer withdevcapsule project --path <checkout> config authorize antigravity-download true, orfalseafter removing the agent from the project's need, thendevcapsule project --path <checkout> config resolve. This is the one-time exception the upgrade-compatibility requirement provides for. - Commands.
project config listis now a data listing with aSOURCEcolumn naming the document each row comes from. The newproject config showadds the files behind the resolution and the review: pending decisions with remedies, and whether resolving is needed.project run --print-commandprints the Docker command instead of launching. - The in-capsule command is
devcapsule; repositories that develop DevCapsule itself may name itdevcapsule0instead. - The legacy
pycharm runis retired; useproject run. - The workflow ships as a component: releases, the reserved
maintenanceworkstream, bug frontmatter,ws-branches, the workflow declaration, the local workflow file, mail and published state on a coordination branch, and the session-start synchronization judgment.
Deferred, tracked in the release bug table: configuration discovery from a directory outside the project inside a capsule, reuse of installed IDE and component layers across formations, manual ecosystem setup for fresh clones, the JetBrains X11 compositing and native-launcher warnings, cleanup of exited recursive containers, and a flaky claim-lifecycle test.