{"version":"2.1.319","anchor":"chrome-tool-setup-card-for-empty-browser-list-and-a-no-bro","canonical_anchor":"chrome-tool-setup-card-for-empty-browser-list-and-a-no-bro","heading":"Claude in Chrome can show its setup card when no browsers are connected","tier":"notice","area":"Claude in Chrome","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/chrome-tool-setup-card-for-empty-browser-list-and-a-no-bro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Claude in Chrome can show its setup card when no browsers are connected\n\nWhen no browsers are connected, Claude in Chrome can now show its setup card, behind a switch that is off unless turned on remotely\n\n**What**\n\nClaude in Chrome lets Claude Code work with your Chrome browser. Its setup card, which walks you through connecting, used to appear only when the result clearly said the browser was not connected.\n\nIt can now also appear when the list of connected browsers comes back empty. This is behind a server-side switch that is off unless it is switched on remotely.\n\nSelecting a browser now waits for a previous browser to finish connecting first, and errors are tagged with a reason such as no browser being selected.\n\n**Why**\n\nThis affects first-time setup of Claude in Chrome. Waiting for an earlier connection to finish should avoid clashes when switching browsers.\n\n- Flag `tengu_fluttering_sutherland`: Not enough to say (read for one account on one subscription tier against v2.1.319; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Claude in Chrome\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}