The warning about a set OAuth token env var can now arrive as its own message after login.
What's wrong with this entry?
Logging in while CLAUDE_CODE_OAUTH_TOKEN is set no longer always glues the warning onto "Login successful". A three-way choice now picks no warning, an inline one, or a separate notice; when the session is about to auto-retry the query that failed, the warning is delivered once as its own message.
- Triggered when
CLAUDE_CODE_OAUTH_TOKENis set in the environment and the gateway is not active. - The login result formatter takes an explicit flag saying whether to include the warning, so the two paths cannot both emit it.
includeEnvTokenWarning
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.229
OAuth token warning no longer tells you to unset the variable
Both mention oauth token auth
-
v2.1.223
Clearer failures when claude.ai project scopes can't be obtained
Both mention oauth token auth
-
v2.1.229
/login warns if an OAuth token is set in your environment
Both mention oauth token auth