You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
AuthArea: what it touches
ImprovementsKind: in v2.1.234,
ImprovementsSection of the release
What
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.
Details
Triggered when CLAUDE_CODE_OAUTH_TOKEN is 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.
Evidence
includeEnvTokenWarning
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed: after /login while CLAUDE_CODE_OAUTH_TOKEN is set, the stale-token reminder no longer leaks into Claude's automatically resumed turn…
