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 userand reads thex-oauth-scopesresponse 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_scopesrecords the failure reason:spawn_failed,timeout,gh_api_failed,no_scopes_header. tengu_remote_setup_resultgains agh_token_workflow_scopefield 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.
Names in the bundle/web-setup
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Error reference touched a line naming /web-setup after this was published.
Ultrareview clones <owner>/<repo> in the cloud with the GitHub account connected to your Claude account, and none is connected (or the connection expired). To fix: run /web-setup to reuse your GitHub CLI login, or connect an account at htt…errors see the edit
Confirmed since
Anthropic's documentation has since written up /web-setup, on Claude Code changelog.
* Fixed `/autofix-pr` and other cloud-session commands saying to retry or install the Claude GitHub App when no GitHub account is connected; they now point to `/web-setup` or the web connect pagechangelog see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /web-setup, on Claude Code changelog.
Anthropic's release notes agree
Added a warning in /web-setup when the GitHub CLI token lacks the workflow scope, since pushes to very large repositories can be rejected…