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
HomeReleasesv2.1.225entry #59

Claude Code v2.1.225 ·

Remote Control: token refresh chain gives up loudly, and auth changes invalidate in-flight attempts

Remote Control now reports dead token refreshes instead of failing silently, and re-logging in cancels stale connection attempts.

You'll notice Improvements
JSON All of v2.1.225
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
ImprovementsKind: in v2.1.225,
ImprovementsSection of the release
What

When the bridge token refresher exhausts its retry chain it now reports the failure instead of stopping quietly, and re-logging in cancels bridge init attempts that started under the old credentials.

Details
  • On exhaustion it logs an error built from the fixed fragment "Refresh chain exhausted for sessionId=" plus the session id and failure count, emits bridge_token_refresh_exhausted, and returns "no_oauth_token" to the caller.
  • App state gained authChangeGeneration, bumped on login or account change; bridge init compares it before applying results.
  • The 401 recovery path keys off a per-endpoint needsOAuthRefresh flag and aborts init after a successful refresh rather than continuing with the stale response.
Evidence

bridge_token_refresh_exhausted

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.225 →

Feedback