Login refresh failures now say whether to run /login or that another session holds the lock.
What's wrong with this entry?
A failed login-token refresh now says which failure it was: the refresh token is no longer valid, in which case it tells you to run /login, or another Claude Code process is currently holding the refresh lock. This is mostly what you see when two sessions try to refresh credentials at the same time.
OAuth access token could not be refreshed: another Claude Code process is holding the refresh lock
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.225
Untrusted-device recovery can be turned off by a flag; unarchive gets its own 403 handling
Both mention login auth
-
v2.1.234
Clearer error when an Anthropic profile login has expired
Both mention login auth
-
v2.1.242
/login asks how you want to sign in to a Console account
Both mention login auth