AlmightyGPT markAlmightyGPT
Docs navigation
Auth setup

Store provider keys locally. Do not put them in repo config.

AlmightyGPT uses guided setup, OS keychain storage, VS Code SecretStorage, scoped environment injection, and redaction checks before provider calls.

CLI setup

Terminal
> almightygpt auth

The guided flow lets you choose OpenAI, Anthropic, or Google, opens the relevant key page, accepts the key through hidden input, validates it, and stores it locally.

Check current status

Terminal
> almightygpt auth status

Add --validate when you want real model-class validation calls. Use --validate-provider google when you only want to check one provider.

Resolver priority

  1. Explicit command input, such as setup via stdin.
  2. Environment variable for this process.
  3. OS keychain entry.
  4. Missing or keychain error state.
Why env still exists
Environment variables are useful for CI and one-off shells. For daily local use, prefer keychain or VS Code SecretStorage.

VS Code auth

VS Code Chat
> @almightygpt /auth

The extension stores keys in VS Code SecretStorage. Review commands pass only the keys needed for that command into the CLI process.