{"version":"2.1.290","anchor":"list-connected-browsers-now-throws-on-a-malformed-response","canonical_anchor":"list-connected-browsers-now-throws-on-a-malformed-response","heading":"Errors when listing connected browsers now show instead of an empty list","tier":"notice","area":"Chrome & Browser","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/list-connected-browsers-now-throws-on-a-malformed-response","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Errors when listing connected browsers now show instead of an empty list\n\nA bad reply when listing connected browsers now raises an error instead of quietly showing that no browsers are connected\n\n**Unclear.** It is not clear how the error is shown to you.\n\n**What**\n\nClaude Code can ask the browser extension which browsers are connected to it. Because of a bug, that request always ended with an empty list. Now Claude Code checks the reply, and if the reply is not in the expected shape, it raises an error.\n\n**Why**\n\nProblems connecting to the browser extension now surface as errors. Before, they looked as if no browsers were connected.\n\n- Area: Chrome & Browser\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}