What
The suggestion to run /web-setup to connect a GitHub account previously required both an experiment flag that defaulted to off and the allow_quick_web_setup entitlement, so most people never saw it. The experiment check is gone and both places that offer the advice now share one helper that checks the entitlement alone.
Details
- The two call sites are the routine-authoring prompt and the GitHub-access preflight message.
Evidence
they should run /web-setup to connect their GitHub account (or install the Claude GitHub App on the repo as an alternative)
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…