Follow Discord
Sweep 02 Oct 2026 · 18:55Z Build v2.1.288 509 read Stable v2.1.285 Latest v2.1.288 Next v2.1.288 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.288 ·

Login refresh lock is no longer taken from a process that is still alive

When processes share login credentials, a refresh lock held by a live process no longer counts as stale after a fixed 60 seconds

You'll notice Bug Fixes
JSON All of v2.1.288
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
AuthArea: what it touches
Bug FixesKind: in v2.1.288,
Bug FixesSection of the release
What

When several Claude Code processes share the same login credentials, one of them takes a lock while it refreshes the login, so the others wait. Before, any lock older than 60 seconds was treated as abandoned and could be taken over. Now:

  • a lock whose holder is shown to still be running is never treated as abandoned
  • a lock whose holder cannot be shown to be running becomes abandoned after a set time
  • a request to take over the lock is tied to the holder's folder rather than to its process

The log message written when a process takes over a lock is also shorter.

Why

This may cut down on one Claude Code process wrongly taking the lock from another that is still busy refreshing, which matters when you run several at once.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe exact waiting time used when the holder is not proven to be running is not stated.

See this entry in the whole of v2.1.288 →

Feedback