Update#
godmode updateThe main menu has the same Update action. godmodeup remains available.
Updates follow the release manifest on godmode.build. A Git tag or draft release does not change it. There are no background downloads.
The updater verifies the archive checksum, replaces only managed files, and saves ~/.godmode/bin/godmode.previous. If your installed version is already current, no release archive is downloaded.
Check the result with godmode --version and godmode doctor. See release notes and membership updates.
| Option | Use |
|---|---|
--version vX.Y.Z | Select an available release; replace vX.Y.Z with its version |
--setup | Open setup after installation |
--force | Adopt an unmanaged executable, only after reviewing it |
The free CLI updates independently of your member pack. Download pack updates from your account.
Commands you run afterward use the updated executable. Ask an active agent to reread instructions or start a fresh session.
Install a downloaded archive#
For offline installation on an Apple Silicon Mac, obtain the installer, archive, and checksum from Install, then run:
sh godmode-install.sh \
--archive godmode-v0.19.2-aarch64-apple-darwin.tar.gz \
--checksum SHA256SUMS --install-onlyUse the destination's archive suffix: aarch64-apple-darwin, x86_64-apple-darwin, aarch64-unknown-linux-musl, or x86_64-unknown-linux-musl. Local archive installation downloads nothing. Ordinary local use needs no activation.
Check the local setup#
Doctor checks local file permissions, readable sealed values, business facts, agent instructions and the installed updater. It does not contact providers or claim a stored key still has access.
godmode doctor
godmode --env acme-test --context acme doctor --jsonErrors return exit code 1; optional setup gaps are warnings. Doctor changes no files.
Recover a failed update#
Keep the error and check the installation before retrying:
godmode --version
command -v godmode
godmode pathFor an archive/checksum mismatch, obtain a matching pair. Never skip verification.
The previous executable does not restore the updater or install receipt. Roll back with a verified release archive and the managed installer, checking data compatibility. See Get help.
Migrate an older plaintext store#
Godmode 0.9 and earlier could store plaintext keys under ~/.config/godmode. Check godmode path and change direct file readers to use godmode run, then seal the keys:
godmode migrateMigration checks that values read back identically and refuses ambiguous, duplicate, or malformed entries without printing values. Existing keys remain; shared names must match. Keep a private recovery copy until your tools work.
Remove programs and keep data#
For a default install, remove only the programs and PATH setup:
rm -f ~/.godmode/bin/godmode ~/.godmode/bin/godmodeup \
~/.godmode/bin/godmode.previous ~/.godmode/bin/.godmode-install-receipt \
~/.godmode/envRemove the # Godmode line and following source line from startup files changed by --path. Retain the matching seal key and a compatible executable or archive to use saved credentials later. Deleting the whole home deletes keys and profile; it never revokes provider credentials.