Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.248 Home All releases ←olderv2.1.247 v2.1.250newer→
Claude Code v2.1.248

/web-setup warns when your GitHub CLI token lacks the workflow scope

You'll notice
Useful3 Signal2
GitHub Integration

/web-setup warns if your gh token lacks the workflow scope before you connect.

/web-setup
What

Before 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.

Details
  • Runs gh api --include user and reads the x-oauth-scopes response header, classifying the token as present, missing or unknown.
  • The warning panel appears above the confirm prompt and points at gh auth refresh -s workflow.
  • New telemetry event remote_setup_gh_token_scopes records the failure reason: spawn_failed, timeout, gh_api_failed, no_scopes_header.
  • tengu_remote_setup_result gains a gh_token_workflow_scope field on both success and import_failed.
  • No flag gates it; everyone on this build gets the check.
Evidence

Your GitHub CLI token doesn't have the workflow scope.

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.248 →