After logging in, you're warned if an OAuth token in your environment will override it later.
What's wrong with this entry?
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.
- 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.
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.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.223
Clearer failures when claude.ai project scopes can't be obtained
Both mention oauth token login auth
-
v2.1.234
The CLAUDE_CODE_OAUTH_TOKEN login warning can arrive as its own message
Both mention oauth token auth
-
v2.1.221
Artifact credentials and artifact base URLs are stripped from child process environments
Both mention oauth token