After a token refresh, requests use your current account rather than the previous one.
What's wrong with this entry?
After a token refresh, Claude Code clears the cached snapshot of the signed-in account (account id, email, organisation), so requests made after the refresh use the current account rather than the previous one.
- Applies after recovering from a 401 using the token on disk, after an SDK token callback refresh, after adopting a newer token written by another Claude Code process, and on login-state reset.
- Request metadata for the account id now falls back to the stored OAuth account.
tengu_oauth_401_recovered_from_disk
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