Collect diagnostics#
These commands identify the installed version and selected home:
godmode --version
python3 --version
command -v godmode
godmode path
godmode build-infoReview the output before sharing; paths can identify your setup. Include your OS, terminal or agent client, and whether the command works in your own terminal.
Use synthetic values to demonstrate credential-entry problems. Never share purchase keys, provider credentials, OAuth grants, private receipts, or unredacted recordings. Avoid diagnostics that print the environment.
Command not found#
Your shell may not know where Godmode is installed.
For a default installation:
. ~/.godmode/env
~/.godmode/bin/godmode helpIf the full path works, fix that shell's PATH. Your agent may use a different shell or host. See Remote machines for custom homes and remote runtimes.
Member sign-in#
Use the email you entered at checkout. Request a new sign-in link if the old one expired. The CLI does not require a license key or membership.
Provider errors#
For provider access, confirm the account, resource, permissions, and API status before replacing a key. Use the provider's official recovery flow. See Credentials.
File errors#
Read the named path and error. Do not bypass file checks with broad permission changes or blind replacement. Keep matched backups before repairs; a lost seal.key cannot be recovered from ciphertext. See Security.
Agent-note errors#
For an agent-note conflict, rerun godmode agents and inspect the new preview. Use godmode --plain agents in a small terminal.
Report a vulnerability#
Email godmode@lofilabs.xyz privately. Include the affected version and a reproducible example with fake credentials.