What
After a successful login, if CLAUDE_CODE_OAUTH_TOKEN was set when /login started and the gateway is not in use, the success message now notes that new sessions will keep using the old token until you remove it from your shell profile or settings file.
Details
- Message begins
Note: CLAUDE_CODE_OAUTH_TOKEN was set in your environment when /login started. - Helpers were added alongside to re-run the bypass-permissions and auto-mode checks after login.
Evidence
Note: CLAUDE_CODE_OAUTH_TOKEN was set in your environment when /login started.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundleCLAUDE_CODE_OAUTH_TOKEN/login
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.
Confirmed since
Anthropic's documentation has since written up /login, on Claude Code changelog.
* Added the `gatewayInternalNetworks` managed setting, letting administrators allow `/login` to a Claude apps gateway on their organization's own public IPv4 blockchangelog 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 /login, on Claude Code changelog.
Anthropic's release notes agree
Updated /login to repeat the CLAUDE_CODE_OAUTH_TOKEN override warning after a successful login