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.228 Home All releases olderv2.1.227 v2.1.229newer
Claude Code v2.1.228

Bridge reconnects re-register after a conflict, up to a limit

You'll notice
Useful3 Signal2
Sessions

After a network drop, sessions re-register automatically, but only a limited number of times per hour.

What

After a network interruption, a bridge session that comes back to a conflict now re-registers instead of giving up, but no more than a fixed number of times per hour. Past that it stops with an explicit message.

Details
  • Worker registration uses compare-and-swap fencing so a stale connection cannot overwrite a newer one.
  • If another connection has genuinely taken the session over, this device stands down and says so rather than retrying.
Evidence

another connection took over this session while it was being restored \u2014 this device is standing down

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