daem v0.2.0
Before upgrading from v0.1.0
If you already use daem to manage an environment, follow the upgrade procedure before replacing the executable. Populated old state and ownership records are not migrated automatically, and old recovery journals are refused. Keep your old daem binary and back up your manifest and lockfile. Do not edit or delete state files to bypass an upgrade error.
Scripts that consume JSON output need to account for changed schema_version values and output fields. See the CLI reference.
What's new
- A standalone installer. Install an exact release, upgrade, or restore the previous executable with
install.sh. It checks the download and binary identity before replacement. Rollback restores the executable only—not your manifest, lockfile, or managed state. - MCP support for Pi. Manage project and global MCP configuration through an explicit
pi-mcp-adapterprovider. - MCP environment references. Refer to environment variables without storing their values in the lockfile. Available mappings depend on the target host.
- Extension import and ordering. Import supported extensions from existing host configuration. Preview and apply Pi package precedence and OpenCode configuration-order changes.
- Clearer command feedback. Import shows progress and explains skipped resources. Repeating an already-satisfied
addreportsunchanged; common input errors include corrective guidance.
This release also fixes premature Git timeouts during slow local processing and includes Go runtime security fixes.
Install
Available for macOS 26 or newer on Apple silicon and Linux x86-64. Download the matching archive below or follow the installation guide.