Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.222entry #55

Claude Code v2.1.222 ·

Bridge recovery has a rebuild budget and richer failure telemetry

A remote bridge that cannot recover now stops retrying after a budget and tells you why.

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

Recovery from 401, 4091 and 4093 transport closes is now table-driven, and repeated transport rebuilds are capped so a bridge that cannot heal stops retrying and says why.

Details
  • each close code maps to its own reconnect detail, cause, diagnostic, terminal-vs-retry fetch failure classification and recovered code
  • 4093 rebuilds within a one hour window are budgeted; exceeding the budget stops recovery with an explicit message
  • new presence telemetry codes: recovery_exhausted, heartbeat_budget_exhausted, recovery_no_oauth_token, recovery_reauth_required, recovery_credentials_fetch_failed, recovery_credentials_rejected, recovery_abandoned_at_teardown, bridge_connect_died_before_presence
Evidence

presence heartbeats to the server kept failing after repeated reconnects

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

Feedback