Claude Code v2.1.222 ·
Design OAuth refresh lock holds longer and reports compromise
Slow token refreshes no longer trip the lock early, cutting spurious login hiccups.
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
ImprovementsKind: in v2.1.222,
ImprovementsSection of the release
What
The lock guarding OAuth token refresh tolerates slower refreshes and lets the holder find out if its lock was taken away mid-flight.
Details
- Stale window raised from 10s to 60s, with a 5s update interval.
- The callback now receives an object exposing
isCompromised(). - Lock contention throws a dedicated error class rather than a bare
Error.
Evidence
Design OAuth refresh lock compromised
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.222 →
