[DOCS] `/web-setup` docs omit warning before replacing an existing GitHub App connection
Documentation Type
Missing documentation (feature not documented)
Documentation Location
https://code.claude.com/docs/en/web-quickstart
Section/Topic
Connect from your terminal and the GitHub authentication guidance for Claude Code on the web
Current Documentation
The /web-setup quickstart currently says:
If you already use the GitHub CLI (gh), you can set up Claude Code on the web without opening a browser. This requires the Claude Code CLI./web-setupreads your localghtoken, links it to your Claude account, and creates a default cloud environment if you don't have one. This syncs yourghtoken to your Claude account. If you don't have a cloud environment yet,/web-setupcreates one with Trusted network access and no setup script.
The web auth reference currently says:
Cloud sessions need access to your GitHub repositories to clone code and push branches. You can grant access in two ways: | GitHub App | Authorize the Claude GitHub App during web onboarding. | |/web-setup| Run/web-setupin your terminal to sync your localghCLI token to your Claude account. | Either method works.
What's Wrong or Missing?
The docs explain the two GitHub authentication methods, but they do not document the v2.1.142 behavior change that /web-setup warns before replacing an existing GitHub App connection.
That leaves a gap for users who already connected GitHub through browser onboarding and later run /web-setup from the CLI. The current docs describe both paths as equivalent, but do not say that switching to /web-setup can replace the existing GitHub App connection or that Claude Code now shows a warning before doing so.
Suggested Improvement
Add a short warning note to the /web-setup walkthrough and the GitHub authentication options section, for example:
Warning: If your account is already connected through the Claude GitHub App, running/web-setupcan replace that existing connection with your localghCLI credentials. Claude Code warns before making this change.
Also mention when a user might want to keep the GitHub App connection instead, such as when they rely on App-based setup flow or are comparing the two connection methods. Mention that this warning behavior was added in v2.1.142.
Impact
Medium - Makes feature difficult to understand
Additional Context
Affected Pages:
| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/web-quickstart | 80-109 | /web-setup walkthrough explains token sync and environment creation but does not mention the replacement warning |
| https://code.claude.com/docs/en/claude-code-on-the-web | 31-48 | GitHub authentication options present GitHub App and /web-setup as parallel choices, but do not explain replacement behavior |
Total scope: 2 pages affected
Relevant changelog item in v2.1.142: /web-setup warns before replacing an existing GitHub App connection.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗