mise/Tool/GitHub/Token/Native/GitHub/OAuth

• Native GitHub OAuth

  • In upstream mise documentation, Native GitHub OAuth names an experimental built-in path where mise itself runs GitHub’s device flow against a GitHub App client ID (github.oauth_client_id), caches tokens, and can export GITHUB_TOKEN into the environment after mise activate / hook-env / mise env / mise exec—without requiring a PAT, app private key, gh, or ghtkn for mise’s own GitHub API traffic.
  • Enable experimental (for example mise settings set experimental true or MISE_EXPERIMENTAL=1) before relying on it; behavior and cache format may change. First-time setup uses mise token github --oauth for authorization; see the linked section for optional oauth_scopes, oauth_open_browser, and oauth_export_env.
  • Token priority for github.com lists this source after credential_command and before github_tokens.toml; the full ordering and GHE variants are summarized on mise/Tool/GitHub Token.
  • Relationship to Person/Shunsuke Suzuki/GitHub/ghtkn: the mise doc states the native OAuth design was inspired by ghtkn; if you prefer a separate binary and stdout-based wiring, use credential_command with ghtkn get as described under Using ghtkn on the same doc page.
  • GitHub/CLI tokens are a different integration: mise can read gh hosts.yml when no higher-priority token is set—see gh CLI integration on that page (mise reads the file directly; long-lived gh auth login OAuth tokens there are not the same mechanism as mise native OAuth).