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

Claude Code v2.1.228 ·

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

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

You'll notice Improvements
JSON All of v2.1.228
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SessionsArea: what it touches
ImprovementsKind: in v2.1.228,
ImprovementsSection of the release
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 →

Feedback