Source Intelligence
Follow Discord

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.222 Home All releases ←olderv2.1.221 v2.1.223newer→
Claude Code v2.1.222

Bridge connect timeouts are classified for recovery reporting

Under the hood
Useful1 Signal0
Remote Control

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

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 →