# Godmode documentation — v0.20.0 Reviewed 2026-11-19. Use these guides with the user's task and project instructions. Check godmode --version. For a task tied to an account, use the scoped task note or inspect the selection with godmode active --command. Run help with that prefix, and pass selected names through godmode run. Keep credentials out of chat and leave .env.godmode and seal.key private. > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/ # Start here Godmode gives your coding agent local business details and passes selected provider keys to the commands that need them. ## First use 1. [Install Godmode](/install) on the machine where your agent runs. 2. [Connect one account and your agent](/docs/quickstart), then verify access with a read-only check. 3. [Build an app](/docs/launch) or [change an existing one](/docs/changes). Run `godmode --version` to check your installation. These guides cover v0.20.0. See the [release notes](/changelog) or read the [v0.19.2 docs](/docs/v0.19.2) for the previous interface. ## Give a guide to your agent Choose **Copy for agent** on a guide, then paste it with your task. In the agent's terminal, run `godmode help` for the selected setup and its saved key names. For direct access, use [the agent index](/llms.txt), [Quickstart Markdown](/docs/quickstart.md), or [the full reference in plain text](/llms-full.txt). ## Find an answer | If you want to… | Read | | --- | --- | | Save a key or keep a working provider login | [Credentials and native logins](/docs/credentials) | | Pick a service and verify its access | [Provider catalog](/docs/providers) | | Separate businesses or sandbox keys | [Businesses and environments](/docs/contexts) | | Look up a command | [Command reference](/docs/commands) | | Set up a second host | [Remote machines](/docs/remote) | | Fix a local setup | [Get help](/docs/support) | --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/quickstart # Quickstart Connect one provider account to your coding agent and run a read-only check. ## Install Use bash or zsh on macOS or Linux (ARM64 or x86-64), with Python 3.9 or later. ```sh curl -fsSL https://get.godmode.build | bash ``` Open a new terminal or run `. ~/.godmode/env` in your current shell. Check with `godmode --version`. See [Installation](/install) for downloads and existing installs. ## Add what your task needs ```sh godmode ``` Open **Provider keys** and choose the account your task needs. Follow the provider's steps, paste the key at the masked prompt, then review and save it. For GitHub, you can jump straight to `godmode setup github`. If the provider's CLI already has the right login, use it directly. Add **Business details** only if the task needs them. [Credentials and native logins](/docs/credentials) covers both access paths. ## Connect your agent ```sh godmode agents ``` - **Copy for this task** gives you a note to paste into an open agent session. You can also print it with `godmode agents --print`. - **Add to agent files** lets you select detected agent files and review the additions before saving. Start a fresh agent session in your project so it can load the saved note. See [Connect your agent](/docs/agents) to check the setup from inside the agent. ## Verify one account Give your agent this task with the bracketed details filled in. ```text Run godmode help, then read godmode provider [provider]. Use my existing login or only the saved keys this check needs. Check that you can read [project] in [account]. Report the account and project you verified. Keep credentials private. ``` A saved key only confirms local storage. A successful read confirms access to the resource you checked. [Build an app](/docs/launch) or [change an existing one](/docs/changes) once you have the right account. ## Choose the active setup Open **Switch setup** to choose a key environment and business profile for future commands. Run `godmode active` to check your selection. [Pin both selections](/docs/contexts#give-an-agent-the-selection) for a task that needs a specific account. ## Display options On first use, Enter advances the intro. Use `godmode --no-motion` for a still intro or `godmode --plain` for numbered menus. Use **Settings → Motion** to save the motion preference. --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/agents # Connect your agent Give your existing agent a short note that tells it how to find business details and use provider keys. For a single task, copy a note with that task's setup. For future sessions, append a generic note to your agent's instruction files. ## Review and add the note Run `godmode agents`, or select **Connect agent** in the main menu. 1. Choose **Add to agent files** and select one agent or **All detected agents**. 2. Scroll through the full preview. Check the destinations and added lines. 3. Press Enter to append the note. Start a fresh agent session so it can load the file. Godmode detects Claude Code, Codex, Gemini CLI, Copilot CLI, and OpenCode from existing folders. It preserves existing text and skips files that already mention `godmode help` or contain a Godmode marker, including edited notes. If a file changes during review, reopen the preview. Godmode shows the resolved destination for links and refuses unsafe files. If the preview is hard to review in your terminal, try `godmode --plain agents` for numbered choices and a text preview. ## Check that it works In the fresh session, ask the agent to run `godmode help`. It should describe the selected setup and list saved key names. For a task that uses a provider, have the agent confirm access to the expected account and resource with a read. ## Use another agent or one project Choose **Copy for this task**, then press Enter to copy the note. Paste it into the current conversation. You can also print it directly: ```sh godmode agents --print ``` For project-wide instructions, add the text to the file your agent already reads in that project. When sharing it across tasks, review the pinned setup in the note. ## Pin a task to one setup A task note includes the selected key environment, business profile, and custom home if you use one. With the global note, capture the command prefix once at the start of each task: ```sh godmode active --command ``` Use that prefix for every Godmode call in the task. See [Businesses and environments](/docs/contexts#give-an-agent-the-selection). ## Fix a missing command or wrong home For a default install, run `~/.godmode/bin/godmode` if the agent's PATH omits it. For a custom home, pass `--home DIR` or set `GODMODE_HOME` as well. For an agent running on another host, see [Remote machines](/docs/remote). ## Remove the note Delete the block from `` through `` in each file you changed. Start a fresh agent session. --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/profile # Business profile Save optional business details so your agent can use your real name, address, and contact information when a task needs them. ## Add your details Run `godmode profile`, or choose **Business details** and then **Edit business details** in the main menu. ```sh godmode active godmode profile ``` This edits the selected profile. Use **Switch setup** to choose a different business. **Automatic** uses the selected key environment's own profile. See [Businesses and environments](/docs/contexts). Select any field to edit it. In the form, submit an empty field to keep its current value, use `/clear` to remove it, or press Esc to cancel. | Field | What to enter | | --- | --- | | `operator_name` | Your name for signatures | | `business_name` | The name customers see | | `legal_name` | The registered business name, or your own name if appropriate | | `website` | Your main business website | | `public_email` | Your public contact address | | `business_mailing_address` | Postal address for invoices, legal pages, or email footers | Keep credentials, tax IDs, and banking details out of the profile. Prefer the project's own branding and contact details when available. Review any values the agent plans to publish. ## Read or change one field ```sh godmode profile get business_name godmode profile set \ business_mailing_address --stdin \ < business-address.txt godmode profile unset website ``` `get` writes one value to standard output. An unset field produces an error on standard error and exits with status 1. `set FIELD` opens a visible prompt. To script an update, send plain text with `--stdin`. The mailing address supports multiple lines. ## Keep the file private Run `godmode profile path` to locate the selected JSON file. The default is `~/.godmode/profile.json`. `godmode profile show` prints the entire profile, so use `get` when you need only one field. Keep profile files out of version control and treat their values as data. --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/contexts # Businesses and environments A **key environment** is a complete set of provider keys. A **business context** is a reusable profile. Select one of each to give a task the right credentials and business details. ## Select the active setup Open **Switch setup** in `godmode`. Choose a **Key environment** and **Business profile**, then select **Use this setup**. In the terminal: ```sh godmode use --env acme-test \ --context acme godmode active ``` The named selections must already exist. The pair is saved in `active.json` for future commands. **Recent setups** shows up to five prior pairs when history exists. Choose a pair and confirm it before switching. **Automatic** uses the selected environment's own profile. To return to the original setup, run `godmode use --env default --context -`. ## Copy a key file Copy an existing environment to create an independent snapshot of all its keys: ```sh godmode env create acme-copy \ --copy default ``` For a new client or account, start empty and add only its keys: ```sh godmode env create acme-test godmode --env acme-test \ --context - setup stripe ``` Future edits and rotations affect only the file you edit. Each environment uses its own keys. ## Reuse one business profile If the same business uses both test and live keys, create its profile once: ```sh godmode context create acme godmode --context acme profile ``` Use `--context acme` with either key environment to select the same business facts. For a profile that belongs exclusively to one environment, edit it with `--env NAME --context -`. ## Give an agent the selection Print a task note with both selections pinned: ```sh godmode --env acme-test \ --context acme agents --print ``` Paste it into the task. For shell commands, `godmode active --command` prints the prefix for the current pair. `godmode run` also passes the selected pair to nested Godmode commands. For each selection, command flags take precedence over shell variables (`GODMODE_ENV` and `GODMODE_CONTEXT`), then the saved pair. Pass both flags to pin the entire pair. `godmode use` with only one flag saves the other axis as currently resolved. An agent already running may hold its own scope, so give it an updated task note to switch. ## Inspect the files | Command | What it shows | | --- | --- | | `godmode active --json` | The resolved setup, paths, and where each selection came from | | `godmode env list --json` | Available environments and local paths | | `godmode path` | The selected key file | | `godmode profile path` | The selected profile file | ## Reuse a saved key name A context alias maps a requested key to the name already in the selected environment: ```sh godmode context map acme \ STRIPE_TEST_SECRET_KEY \ ACME_STRIPE_KEY godmode --env acme-test \ --context acme run \ STRIPE_API_KEY=STRIPE_TEST_SECRET_KEY \ -- stripe balance retrieve ``` Here `ACME_STRIPE_KEY` must already exist in `acme-test`. A missing mapped key stops the command. Remove the alias with `godmode context unmap acme STRIPE_TEST_SECRET_KEY`. ## Repair a missing selection Run `godmode env list` and `godmode context list` to find valid choices, then save an existing pair with `godmode use`. If `active.json` is malformed, pass both selection flags to work around it for one command. Repair the file or move it aside before saving another default. --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/stripe # Stripe accounts and sandboxes Keep Stripe test and live keys in separate Godmode environments. Confirm the Stripe account and sandbox before building or changing a payment flow. ## Select the account and sandbox 1. In the Stripe Dashboard, open the intended account and sandbox. 2. Create an empty environment and save the sandbox's keys. 3. Use that environment for local development and agent tasks. ```sh godmode env create acme-test godmode --env acme-test \ --context - setup stripe godmode --env acme-test \ --context - agents --print ``` Stripe recommends a general sandbox for new integrations. Test keys start with `sk_test_` or `rk_test_`, and their prefix is shared across sandboxes. Identify the sandbox in the Dashboard when obtaining the key. [Stripe Sandboxes](https://docs.stripe.com/sandboxes) · [API keys](https://docs.stripe.com/keys) ## Check the target before changing it With the Stripe CLI installed, check that the saved test secret can read a sandbox balance: ```sh godmode --env acme-test \ --context - run \ STRIPE_API_KEY=STRIPE_TEST_SECRET_KEY \ -- stripe balance retrieve ``` A balance read checks access to that endpoint. Before writes, confirm the authenticated account ID and the mode of a known project resource through the API or SDK. Compare them with the account and resource IDs your project expects. Use a restricted key with only the permissions required. [Account API](https://docs.stripe.com/api/accounts/retrieve) · [Restricted keys](https://docs.stripe.com/keys/restricted-api-keys) If you use an organization key, requests targeting a specific account require `Stripe-Context`. All requests using the organization key require `Stripe-Version`. [Organization keys](https://docs.stripe.com/keys/organization-api-keys) ## Keep webhook secrets with their endpoints Store the signing secret in the receiving deployment's secret store. Test, live, and Stripe CLI forwarding each use their own signing secret. Verify signatures against the raw request body and check mode and project ownership before applying an event. Test with a signed event and check what the receiver did. [Stripe webhooks](https://docs.stripe.com/webhooks) ## Reuse facts and verified resources Share the same [business profile](/docs/contexts#reuse-one-business-profile) across test and live if they use the same legal and contact details. Keep account IDs, price IDs, and webhook destinations in the matching deployment configuration. When retrying an API write, reuse its idempotency key and check for existing resources before creating another. [Stripe idempotency](https://docs.stripe.com/api/idempotent_requests) --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/credentials # Credentials and native logins Use your provider's own login when it already works, or save a key in Godmode and pass it to a specific command. ## Keep a working login If the official provider tool is signed in to the right account, use that login. Environment variables can override the tool's saved credentials. Check which account and resource the tool can read before making changes. ## Save a key Open a masked prompt for one key, then confirm that its name is listed: ```sh godmode set GH_TOKEN godmode list ``` In the native prompt, review the masked edit before pressing Enter. In `--plain` mode, press Enter to review and again to save. Never paste keys into chat or give them as command arguments. Run `godmode active` to check the selected environment. Use an explicit `--env NAME` or [Switch setup](/docs/contexts) to choose a different one. For provider-specific steps, run `godmode provider github` and `godmode setup github`. ## Give a key to a command For an installed GitHub CLI, give it `GH_TOKEN` for one read: ```sh godmode run GH_TOKEN -- \ gh api user --jq .login ``` When a tool expects a different environment variable, use `VAR=NAME`: ```sh godmode run \ STRIPE_API_KEY=STRIPE_TEST_SECRET_KEY \ -- stripe balance retrieve ``` `VAR` is the variable the command receives. `NAME` is the saved key. A missing or unreadable key stops the command before it runs. The command inherits your existing shell environment as well, so use trusted programs and keep shell tracing and environment dumps off. ## Import JSON Import a private credential file under a name ending in `_JSON`: ```sh godmode set ACME_AUTH_JSON --stdin \ < /private/path/credential.json ``` Godmode requires a JSON object and stores it on one line. The source file stays in place. Keep it private and out of version control. Your program must parse the variable and pass the resulting object to its auth library, or use a supported private-file mechanism. `GOOGLE_APPLICATION_CREDENTIALS` expects a file path. Google's bundled entries accept service-account private key JSON. See the [Google provider guide](/docs/provider-google) and [Google's credential search order](https://docs.cloud.google.com/docs/authentication/application-default-credentials). ## Replace or refresh a credential Let the provider tool own and refresh its login. If it returns a replacement grant that you keep in Godmode, save it with `godmode set NAME --stdin`. Godmode only saves credentials when you explicitly write them. For a rejected key, check the account, permissions, API, and target first. If the key needs rotation, replace it under the same name and verify it with the provider. Update copies on other machines and deployments separately. --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/providers # Provider catalog Use the bundled guides to find the credentials, account permissions, and access checks for your provider. ## Choose a provider - [GitHub](/docs/provider-github): Keep your product's code, issues, and release workflows in one place. - [Cloudflare](/docs/provider-cloudflare): Put your product online with hosting, data storage, and domain settings. - [Vercel](/docs/provider-vercel): Deploy your web app and manage its domains and project settings. - [Supabase](/docs/provider-supabase): Manage the database and sign-in services behind your app. - [Stripe](/docs/provider-stripe): Add payments to your product and test the checkout before going live. - [PostHog](/docs/provider-posthog): Understand how people use your product and manage feature flags. - [Notion](/docs/provider-notion): Keep product plans, research, and operating notes in pages your agent can update. - [Gmail](/docs/provider-gmail): Read and send product-related email through a mailbox you choose. - [Google](/docs/provider-google): Research search terms and track how people find your site in Google Search. - [Higgsfield](/docs/provider-higgsfield): Create images and videos for your product and its marketing. - [Zernio](/docs/provider-zernio): Publish product updates through your connected social accounts. - [Prodigi](/docs/provider-prodigi): Order and ship printed products for your customers. ## Open setup For example, read the Cloudflare guide and open its key prompt: ```sh godmode provider cloudflare godmode setup cloudflare ``` Run `godmode provider` to list provider slugs. In the native menu, choose **Provider keys** and press `/` to search. For a credential outside the catalog, use `godmode set NAME`. ## Check access 1. Read the provider's access scope and choose the narrowest permissions that work for your task. 2. Confirm the intended account and project with a read. 3. Pass the required keys using `godmode run NAME... -- CMD` and verify the result with the provider. **Saved** tells you the key is stored locally. Authorization to make changes comes from the user. See [Credentials and native logins](/docs/credentials). ## Catalog source These guides use the provider catalog bundled with Godmode v0.20.0. Follow the linked provider documentation if account setup has changed. [Download the catalog JSON](/docs/providers.json) --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/launch # Build and launch an app Give your agent a visitor action, a deployment target, and a clear test to run. If the task needs provider access, paste a [scoped Godmode note](/docs/agents#pin-a-task-to-one-setup) into the conversation. ```text Build a booking-request site using my existing repository and hosting project. A visitor should submit a request and see a confirmation. Skip payments. Ask before taking on a new recurring charge. Deploy it, submit a test request, and record the live URL and rollback steps. ``` ## Check existing work and access Review the project's instructions, source, and deployment settings. If you need Godmode, use the scoped task note or capture the command prefix with `godmode active --command`. Run `help` with that prefix to see the available key names and profile fields. Use a working provider login or selected keys from Godmode. Verify the account and project with a read before making changes. See the [provider catalog](/docs/providers). ## Build the visitor flow Complete the main action, including its success and error states. Check that a visitor can finish it on a phone and with a keyboard. Put private runtime credentials in the deployment's secret store. ## Confirm spending and public actions Use the authority given in the task. Confirm domain purchases, recurring charges, live payments, or public messages before proceeding if the user has yet to authorize them. The account owner handles sign-in, MFA, and provider review. ## Deploy and test Deploy to the intended project, then open its live URL. For the booking site, submit a test request, check the confirmation, and verify that the request reached its destination. Keep test records separate from customer activity. ## Save the release details Record the live URL, source revision, deployment ID, observed result, and rollback steps in the project. See [Change an existing app](/docs/changes) for the next release. --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/changes # Change an existing app Name the behavior to change and the flow that must keep working. ```text Show the selected date on the booking confirmation. Keep the existing hosting and data model. Verify the confirmation on mobile and on the deployed site. ``` ## Check the current app Read the project instructions and current diff. Reproduce the behavior, find the code that controls it, and check the existing deployment target. If you need credentials, use the [task's pinned Godmode setup](/docs/agents#pin-a-task-to-one-setup). Read the provider guide, then verify the intended account and resource with a read. ## Make the change Reuse the current components and conventions. Keep unrelated edits intact. For a data change, check compatibility with the current app and verify recovery before any destructive migration. ## Test and deploy Test the changed behavior and an adjacent flow. Review the diff. If the task includes deployment, confirm the reviewed revision is live in the intended project, then repeat the user action there. ## Record the result Save the changed behavior, test results, revision, and live URL when applicable. If the new release fails, follow [Recover a failed deploy](/docs/recovery). --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/recovery # Recover a failed deploy Check whether the previous release still serves traffic. Identify what failed before choosing a rollback or a targeted fix. ## Find the failure Record the account, project, deployment ID, source revision, and affected URL. Reproduce the failing action and read its logs with secrets and personal data removed. | Signal | Check first | | --- | --- | | Build failed | Build logs and the last successful revision | | Published app returns errors | Runtime logs, bindings, and data compatibility | | URL serves the wrong build | Project, route, domain, and deployment target | | Provider returns an error | Account, resource, permissions, and provider status | If you need credentials, [pin the task's setup](/docs/agents#pin-a-task-to-one-setup) and read the provider guide before using its recovery tools. ## Restore service Fix a reversible configuration error at its source. For a rollback, choose a known working release and check what the provider restores. Database changes, queues, and external writes can outlast a code rollback. ## Check the recovery Open the affected URL, confirm the intended release, and repeat the failing action. Test the main related flow and record the cause, fix, and remaining impact. ## Fix account access Check which account the tool uses and whether the credential can access the intended resource. For an expired or revoked credential, follow the provider's rotation steps and update each affected host or deployment. See [Credentials and native logins](/docs/credentials#replace-or-refresh-a-credential). --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/licensing # CLI and membership Use Godmode's CLI free for personal and commercial work. It runs locally without an account or activation. Its readable source and redistribution terms are covered by the [CLI license](/license#cli). ## Product membership Godmode membership is $100 USD per year. It includes the versioned product playbook and its updates, the member Slack invite, and Godmode setup help. See [membership](/pricing) or [sign in to your account](/login) for access. ## Cancel renewal Open [your account](/account) and choose **Manage billing**. Cancel renewal in the billing portal. Keep using your membership through the paid term and any downloaded packs afterward. ## Earlier paid licenses Earlier paid grants keep their original rights. For receipt commands, run `godmode license --help`. Godmode v0.17 and later run ordinary CLI commands without a receipt. --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/membership # Product playbook and updates The product pack gives your coding agent local instructions for building, deploying, and maintaining an app. ## Pack contents - An `AGENTS.md` entry point to seven workflows, from product planning to operations and releases. - Five provider guides covering Cloudflare, Stripe, GitHub, Better Auth, and PostHog. - Two examples, two templates, and a changelog. ## Install the pack Use Python 3.9+ and Godmode CLI 0.17 or later. [Sign in](/login) with your membership email, then download the pack from your account. Use the filename shown there. ```sh python3 ~/Downloads/godmode-product-2026.11.1.pyz ``` Add `--preview` to list the planned files. The installer writes a versioned directory under `~/.godmode/packs/godmode-product/`. ## Give it to your agent In a fresh conversation, ask your agent to read the `AGENTS.md` path printed by the installer. Include the task you want it to complete. ## Update instructions Download and run the new pack installer from [your account](/account). It installs next to the previous version. Start a fresh agent session with the new `AGENTS.md` path. Use [godmodeup](/docs/updates) for CLI updates. ## Release emails [Subscribe to Godmode updates](https://mail.godmode.build/subscribe), or set the email preference for your verified address in [your account](/account). A paid membership is optional for release emails. Follow any confirmation prompt. Each update includes an unsubscribe link. ## Member community Active members can choose **Join Godmode Slack** in their account. After joining, use **Open Slack**. Use the setup-help link if the invite is unavailable. ## Membership ends Keep using downloaded packs for your own and client work. New pack downloads and member setup help require active membership. Verified `@lofilabs.xyz` accounts receive complimentary access. Use **Manage billing** if you also have a paid subscription to review or cancel. --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/remote # Remote machines Install Godmode where your agent runs. Add only the keys the remote workload needs, or transfer a complete environment to a host you trust. ## Prepare the destination Follow [Install](/install) on the remote host. Run these checks in your agent's shell or runtime. ```sh command -v godmode godmode --version godmode active ``` For the default installation, source `~/.godmode/env` or use `~/.godmode/bin/godmode`. For a custom home, set `GODMODE_HOME` or pass `--home` when calling the binary. ## Supply the required keys Use the provider's login flow or add keys on the remote host with `godmode setup PROVIDER`. See [Credentials](/docs/credentials) for imports and command examples. ### Copy a complete key file A key file and its matching `seal.key` give the destination access to every key in that file. Use a fresh remote home. Existing named environments may rely on the seal key already on the destination. Replace `devbox` with your SSH host. ```sh ssh devbox ' umask 077 remote_godmode="$HOME/.godmode-remote" mkdir "$remote_godmode" && curl -fsSL https://godmode.build/install.sh -o "$remote_godmode/install.sh" && sh "$remote_godmode/install.sh" --home "$remote_godmode" --install-only ' ``` Continue after this succeeds. If the directory exists, choose a new destination. On the source host, confirm the path with `godmode --env default --context - path`. [Migrate older plain-text keys](/docs/updates#migrate-an-older-plaintext-store) first. This example copies from the standard home. ```sh scp -p ~/.godmode/.env.godmode ~/.godmode/seal.key devbox:.godmode-remote/ && ssh devbox '~/.godmode-remote/bin/godmode --home ~/.godmode-remote --env default --context - list' ``` `scp -p` preserves mode 0600. The list confirms which names are saved. For a named environment, use the key path from `godmode env show NAME`, copy that file with its matching seal key and replace `--env default` with `--env NAME`. To bring the default business details too, copy `profile.json` separately with `scp -p`. A profile-only transfer needs just that file. See [Businesses and environments](/docs/contexts) for named profiles. ## Connect the agent Run `godmode agents` in the remote shell with the chosen home. Review the destination before saving the note, then start a fresh agent session. Use [scoped agent instructions](/docs/agents) or pin both selectors in a scheduled task. Use a read-only provider request to check the remote tool's account. Copies are snapshots. Save rotations on each machine and revoke keys at the provider when a host should lose access. --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/updates # Updates and removal Update the CLI through its managed installer. Your key files, profiles, and agent notes stay on disk. ## Update ```sh godmodeup godmode --version ``` Use `godmode update` or **Settings → Update Godmode** to invoke the same updater. It reads the release manifest on `godmode.build`, checks the archive's SHA-256, and keeps the previous executable as `godmode.previous`. A current installation needs no new archive. To select a published release, use `godmodeup --version v0.20.0`. See [release notes](/changelog) for what's changed. Update the [member pack](/docs/membership#update-instructions) separately. ## Install a downloaded archive Download the [v0.20.0 installer](/releases/v0.20.0/install.sh), [checksums](/releases/v0.20.0/SHA256SUMS), and the archive for your platform from [Release files](/install#release-files). For Apple Silicon: ```sh sh install.sh --archive godmode-v0.20.0-aarch64-apple-darwin.tar.gz \ --checksum SHA256SUMS --install-only ``` Use the corresponding archive for Intel macOS or Linux. This installation can run offline. Add `--path` if you want the installer to update a supported shell's startup files. ## Check the local setup ```sh godmode doctor godmode doctor --json ``` Doctor checks the installation, selected files, and detected agent notes. Failed checks return exit status 1. Use a provider's read-only check to verify account access. ## Recover a failed update Run `command -v godmode` and `godmode --version` to identify the executable on PATH. To repair or roll back a managed install with downloaded files, run `godmodeup --archive PATH --checksum SHA256SUMS` with a verified archive and its matching checksum. `godmode.previous` holds the former executable only, so copying it over the installed file can leave the updater's receipt out of sync. See [Get help](/docs/support). ## Migrate an older plaintext store Check `godmode path` first. Switch any direct file readers to `godmode run`, then run `godmode migrate` to seal an older plaintext store. Keep a private recovery copy until the new workflow works. Migration stops on malformed or ambiguous entries. ## Remove programs and keep data For a default install, remove the program files and shell helper: ```sh rm -f ~/.godmode/bin/godmode ~/.godmode/bin/godmodeup \ ~/.godmode/bin/godmode.previous ~/.godmode/bin/.godmode-install-receipt \ ~/.godmode/env ``` Remove the matching `# Godmode` block from any startup file changed by `--path`. Keep the rest of the Godmode home to retain credentials and business details. Revoke credentials through their provider if you want to remove account access. --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/commands # Command reference These commands cover Godmode v0.20.0. Run `godmode --help` for the installed command list or `godmode help COMMAND` for most commands. In the examples below, replace uppercase placeholders with your own names or command. ## Open and inspect | Command | Result | | --- | --- | | `godmode` | Open the terminal interface. | | `godmode --version` | Print the installed version. | | `godmode help` | Print the agent guide for the selected setup, including saved key names. | | `godmode faq` | Read local setup and troubleshooting help. | | `godmode intro` | Replay the welcome. | | `godmode doctor`, `godmode doctor --json` | Check the local install, selected files and detected agent notes. Failed checks return exit status 1. | | `godmode source` | Print the embedded Python file engine. | | `godmode build-info` | Print compiler, dependencies and engine hash. | ## Credentials and providers | Command | Result | | --- | --- | | `godmode setup`, `godmode setup PROVIDER` | Choose a provider or open its setup screen directly. | | `godmode provider`, `godmode provider PROVIDER` | List providers or show setup, verification and recovery steps for one. | | `godmode list` | Print saved key names, one per line. An invalid store can return a nonzero status. | | `godmode set NAME`, `godmode set NAME --stdin` | Save a value through a masked prompt or read it from stdin. | | `godmode run NAME... -- CMD` | Add only the requested saved keys to the command's inherited environment. | | `godmode run VAR=NAME -- CMD` | Supply a saved key under the variable the command expects. | | `godmode path` | Print the selected credential file's path. | | `godmode edit` | Open the file in nano. Sealed entries stay encrypted. | | `godmode migrate` | Seal keys from an older plaintext store. | Keep credentials out of command arguments and chat. For an account check, run a provider's read-only command with the minimum key set. See [Providers](/docs/providers). ## Profile and agent instructions | Command | Result | | --- | --- | | `godmode profile` | Edit the optional business fields. | | `godmode profile show`, `godmode profile path` | Print the selected profile as JSON or print its file path. | | `godmode profile get FIELD` | Print one field. An unset field returns exit status 1. | | `godmode profile set FIELD`, `godmode profile set FIELD --stdin` | Set a field through a visible prompt or from stdin. | | `godmode profile unset FIELD` | Remove a field. | | `godmode agents` | Copy the selected task note or review additions to detected agent files. | | `godmode agents --print` | Print the note scoped to the selected setup. | See [Business profile](/docs/profile) for field names and [Connect your agent](/docs/agents) for the review and verification steps. ## Home and display settings In the terminal UI, use the arrow keys to move, Enter to open, and Esc to go back. Press Ctrl-K to find an action or `?` for keyboard help. | Option or command | Result | | --- | --- | | `--home DIR` | Select a Godmode home. The default is `~/.godmode`. | | `--plain` | Use static text and numbered menus for this invocation. | | `--no-motion` | Disable animations for this invocation. | | `godmode settings` | Open Settings in a terminal or report the motion preference in plain mode. | | `godmode settings --json` | Read the stored motion preference and its path. | | `godmode settings motion on`, `godmode settings motion off` | Save the motion preference. | `GODMODE_HOME` also selects a home. The older `GODMODE_CONFIG_DIR` alias still works. Use `GODMODE_PLAIN=1`, `GODMODE_NO_MOTION=1` or `NO_COLOR=1` for shell-wide display overrides. ## Businesses and environments | Command | Result | | --- | --- | | `godmode active`, `godmode active --json` | Inspect the resolved key environment and business profile. JSON includes paths and selection sources. | | `godmode active --command` | Print the full command prefix that pins the current setup. | | `godmode use --env NAME --context BUSINESS` | Save the active pair for future commands. Omit one flag to keep that part of the current selection. `godmode use NAME` is shorthand for `godmode use --env NAME`. | | `godmode env`, `godmode env list` | List key environment names. Add `--json` to `env list` for metadata. | | `godmode env create NAME`, `godmode env create NAME --copy SOURCE` | Create an empty store or an independent copy. | | `godmode env show NAME` | Show the environment's paths and saved names. | | `godmode context`, `godmode context list` | List business profile names. | | `godmode context show BUSINESS` | Show a profile path and its key mappings. | | `godmode context create BUSINESS` | Create a named business profile. | | `godmode context map BUSINESS VARIABLE SAVED_KEY` | Resolve a variable through another key name in the selected store. | | `godmode context unmap BUSINESS VARIABLE` | Remove a key mapping. | For one command, put `--env NAME` and `--context BUSINESS` before the command. `--env default` selects the default store. `--context -` selects **Automatic**, which uses that environment's own profile. Explicit flags take priority over shell variables, which take priority over the saved setup. See [Businesses and environments](/docs/contexts). ## Update the installation | Command | Result | | --- | --- | | `godmodeup`, `godmode update` | Update the recorded installation to the latest available release. | | `godmodeup --version vX.Y.Z`, `godmode update --version vX.Y.Z` | Install a specific published version. | See [Installation](/docs/updates) for recovery and [Licensing](/docs/licensing) for earlier paid releases. Run `godmode license --help` for receipt commands. --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/security # Security and network access Godmode saves keys on your machine. Any program running as your user can request them. Pass keys only to programs you trust. ## 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](/docs/contexts) 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](/docs/contexts). ## 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](/privacy) for website data handling. ## Inspect a release ```sh godmode source | less godmode build-info ``` `source` prints the embedded Python engine. `build-info` reports the compiler, dependencies and engine SHA-256. [Install](/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. ```sh 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](/docs/support). --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/support # Get help Email [godmode@lofilabs.xyz](mailto:godmode@lofilabs.xyz) for CLI bugs and setup questions. ## Collect diagnostics ```sh godmode --version python3 --version command -v godmode godmode doctor ``` Include 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](/docs/remote). ## Member sign-in Request a fresh sign-in link at [Sign in](/login) 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](/docs/credentials). ## 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](/docs/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](/docs/agents). ## Report a vulnerability Email [godmode@lofilabs.xyz](mailto:godmode@lofilabs.xyz) privately with the affected version and a minimal reproduction. Use fake values and omit credentials, OAuth files, receipts, and account data. --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/provider-github # GitHub Keep your product's code, issues, and release workflows in one place. ## Connect GitHub Keep a working [native login](/docs/credentials#keep-a-working-login), or save the keys below. ```sh godmode setup github ``` ## Account access A fine-grained personal access token acts as its owner within one selected user or organization. The setup requests broad repository write access, including administration, across all repositories for that owner. Organization approval, token lifetime policy and your own role still apply; other accounts or API operations can require different permissions or a GitHub App. ## Add credentials Save only the keys your product needs. ### Access token Give your agent access to your product's repositories and release work. **[Visit GitHub's token page](https://github.com/settings/personal-access-tokens/new?name=godmode&expires_in=366&administration=write&contents=write&workflows=write&actions=write&secrets=write&actions_variables=write&environments=write&issues=write&pull_requests=write)** 1. Choose the **Resource owner** and **All repositories**. 2. Select **Generate token** and copy it. Save as `GH_TOKEN` in Godmode. ## Check access - Use the official GitHub CLI or API to identify the token owner and read an intended repository. Check the endpoint's required permissions before creating repositories, configuring Actions, managing secrets or opening pull requests. A successful identity check alone does not prove repository write access. ## Restore access - For permission failures, check the resource owner, repository selection and organization approval first. For an expired or revoked token, create a replacement through GitHub and save it with godmode set GH_TOKEN. Verify the intended operation before retiring a still-valid old token. ## Provider docs - [Personal access tokens and permissions](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens) - [GitHub CLI authentication environment](https://cli.github.com/manual/gh_help_environment) Source: Godmode v0.20.0 provider catalog · 2026-11-13. --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/provider-cloudflare # Cloudflare Put your product online with hosting, data storage, and domain settings. ## Connect Cloudflare Keep a working [native login](/docs/credentials#keep-a-working-login), or save the keys below. ```sh godmode setup cloudflare ``` ## Account access A user API token reaches the account and zone resources included in its policies. The setup deliberately starts broad and changes available Read permissions to Edit; inspect the summary for Workers, D1, R2, DNS and any other intended service. Resource selection, your account role and service availability still limit access. R2 S3 credentials are a separate credential type. ## Add credentials Save only the keys your product needs. ### API token Let your agent manage the Cloudflare accounts and zones your product uses. **[Visit Cloudflare's token page](https://dash.cloudflare.com/profile/api-tokens)** 1. Create a token from **Read All Resources**. 2. Change **Read** to **Edit** where available. 3. Review the summary, create the token and copy it. Save as `CLOUDFLARE_API_TOKEN` in Godmode. ## Check access - Check the user token with GET /client/v4/user/tokens/verify, then list the intended account or zone resources using Cloudflare's API or Wrangler. An active token does not prove every service permission. Select the exact account and zone before provisioning or deploying. ## Register a domain Registration creates a billable domain purchase. Confirm the price and your spending limit first. For domain registration, verify Registrar write permission for the intended account; changing Read to Edit does not establish Registrar access. The Registrar API beta registers supported available domains and requires a valid default payment method, a default registrant contact and acceptance of the Domain Registration Agreement. The user must set up billing in the dashboard. Check the domain's current availability and price and the user's purchase authorization before registering. ## Restore access - Fix missing permissions or resource policies without replacing a valid secret. For a lost, expired or revoked secret, use the dashboard to create a replacement or roll the token, then godmode set CLOUDFLARE_API_TOKEN. Rolling invalidates the old value; creating a separate token allows a staged replacement. ## Provider docs - [Create API tokens](https://developers.cloudflare.com/fundamentals/api/get-started/create-token/) - [Roll tokens](https://developers.cloudflare.com/fundamentals/api/how-to/roll-token/) - [Wrangler commands](https://developers.cloudflare.com/workers/wrangler/commands/) - [Registrar API beta prerequisites and workflow](https://developers.cloudflare.com/registrar/registrar-api/) - [Registrar API support and billing requirements](https://developers.cloudflare.com/api/resources/registrar/) Source: Godmode v0.20.0 provider catalog · 2026-11-13. --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/provider-vercel # Vercel Deploy your web app and manage its domains and project settings. ## Connect Vercel Keep a working [native login](/docs/credentials#keep-a-working-login), or save the keys below. ```sh godmode setup vercel ``` ## Account access A Full Account token reaches your personal account and teams, subject to your role. Team and project scopes are alternatives when desired. Full-account requests need the intended team ID or slug when targeting team resources; a valid token can otherwise select a different default team. ## Add credentials Save only the keys your product needs. ### Access token Give your agent access to the team and projects that host your app. **[Visit Vercel's token page](https://vercel.com/account/settings/tokens)** 1. Make a token with **Full Account** scope. Choose an expiration date. Save as `VERCEL_TOKEN` in Godmode. ## Check access - Use Vercel's CLI or REST API to list projects or deployments in the intended team. Confirm the project before configuring its environment, deploying or changing domains. The CLI accepts VERCEL_TOKEN; direct API clients must read that variable and send Bearer authentication. ## Restore access - Read the error: missingToken means the credential was not supplied; invalidToken can mean wrong, expired or deleted. Fix team/project targeting for scope failures. Replace an invalid token from Account Tokens and save it with godmode set VERCEL_TOKEN. ## Provider docs - [Access token scope, use and recovery](https://vercel.com/docs/accounts/access-tokens) - [CLI token option](https://vercel.com/docs/cli/global-options#token) Source: Godmode v0.20.0 provider catalog · 2026-11-13. --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/provider-supabase # Supabase Manage the database and sign-in services behind your app. ## Connect Supabase Keep a working [native login](/docs/credentials#keep-a-working-login), or save the keys below. ```sh godmode setup supabase ``` ## Account access The legacy full-access personal token reaches all organizations and projects your account can access, including future ones. Scoped tokens are also available. This credential authenticates the Management API, CLI and compatible tools; it is not a database password, project publishable key or runtime secret key. ## Add credentials Save only the keys your product needs. ### Access token Manage your Supabase projects through the CLI and Management API. **[Visit Supabase's access tokens](https://supabase.com/dashboard/account/tokens)** 1. Select **Generate new token** > **Create legacy token**. 2. Type a name and set **Expires in** to **Never**. 3. Select **Generate token**, then copy the token. Save as `SUPABASE_ACCESS_TOKEN` in Godmode. ## Check access - List accessible organizations and projects through the Management API or official CLI, then confirm the intended project and account role. Use the relevant management permissions for project configuration, database work and deployments. Check the installed CLI help: hosted and local targeting can differ by version. ## Restore access - Check account role and token scope on permission errors. Replace an expired or revoked token in account settings and save it with godmode set SUPABASE_ACCESS_TOKEN. The CLI reads this environment variable before a saved login token; Godmode does not update the CLI cache. ## Provider docs - [Personal access tokens](https://supabase.com/docs/guides/platform/personal-access-tokens) - [Management API](https://supabase.com/docs/reference/api/introduction) - [CLI reference](https://supabase.com/docs/reference/cli/introduction) Source: Godmode v0.20.0 provider catalog · 2026-11-13. --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/provider-stripe # Stripe Add payments to your product and test the checkout before going live. ## Connect Stripe Keep a working [native login](/docs/credentials#keep-a-working-login), or save the keys below. ```sh godmode setup stripe ``` ## Account access Standard secret keys have broad API access in one account or sandbox. Test and live credentials are separate; publishable keys are for client applications and cannot perform secret-key operations. Restricted keys are an alternative. Webhook signing secrets are separate values. ## Add credentials Save only the keys your product needs. ### Test secret key Test payment operations in a sandbox before taking real payments. **[Visit Stripe’s test keys](https://dashboard.stripe.com/test/apikeys)** 1. Under **Standard keys**, reveal the **Secret key** (sk_test_…) and copy it. If there is no sk_test_ key, switch to a sandbox in the account picker. Save as `STRIPE_TEST_SECRET_KEY` in Godmode. ### Test publishable key Connect your browser checkout to Stripe's test environment. **[Visit Stripe’s test keys](https://dashboard.stripe.com/test/apikeys)** 1. Under **Standard keys**, copy the **Publishable key** (pk_test_…). Save as `STRIPE_TEST_PUBLISHABLE_KEY` in Godmode. ### Live secret key Run payment operations in your live Stripe account. **[Visit Stripe’s live keys](https://dashboard.stripe.com/apikeys)** 1. Select **Create secret key** and type the verification code. 2. Type a **Key name**, then select **Create**. 3. Select the key (sk_live_…) to copy it. Save as `STRIPE_LIVE_SECRET_KEY` in Godmode. ### Live publishable key Connect your browser checkout to Stripe's live environment. **[Visit Stripe’s live keys](https://dashboard.stripe.com/apikeys)** 1. Under **Standard keys**, copy the **Publishable key** (pk_live_…). If it starts with pk_test_, switch to live mode first. Save as `STRIPE_LIVE_PUBLISHABLE_KEY` in Godmode. ## Check access - Use the Stripe SDK or API to read the intended account and inspect a resource in the selected sandbox or live mode. Supply the selected secret key explicitly: these Godmode key names are not an automatic Stripe SDK configuration. Build and test payment flows in a sandbox before an authorized live operation. ## Restore access - For an invalid or expired key, use the account's API keys page to create or rotate it and overwrite the matching Godmode entry. Stripe offers an expiration grace period for the old key. Check mode, restrictions and account status before assuming every denied operation needs rotation. ## Provider docs - [API key types, environments and rotation](https://docs.stripe.com/keys) - [Stripe API](https://docs.stripe.com/api) Source: Godmode v0.20.0 provider catalog · 2026-11-13. --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/provider-posthog # PostHog Understand how people use your product and manage feature flags. ## Connect PostHog Keep a working [native login](/docs/credentials#keep-a-working-login), or save the keys below. ```sh godmode setup posthog ``` ## Account access A personal API key accesses private analytics, insights, flags and other APIs using your account permissions and the key's scopes. The MCP preset is convenient for broad agent use; confirm its organization/project selection. Use the matching US, EU or self-hosted instance. A project ingestion key is a different credential. ## Add credentials Save only the keys your product needs. ### Personal API key Let your agent query product analytics and manage PostHog resources. **[Visit PostHog's personal API keys](https://app.posthog.com/settings/user-api-keys?preset=mcp_server)** 1. Select **Create key**; the form is already filled in. 2. Copy the key (phx_…) from the dialog. Save as `POSTHOG_PERSONAL_API_KEY` in Godmode. ## Check access - Use PostHog's API to read the intended project and run a small query or list the intended resource. Check the endpoint's required scope before managing flags, dashboards or experiments. Keep the personal key server-side; it is not a browser analytics key. ## Restore access - Check the instance, project and scopes first. Create a replacement for an invalid key and save it with godmode set POSTHOG_PERSONAL_API_KEY. If rolling a legacy key, the old value is invalidated; update every consumer that used it. ## Provider docs - [Personal API keys](https://posthog.com/docs/api/personal-api-keys) - [API scopes](https://posthog.com/docs/api/scopes) - [API overview](https://posthog.com/docs/api) Source: Godmode v0.20.0 provider catalog · 2026-11-13. --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/provider-notion # Notion Keep product plans, research, and operating notes in pages your agent can update. ## Connect Notion Keep a working [native login](/docs/credentials#keep-a-working-login), or save the keys below. ```sh godmode setup notion ``` ## Account access The personal access token acts as its creator in one workspace, with the selected Notion API capability and that user's content permissions. The workspace can restrict who creates or uses PATs. An internal connection token is an alternative identity with capabilities and explicitly shared pages, independent of one user's membership. ## Add credentials Save only the keys your product needs. ### Access token Give your agent access to the workspace content used to run your product. **[Visit Notion's token page](https://app.notion.com/developers/tokens)** 1. Select **New token** and name it. 2. Choose the workspace, **Notion API**, and an expiration. 3. Select **Create token**, then copy the token. Save as `NOTION_API_KEY` in Godmode. ## Check access - Use the Notion SDK or API to retrieve the token identity and an intended page or data source. Confirm the workspace and content access before creating or updating pages, databases or comments. The SDK must read NOTION_API_KEY explicitly. ## Restore access - PATs expire within one year. Create a replacement through the Developer portal and save it with godmode set NOTION_API_KEY. An unauthorized response can also come from workspace PAT policy; missing content can reflect lost user access or a page not shared with an internal connection. Repair that access instead of repeatedly replacing tokens. ## Provider docs - [Personal access tokens](https://developers.notion.com/guides/connections-and-tokens/personal-access-tokens) - [Internal connections](https://developers.notion.com/guides/connections-and-tokens/internal-connections) Source: Godmode v0.20.0 provider catalog · 2026-11-13. --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/provider-gmail # Gmail Read and send product-related email through a mailbox you choose. ## Connect Gmail Keep a working [native login](/docs/credentials#keep-a-working-login), or save the keys below. ```sh godmode setup gmail ``` ## Account access The mailbox address and app password support IMAP/SMTP clients where Google Account policy allows them. App passwords require 2-Step Verification and can be unavailable for some organization accounts, security-key-only setups or Advanced Protection. They do not grant Gmail API, Google SSO or Workspace administration access. ## Add credentials Save only the keys your product needs. ### Mailbox address Choose the mailbox your agent will use. Save as `GMAIL_USER` in Godmode. ### App password Let a supported mail client sign in to that mailbox over IMAP or SMTP. **[Visit Google's app passwords](https://myaccount.google.com/apppasswords)** 1. Type a name under **App name**, then select **Create**. 2. Copy the 16-character password. This page works only with 2-Step Verification turned on. Save as `GMAIL_APP_PASSWORD` in Godmode. The password prompt removes spaces, including nonbreaking spaces. With `--stdin`, remove those spaces yourself. ## Check access - Configure the mail client with GMAIL_USER and GMAIL_APP_PASSWORD and establish an authenticated TLS IMAP or SMTP session without sending a message. Confirm the mailbox before reading mail or carrying out an authorized send. Use the Gmail API's separate OAuth flow if the task requires that API. ## Restore access - Google revokes app passwords after an account password change. Create a replacement and save it with godmode set GMAIL_APP_PASSWORD. If app passwords are unavailable, use a supported Google sign-in/OAuth client; repeating app-password setup cannot override account policy. ## Provider docs - [App passwords and recovery](https://support.google.com/accounts/answer/185833) - [Gmail IMAP and SMTP](https://developers.google.com/workspace/gmail/imap/imap-smtp) Source: Godmode v0.20.0 provider catalog · 2026-11-13. --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/provider-google # Google Research search terms and track how people find your site in Google Search. ## Connect Google Keep a working [native login](/docs/credentials#keep-a-working-login), or save the keys below. ```sh godmode setup google ``` ## Account access The bundled JSON entries are service-account private keys, not OAuth clients or user grants. For Ads, enable the API and obtain the required API access level in that Cloud project, then add the service-account email to the intended Ads account or manager. For Search Console, enable its API and grant the identity access to each property. Cloud IAM roles alone do not grant Ads or Search Console access. ## Add credentials Save only the keys your product needs. Drop the downloaded service-account JSON file into its prompt. Godmode reads and saves the JSON, leaving the source file in place. Your code must load the JSON with a supported library. See [credential JSON](/docs/credentials#import-json). ### Ads service account Give your agent an identity for Google Ads research and reporting. **[Visit Google's service accounts](https://console.cloud.google.com/projectselector/iam-admin/serviceaccounts)** 1. Pick your Ads project, then open or create a service account. 2. Select **Keys** > **Add key** > **Create new key** > **JSON** > **Create**. Then add its email in Google Ads under Admin > Access and security. Save as `GOOGLE_ADS_SERVICE_ACCOUNT_JSON` in Godmode. ### Search Console account Give your agent an identity for reading your site's Search Console data. **[Visit Google's service accounts](https://console.cloud.google.com/projectselector/iam-admin/serviceaccounts)** 1. Pick your Search Console project, then open or create a service account. 2. Select **Keys** > **Add key** > **Create new key** > **JSON** > **Create**. Then add its email to the property under Settings > Users and permissions. Save as `GOOGLE_SEARCH_CONSOLE_SERVICE_ACCOUNT_JSON` in Godmode. ## Check access - The consumer must parse the JSON variable and use an official Google auth/client library with the API's scopes; these variable names are Godmode conventions, not automatic Google SDK settings. Ads uses the adwords scope; Search Console uses webmasters or webmasters.readonly. - List directly accessible Ads customers, then check the intended client/manager path. For Search Console, list sites and confirm the exact property and permission level. Only then run reporting, keyword planning or authorized management operations. ## Restore access - Let the consuming Google library obtain and renew access tokens from the service-account key; ordinary access-token expiry needs no new key or browser consent. For a disabled, deleted or invalid private key, create a replacement on the same service account, save the matching Godmode entry, verify it, then retire the old key. - User OAuth is a separate supported consumer choice: store its refresh grant under a separate name such as GOOGLE_SEARCH_CONSOLE_OAUTH_JSON. Reauthorize only when refresh fails because the grant is revoked, expired or policy requires sign-in. Save any replacement grant with godmode set NAME; Godmode does not write back refreshed credentials. ## Provider docs - [Ads service accounts and account access](https://developers.google.com/google-ads/api/docs/oauth/service-accounts) - [List accessible Ads accounts](https://developers.google.com/google-ads/api/docs/account-management/listing-accounts) - [Search Console authorization](https://developers.google.com/webmaster-tools/v1/how-tos/authorizing) - [List Search Console sites](https://developers.google.com/webmaster-tools/v1/sites/list) - [OAuth refresh and grant expiry](https://developers.google.com/identity/protocols/oauth2) - [Service account key rotation](https://docs.cloud.google.com/iam/docs/key-rotation) Source: Godmode v0.20.0 provider catalog · 2026-11-13. --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/provider-higgsfield # Higgsfield Create images and videos for your product and its marketing. ## Connect Higgsfield Keep a working [native login](/docs/credentials#keep-a-working-login), or save the keys below. ```sh godmode setup higgsfield ``` ## Account access The key ID and secret are one credential pair for a personal or organization account. Both are needed for server-side authentication. The selected account owns generated work and charges; individual models and environments can have separate access requirements. ## Add credentials Save only the keys your product needs. ### API key ID Identify the API key for the Higgsfield account your agent will use. **[Visit Higgsfield's API keys](https://open.higgsfield.ai/api-keys)** 1. Create and name an **API key**. 2. Copy the key. Keep the dialog open. The copied key is ID:secret. This saves the ID; the next step, the secret. Save as `HIGGSFIELD_API_KEY_ID` in Godmode. ### API key secret Complete the credential pair so your agent can authenticate. If the key is lost, create one and replace both the ID and secret. Save as `HIGGSFIELD_API_KEY_SECRET` in Godmode. Paste the same `ID:secret` value into both prompts; Godmode splits it into the two saved names. With `--stdin`, pass each part separately. ## Check access - Use the selected model's official API documentation and the Higgsfield client or API. Supply both stored values explicitly; official examples may use HF_API_KEY_ID and HF_API_KEY_SECRET instead of these Godmode names. Read an existing request's status when available. Creating a generation can incur charges and is not a free authentication probe. ## Restore access - For invalid, expired or disabled credentials, use API keys in Higgsfield Console and replace both Godmode entries from the same new pair. Verify before deleting a still-valid old pair. A model availability error is not proof that the credential is invalid. ## Provider docs - [Authentication](https://docs.higgsfield.ai/docs/authentication) - [Key lifecycle and account controls](https://docs.higgsfield.ai/docs/enterprise/access-control) - [Model documentation index](https://docs.higgsfield.ai/docs/llms.txt) Source: Godmode v0.20.0 provider catalog · 2026-11-13. --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/provider-zernio # Zernio Publish product updates through your connected social accounts. ## Connect Zernio Keep a working [native login](/docs/credentials#keep-a-working-login), or save the keys below. ```sh godmode setup zernio ``` ## Account access The API key accesses Zernio profiles and resources within its permissions. This setup uses broad read/write access; narrower profile, resource and read-only scopes exist. Social accounts must also be connected with their own platform permissions. ## Add credentials Save only the keys your product needs. ### API key Give your agent access to the Zernio profiles used for your product. **[Visit Zernio's API keys](https://zernio.com/dashboard/api-keys)** 1. Open **API Keys**, then select **Create API key**. 2. Name the key, select **Create key**, then copy it. Save as `ZERNIO_API_KEY` in Godmode. ## Check access - Use Zernio's SDK or API to list profiles and connected accounts, then confirm the intended account ID and connection health. Check platform support before scheduling posts, reading analytics or managing an inbox. SDKs read ZERNIO_API_KEY. ## Restore access - Replace an expired or revoked Zernio API key through its API keys settings and save it with godmode set ZERNIO_API_KEY. If only a connected social account needs authorization again, use Zernio's official reconnect flow for that account; replacing the Zernio key will not repair the platform grant. ## Provider docs - [API setup and connected accounts](https://docs.zernio.com/quickstart) - [API keys and authentication errors](https://docs.zernio.com/api-keys/list-api-keys) - [Connection troubleshooting](https://docs.zernio.com/for-you/troubleshooting) Source: Godmode v0.20.0 provider catalog · 2026-11-13. --- > Godmode v0.20.0 documentation · Reviewed 2026-11-19 > Source: https://godmode.build/docs/provider-prodigi # Prodigi Order and ship printed products for your customers. ## Connect Prodigi Keep a working [native login](/docs/credentials#keep-a-working-login), or save the keys below. ```sh godmode setup prodigi ``` ## Account access Sandbox and live API keys belong to separate environments. Sandbox orders are not fulfilled or charged. Live orders are printed, shipped and billed. Select the endpoint that matches the key. ## Add credentials Save only the keys your product needs. ### Sandbox API key Test print orders without production, shipping, or charges. **[Visit Prodigi's API settings](https://sandbox-beta-dashboard.pwinty.com/settings/api)** 1. Under **API authentication**, select **Show key** and copy it. pwinty.com is Prodigi's sandbox; sign in with your Prodigi account. Save as `PRODIGI_SANDBOX_API_KEY` in Godmode. ### Live API key Place live orders that Prodigi prints, ships, and bills. **[Visit Prodigi's API settings](https://dashboard.prodigi.com/settings/api)** 1. Under **API authentication**, select **Show key** and copy it. Orders placed with this key are printed, shipped and billed. Save as `PRODIGI_API_KEY` in Godmode. ## Check access - Use the Print API's documented authentication header with the matching environment. Read existing orders or product details to check the intended access, or request a quote for the intended specification. Use sandbox orders for fulfillment integration tests; a sandbox result does not prove a live print was produced. ## Restore access - Check that the key matches the sandbox or live API first. Retrieve or replace the environment's key through the Prodigi dashboard and official support if required, then save the matching Godmode entry. Confirm the provider's replacement behavior before retiring a key used by other consumers. ## Provider docs - [Print API documentation](https://www.prodigi.com/print-api/docs/) - [v4 environments, authentication and operations](https://www.prodigi.com/print-api/docs/v4/) Source: Godmode v0.20.0 provider catalog · 2026-11-13.