{"version":"2.1.302","anchor":"bridge-reconnect-telemetry-gains-recovery-bucket","canonical_anchor":"bridge-reconnect-telemetry-gains-recovery-bucket","heading":"Remote-bridge recovery reports how long recovery took","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/bridge-reconnect-telemetry-gains-recovery-bucket","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Remote-bridge recovery reports how long recovery took\n\nRemote-bridge reconnect and recovery events now carry a `recovery_bucket` time range and track when the failure began\n\n**What**\n\nThe remote bridge is the connection that links a Claude Code session to a remote client. Its reconnect reporting now records more timing detail.\n\n- Recovery events now include `recovery_bucket`, a rough time range for how long the recovery took. This applies after a 403 stream recovery (a 403 is an access-refused response from the server) and after a transport recovery.\n\n- Transport recovery now records when the failure started, and recovery that is still pending keeps `at` timestamps.\n\n- The handler that runs when the connection closes also records when the last message frame was read.\n\nBefore, the recovered event carried only `remint_attempts`.\n\n**Why**\n\nThis is diagnostic reporting only. It has no visible effect on how Claude Code behaves for you.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}