{"version":"2.1.287","anchor":"chrome-browser-picker-distinguishes-bridge-unreachable","canonical_anchor":"chrome-browser-picker-distinguishes-bridge-unreachable","heading":"Browser picker telemetry now records when the Chrome bridge can't be reached","tier":"internal","area":"Chrome","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/chrome-browser-picker-distinguishes-bridge-unreachable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Browser picker telemetry now records when the Chrome bridge can't be reached\n\nWhen choosing a browser fails because the Chrome bridge is unreachable, telemetry now records that cause instead of a general failure\n\n**What**\n\nWhen Claude Code fails to select a browser through its Chrome bridge, telemetry now separates two cases. Telemetry is usage data sent to Anthropic. If the bridge could not be reached, it reports `bridge_unreachable`. Other failures are still reported as `select_failed`. Before this change, every failure was reported as `select_failed`. The message for when no browsers are found now uses shared wording.\n\n**Why**\n\nThe usage data now tells connection problems apart from other selection failures. Nothing changes in what you do.\n\n- Area: Chrome\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}