Public release is in preparation
Private maintainer builds are not a public release, and an internal build number is not a support promise. This page intentionally has no placeholder download button.
When a release is approved, its entry must identify the version, supported platforms, immutable artifact URL, SHA-256, signing/notarization evidence and matching release notes. Until then, use only a trusted maintainer-supplied build or an authorized checkout.
Requirements and platform limits
| Platform | Current evidence |
|---|---|
| macOS desktop | macOS 14+ target. Source builds require the repository's selected Xcode toolchain. A target version is not certification on every supported physical machine. |
| Apple silicon / Intel | Distributed binaries must pass architecture and signing gates. Do not infer a public universal artifact from a private development build. |
| Linux / Unix CLI | Linux amd64 cross-build is verified; full runtime/test portability remains limited. No native desktop shell is released. |
| Windows / WSL | Windows Go source includes amd64 and arm64 cross-build checks. A separate Windows desktop client has qualified ARM64 product/fixture builds and supplied-API native-shell tests. Full runtime/test portability, installed-app, live-service and physical-x64 release qualification remain open; no approved public Windows installer is listed. WSL runtime certification remains open. |
The provider CLIs and accounts you select have their own installation, access and quota requirements. Optional on-device generation has additional OS/hardware requirements.
Install a trusted pre-release build
- Confirm its source, version and supplied integrity/signing evidence. Do not bypass Gatekeeper warnings for an unverified package.
- Place the supplied app in Applications. Keep any supplied CLI on PATH.
- Inspect
commandem version, the app's build identity and dependency evidence. Keep the app and CLI aligned before using newly documented features. - Follow first-project setup. Provider authentication remains separate.
Update and roll back safely
The app can detect a changed installed bundle and offer relaunch. That is not proof of download provenance. Finish active turns and choose a safe relaunch window. Do not replace the CLI underneath a frozen experiment. Keep a known-good supplied artifact and its identity before updating; do not reset repositories or erase history to roll back an application.
Uninstall without silently deleting evidence
Quit the app and move its application bundle to Trash. That does not remove local history, provider credentials or remote copies. Before removing local Commandem data, inventory and back up the state you need; use the data-removal checklist. Never delete an entire home directory or blindly run a recursive cleanup command.
Release notes and launch prerequisites
Read release-note policy and pre-release changes. A public release also requires a tested private vulnerability-reporting route, validated artifacts, an approved public repository decision and verified website deployment. None is implied by this page existing.