Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.222 Home All releases ←olderv2.1.221 v2.1.223newer→
Claude Code v2.1.222

Design OAuth refresh distinguishes lock contention from failure

You'll notice
Useful2 Signal0
Elsewhere

Design sign-in refreshes no longer report a failure when another process just got there first.

What

A refresh that loses the cross-process lock race is now reported as contention rather than as a failed refresh, and a compromised lock can still succeed.

Details
  • New DesignOauthLockContendedError marks the case where another process holds the refresh lock.
  • On a compromised lock the stored token is re-read and accepted if it is still fresh.
  • New telemetry codes: design_oauth_refresh_lock_contention, _lock_compromised, _lock_error.
Evidence

Design OAuth lock contention: another process is holding the refresh lock

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 →