Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.248 ·

Clearer error when another Claude Code process is refreshing the same login token

Two Claude Code processes refreshing your login at once now give a clear wait-and-retry message.

You'll notice New Features
JSON All of v2.1.248
You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
AuthArea: what it touches
New FeaturesKind: in v2.1.248,
What probably matters to youSection of the release
What

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.

Details
  • 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.
Evidence

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.

See this entry in the whole of v2.1.248 →

Feedback