Protect local files#
Godmode encrypts each value and authenticates it together with its saved name. Anyone who has the credential file and its matching seal.key has access to its values. Keep both files private.
File under ~/.godmode | Contents |
|---|---|
.env.godmode and .env.godmode.NAME | Key names and encrypted values |
seal.key | Shared seal key for the home |
profile.json | Default business details in plain JSON |
active.json | Names of the saved environment and business |
Credential and profile files must be regular files you own with mode 0600. Store them in a private directory. Godmode rejects symlinks at the home and private files, and checks for concurrent edits before atomic replacement. Keep private files ignored and untracked in Git. See Businesses and environments for named profiles.
Choose what receives keys#
godmode list shows key names. godmode run NAME -- command supplies the selected value to a child process alongside its ordinary inherited environment. Missing or unreadable keys stop the command. Avoid logs that dump the environment and shell tracing around secrets.
Pin both selectors for long-running work, and use a read-only provider request to confirm the account and permissions. Choose an active setup.
Network access#
| Action | Connection |
|---|---|
| Local key and profile commands | Work offline without a license check |
| Install and update | Download release files unless using a local archive or build |
| Provider setup link | Opens the provider page in your browser |
godmode run | The child tool controls its own network use |
| Legacy license activation and deactivation | Contact godmode.build when explicitly requested |
Member sign-in is a separate website flow. See Privacy for website data handling.
Inspect a release#
godmode source | less
godmode build-infosource prints the embedded Python engine. build-info reports the compiler, dependencies and engine SHA-256. Install links to the matching source and native archives.
From the reviewed source, put the exact Go toolchain in go.mod on PATH. Check it with GOTOOLCHAIN=local go version. Rebuild for the installed binary’s OS and architecture.
GOPROXY=off GOSUMDB=off sh scripts/build-native.sh
cmp target/godmode-native "$(command -v godmode)"The installer verifies the release archive against SHA256SUMS. An independent rebuild gives you a separate comparison if the archive and checksum share a publisher.
Back up or recover#
Back up each key file with its matching seal.key and a compatible executable. Keep business details and context settings if you need them. If the seal key is lost, replace the credentials through their providers.
If a credential leaks, revoke or rotate it at the provider and update each consumer. Use synthetic credentials in support requests.