[DOCS] `/upgrade` command reference still describes the pre-v2.1.208 login fallback
Documentation Type
Incorrect/outdated documentation
Documentation Location
https://code.claude.com/docs/en/commands
Section/Topic
The /upgrade row in the "All commands" table.
Current Documentation
The /upgrade row currently says:
Open the upgrade page in your browser to switch to a higher plan tier. When the browser fails to open, the command shows a sign-in prompt without printing the URL
What's Wrong or Missing?
This describes behavior that was fixed in Claude Code v2.1.208. The v2.1.208 release notes state:
Fixed /upgrade showing a login flow instead of the upgrade URL when the browser fails to open
When the browser cannot be opened, the command now prints the upgrade URL instead of showing a login flow. The /upgrade reference is therefore outdated and can send users into an unnecessary authentication flow, while failing to tell them where to find the URL they can open manually.
Suggested Improvement
Update the /upgrade row to describe the v2.1.208 behavior, for example:
Open the upgrade page in your browser to switch to a higher plan tier. As of Claude Code v2.1.208, when the browser fails to open, the command prints the upgrade URL so you can open it manually.
If the behavior is intentionally limited to v2.1.208, state the applicable version range rather than retaining the pre-fix login-flow wording.
Impact
Medium - Makes feature difficult to understand
Additional Context
The related background-session errors section already records the v2.1.208 behavior:
In v2.1.208 only, the/modelpicker was also refused in a background session, and/upgradeprinted the upgrade URL instead of opening a browser.
The command reference should use consistent wording so users who cannot launch a browser—such as users working over SSH or in a headless environment—know to open the printed URL manually.
Affected Pages:
| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/commands | /upgrade command behavior when the browser fails to open |
Total scope: 1 page affected
The behavior change is documented in the v2.1.208 release notes.