{"version":"2.1.242","anchor":"github-cli-login-is-detected-with-gh-auth-token","canonical_anchor":"github-cli-login-is-detected-with-gh-auth-token","heading":"GitHub CLI login is detected with gh auth token","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/github-cli-login-is-detected-with-gh-auth-token","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### GitHub CLI login is detected with `gh auth token`\n\nGitHub CLI sign-in is checked with a quick local command instead of a silent network call.\n\n**What**\n\nClaude Code now checks whether your `gh` is signed in by running `gh auth token` with a 5 second timeout, classifying the result as not installed, authenticated, not authenticated or unknown. An older `gh` without that subcommand reports unknown instead of quietly making a network call.\n\n**Details**\n\n- Parsing `gh auth status` is only used when the caller passes `allowNetworkFallbackForOldGh`.\n\n**Evidence**\n\n`this GitHub CLI version has no `gh auth token``\n\n- Area: Elsewhere\n- Names: `gh auth token`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}