The GitHits CLI reads several environment variables at startup. You can use them to authenticate without a browser, switch credential storage modes, or suppress update notifications.
GITHITS_API_TOKEN
Set an API token to authenticate without browser OAuth. This is the recommended approach for CI pipelines, automation scripts, and headless environments where a browser login isn’t practical.
Tokens follow the format ghi-... and can be generated from your GitHits account settings.
When GITHITS_API_TOKEN is set, the CLI skips local OAuth storage entirely. You can verify this with npx githits@latest auth status, which reports the credential source.
GITHITS_API_TOKEN takes precedence over stored OAuth credentials. If both are present, the environment variable is used.
GITHITS_AUTH_STORAGE
Override the OAuth credential storage mode for a single process or for all GitHits commands in the current shell session.
keychain (default) — stores OAuth credentials in the system keychain (macOS Keychain, Windows Credential Manager, Linux Secret Service).file — stores OAuth credentials as JSON files in the GitHits config directory.
Use file mode in SSH sessions, CI environments, or when persistent keychain prompts remain even after granting access.
File storage is not encrypted. Any process running as your OS user can read the stored tokens. For CI and automation, use GITHITS_API_TOKEN instead.
GITHITS_TELEMETRY
When set to any non-empty value, the CLI emits end-of-run timing spans to stderr. Use this for local profiling and performance investigation. The output goes to stderr only and does not affect stdout.
GITHITS_DISABLE_UPDATE_CHECK
When set to any non-empty value, suppresses the npm latest-version check and update notice that the CLI prints when a newer version is available. Useful in CI environments where the notice would pollute log output.
