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.223 Home All releases ←olderv2.1.222 v2.1.224newer→
Claude Code v2.1.223

OAuth token refresh: shared save path, dead-token handling and strict credential reads

You'll notice
Useful3 Signal0
Auth

Login token refresh retries saving and stops cleanly on dead tokens instead of failing quietly.

What

Saving refreshed OAuth tokens now goes through one routine with retries and explicit outcomes, and two failure paths that previously carried on regardless now stop and report.

Details
  • the shared save routine CAS-writes the new tokens up to 3 times and distinguishes 'saved', 'adopted_sibling' and 'save_failed', emitting the matching telemetry including a save-exception event that names the storage backend
  • refresh bails out early when the refresh token is already known to be dead
  • a failed strict read of the credential store under the lock returns lock_error with new telemetry instead of continuing
Evidence

tengu_oauth_token_refresh_locked_read_failed

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.

See this entry in the whole of v2.1.223 →