ghtkn

Choose and configure where ghtkn stores access tokens (keyring, text, agent). Use when the OS keyring is unavailable (containers, microVMs), or when setting up the ghtkn agent backend.

Configure ghtkn via config file, environment variables, and CLI args. Use for configuration priority, disabling browser open, the GitHub account picker, enterprise GitHub App sharing, or GHTKN_GITHUB_TOKEN.

Understand how ghtkn works internally and how its tokens compare to alternatives. Use to explain the token workflow, compare with GitHub CLI OAuth / fine-grained PAT / installation tokens, or discuss API rate limits.

Configure ghtkn as a Git credential helper and switch GitHub Apps by repository owner. Use when setting up git authentication via ghtkn, handling fork repos, or troubleshooting the credential helper on macOS.

Install the ghtkn CLI and verify downloaded release assets. Use when installing ghtkn via Homebrew, Scoop, aqua, go install, or GitHub Releases, or verifying assets with gh / slsa-verifier / Cosign.

Configure and switch between multiple GitHub Apps in ghtkn. Use when setting up per-organization apps, selecting an app by argument or GHTKN_APP, or switching apps per directory with direnv.

Revoke leaked or compromised ghtkn access tokens. Use during incident response, when a token leaks, or to revoke an app's stored token via ghtkn revoke or the GitHub REST API.

Manage the ghtkn access token lifecycle - regeneration, ghtkn auth, the automatic device flow, and clipboard. Use when tokens expire, configuring -min-expiration, authenticating, or copying the one-time code.

Diagnose ghtkn problems and known limitations. Use when ghtkn or the gh wrapper misbehaves, a token is expired (401), the device flow code isn't shown, or hitting Packages API / cross-user repo limits.