{"version":"2.1.248","anchor":"web-setup-warns-when-your-github-cli-token-lacks-the-workflo","canonical_anchor":"web-setup-warns-when-your-github-cli-token-lacks-the-workflo","heading":"\/web-setup warns when your GitHub CLI token lacks the workflow scope","tier":"notice","area":"GitHub Integration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/web-setup-warns-when-your-github-cli-token-lacks-the-workflo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### \/web-setup warns when your GitHub CLI token lacks the `workflow` scope\n\n\/web-setup warns if your gh token lacks the workflow scope before you connect.\n\n**What**\n\nBefore connecting Claude on the web to GitHub, setup now checks your `gh` token's scopes and warns if `workflow` is missing, because pushes that touch GitHub Actions workflow files will be rejected. You can continue anyway.\n\n**Details**\n\n- Runs `gh api --include user` and reads the `x-oauth-scopes` response header, classifying the token as present, missing or unknown.\n- The warning panel appears above the confirm prompt and points at `gh auth refresh -s workflow`.\n- New telemetry event `remote_setup_gh_token_scopes` records the failure reason: `spawn_failed`, `timeout`, `gh_api_failed`, `no_scopes_header`.\n- `tengu_remote_setup_result` gains a `gh_token_workflow_scope` field on both success and import_failed.\n- No flag gates it; everyone on this build gets the check.\n\n**Evidence**\n\n`Your GitHub CLI token doesn't have the workflow scope.`\n\n- Area: GitHub Integration\n- Names: `\/web-setup`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}