{"version":"2.1.287","anchor":"chrome-bridge-unreachable-handled-quietly-chrome-dialog-get","canonical_anchor":"chrome-bridge-unreachable-handled-quietly-chrome-dialog-get","heading":"Chrome browser list comes back empty instead of failing when Chrome cannot be reached","tier":"notice","area":"Chrome","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/chrome-bridge-unreachable-handled-quietly-chrome-dialog-get","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Chrome browser list comes back empty instead of failing when Chrome cannot be reached\n\nIf Claude Code cannot reach Chrome, asking for the list of Chrome browsers returns an empty list rather than an error\n\n**What**\n\nApps that drive Claude Code can ask it which Chrome browsers are available. If Claude Code cannot reach its connection to Chrome, that request now returns an empty list instead of failing, and the problem is treated as expected rather than reported as an error.\n\nThe request for the Chrome dialog now also returns the starting value for Claude in Chrome on this machine.\n\n**Why**\n\nRemote apps should show fewer error messages that do not point to a real problem.\n\n- Area: Chrome\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}