{"version":"2.1.319","anchor":"chrome-bridge-is-bound-to-the-signed-in-account","canonical_anchor":"chrome-bridge-is-bound-to-the-signed-in-account","heading":"The Chrome connection now only works for the account you are signed in with","tier":"notice","area":"Claude in Chrome","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/chrome-bridge-is-bound-to-the-signed-in-account","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### The Chrome connection now only works for the account you are signed in with\n\nClaude Code's Chrome connection now checks your signed-in account, closing when the account differs and stopping when nobody is signed in\n\n**What**\n\nClaude Code can control Chrome through a live connection to the browser. That connection now checks which account is signed in before connecting, when it opens, on each message and on its regular keep-alive signals. Before, it made no such checks.\n\n- if a different account is signed in, the connection closes\n\n- if nobody is signed in, Claude Code stops trying to reconnect\n\n- a browser action that needs your permission is rejected with a clear message when nobody is signed in or a different account is\n\n- an action aimed at a specific device is now rejected only when that device disconnects, not when the selected device goes away\n\n**Why**\n\nAfter switching accounts with `\/login`, browser actions can no longer run under, or be approved for, the wrong account.\n\n- Area: Claude in Chrome\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}