Authentication

Swelog stores every credential in your operating system’s credential store — Keychain on macOS, Credential Manager on Windows, and the Secret Service on Linux. Nothing is written to swelog.json or any other file in your vault.

Credential	Used by	How it is obtained
GitHub token	swelog fetch github	Prompted on first use
OpenAI API key	swelog summarize with "llm": "openAi"	Prompted on first use
OpenRouter API key	swelog summarize with "llm": "openRouter"	Prompted on first use
Linear authorization	swelog fetch linear	Browser OAuth on first use
Google Calendar authorization	swelog fetch google-calendar	Browser OAuth on first use

Inspecting stored credentials

Review what is stored — values are never printed:

swelog auth status

Clearing a credential

If a credential is revoked or rejected, clear it and run the command again to enter a new one. Every authorization error names this command:

swelog auth clear github
swelog auth clear --all

swelog auth clear accepts github, open-ai, open-router, linear, and google-calendar.

Note

The values accepted by swelog auth clear are hyphenated (open-ai, open-router), which differs from the camelCase spelling used for the llm field in swelog.json (openAi, openRouter).

Environment variable overrides

GITHUB_TOKEN, OPENAI_API_KEY, and OPENROUTER_API_KEY take precedence over the keyring when set. When one of these is set, swelog auth status reports it instead of the stored value.

Linear and Google Calendar are authorized through the browser and have no environment variable override.