When another process refreshes your login, the session re-reads who you are signed in as.
What's wrong with this entry?
When Claude Code detects that another process already refreshed the login token, it now clears its in-process cache of the authenticated account before recording the race, so the session re-derives who you are signed in as rather than holding on to the pre-refresh account.
- The cache is invalidated by bumping its epoch, which happens before the
tengu_oauth_token_refresh_race_resolvedtelemetry fires.
tengu_oauth_token_refresh_race_resolved
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.234
Signing back into the same account keeps a pending auto-resume
Both mention auth
-
v2.1.234
Token screen reports actual remaining validity
Both mention auth
-
v2.1.234
Setup-token login result carries the expiry
Both mention auth