Two Claude Code processes refreshing your login at once now give a clear wait-and-retry message.
What's wrong with this entry?
When two Claude Code processes try to refresh OAuth credentials at the same time, the one that loses the race now gets a message naming the cause and pointing at a recovery, rather than a generic authentication failure. The condition is treated as transient rather than a sign that your login is broken, so the suggested response is to wait and try again. Nothing needs enabling.
- Fires when another process already holds the credential refresh lock, or when a process exited part way through a refresh and left the lock behind.
- The plain failure reads
Could not refresh your login because another Claude Code process is refreshing it. - In debug mode the fuller text explains the cause, suggests retrying in a minute, and if it persists suggests closing other Claude Code processes or signing in again.
Failed to refresh OAuth token: another Claude Code process is refreshing it or exited mid-refresh. This is usually transient; retry in a minute, and if it persists close other Claude Code processes or sign in again, Could not refresh your login because another Claude Code process is refreshing it
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