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 #116

Claude Code v2.1.222 ·

Bridge connect timeouts are classified for recovery reporting

Remote connection timeouts now record whether they happened during recovery or a token refresh.

Under the hood Internal Changes
JSON All of v2.1.222
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
Internal ChangesKind: in v2.1.222,
Internal ChangesSection of the release
What

A repl-bridge connect timeout now records which path triggered the attempt, so timeouts during recovery can be told apart from those during a token refresh.

Details
  • recovery_connect_timeout is used for the auth-401, init-4091, and heartbeat-4093 recovery paths.
  • refresh_connect_timeout is used for a proactive token refresh.
  • The existing tengu_bridge_repl_connect_timeout event still fires.
Evidence

recovery_connect_timeout

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