Source Intelligence

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.225 Home All releases olderv2.1.224 v2.1.226newer

Bridge reconnects only refresh OAuth for the close codes that need it

You'll notice
Useful2 Signal0
Remote Control

Remote Control reconnects skip needless token refreshes, so ordinary disconnects recover faster.

What

Reconnect recovery no longer forces an OAuth refresh for every handled close code, cutting unnecessary token work on non-auth disconnects.

Details
  • The per-close-code recovery table (401, 4091, 4093, 4094) gains needsOAuthRefresh, true for 401 and 4094 only.
  • The flag decides whether to force an OAuth refresh up front, whether to enter the retry loop that prompts for a fresh login, and whether to do a late refresh instead.
  • The CCR client gained an onRequestAuthOk callback fired on a successful heartbeat, wired through the bridge so the session can mark auth as proven.
Evidence

needsOAuthRefresh

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 →