{"version":"2.1.299","anchor":"git-worktreecheckout-validation-reworked-github-token-reso","canonical_anchor":"git-worktreecheckout-validation-reworked-github-token-reso","heading":"Claude Code can now find a GitHub token from your environment or the gh tool","tier":"notice","area":"GitHub","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/git-worktreecheckout-validation-reworked-github-token-reso","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Claude Code can now find a GitHub token from your environment or the gh tool\n\nClaude Code looks for a GitHub token in `GH_TOKEN`, `GITHUB_TOKEN` or enterprise variants, then falls back to `gh auth token`\n\n**What**\n\nClaude Code can now look up a GitHub token, the credential that lets it act on GitHub for you. It checks, in order:\n\n- the environment variables `GH_TOKEN` and `GITHUB_TOKEN`, or enterprise ones such as `GH_ENTERPRISE_TOKEN`\n\n- the output of `gh auth token`, from GitHub's command-line tool\n\nIt skips `gh` when that tool's config folder has no `hosts.yml` or `config.yml`, since there is then no login to read.\n\nChecks on git worktrees (extra working copies of a repository) also changed: errors now say which config file included another.\n\n**Why**\n\nIf you already have a GitHub token in your environment or are logged in with `gh`, Claude Code can pick it up without separate setup.\n\n- Area: GitHub\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}