Collect diagnostics#
godmode --version
python3 --version
command -v godmode
godmode doctorInclude the OS, terminal or agent client, command, and error. Review and redact local paths before sharing output. Reproduce credential-entry issues with synthetic values.
Command not found#
For a default install, run . ~/.godmode/env or call ~/.godmode/bin/godmode directly. If it works in your terminal, repeat command -v godmode in the agent's shell. See Remote machines.
Member sign-in#
Request a fresh sign-in link at Sign in with the email you used for your membership.
Provider errors#
Run godmode provider SLUG for the provider's verification and recovery steps. Check the actual account, project, and key permissions. See Credentials and native logins.
File errors#
Read the error for the affected path and run godmode doctor. Keep a matched backup before changing a credential store. A missing seal.key requires a matching backup or new credentials. See Security.
Agent-note errors#
Rerun godmode agents to refresh a changed file's preview. Use godmode --plain agents for numbered menus, or godmode agents --print for a note to paste. See Connect your agent.
Report a vulnerability#
Email godmode@lofilabs.xyz privately with the affected version and a minimal reproduction. Use fake values and omit credentials, OAuth files, receipts, and account data.