{"version":"2.1.242","anchor":"github-cli-checks-tell-an-old-gh-apart-from-a-broken-one","canonical_anchor":"github-cli-checks-tell-an-old-gh-apart-from-a-broken-one","heading":"GitHub CLI checks tell an old gh apart from a broken one","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/github-cli-checks-tell-an-old-gh-apart-from-a-broken-one","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### GitHub CLI checks tell an old `gh` apart from a broken one\n\nAn outdated GitHub CLI no longer looks like a missing or signed-out one.\n\n**What**\n\nChecking whether your GitHub CLI login can be shared now reports two outcomes it previously folded into not-installed or not-authenticated: `gh_too_old`, meaning `gh` is logged in but lacks the auth-token command, and `gh_check_failed`, meaning the check itself errored. Remote and web setup surface each with its own message, so an outdated CLI no longer looks like a missing or signed-out one.\n\n**Details**\n\n- The status check is version-aware and falls back to a network check on older `gh` versions that cannot report their capability directly.\n- `gh_too_old` shows \"GitHub CLI is logged in, but this version is too old to share its login\", names 2.17.0 or newer as the requirement for `gh auth token`, and offers the web sign-in path instead.\n- `gh_check_failed` reports that the status check failed and appends the trimmed error text.\n- Both outcomes are reported through the existing `tengu_remote_setup_result` event.\n- A background probe of the GitHub connection times out after 3 seconds and reports to a new `api_github_connection_status` event, distinguishing connected, not connected and unknown; the foreground path allows 10 seconds.\n\n**Evidence**\n\n`api_github_connection_status`, `GitHub CLI is logged in, but this version is too old to share its login`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}