{"version":"2.1.287","anchor":"chrome-bridge-not-reachable-error","canonical_anchor":"chrome-bridge-not-reachable-error","heading":"Chrome connection message now comes from its own error","tier":"internal","area":"Chrome","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/chrome-bridge-not-reachable-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Chrome connection message now comes from its own error\n\nWhen no browser is connected to Claude in Chrome, Claude Code raises a dedicated error telling you to open Chrome and sign in\n\n**Unclear.** It is not clear whether this replaces an older message in some situations.\n\n**What**\n\nClaude in Chrome is the browser extension that lets Claude Code work in Chrome. When no browser is connected to it, Claude Code now raises a dedicated error with this message: \"No browsers are connected. Open Chrome with the Claude extension and make sure you're signed in to the same claude.ai account.\" The message existed before; it is now attached to its own kind of error.\n\n**Why**\n\nIf Claude cannot reach Chrome, the message tells you exactly what to check: that Chrome is open with the extension and signed in to the same claude.ai account you use with Claude Code.\n\n- Area: Chrome\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}