{"version":"2.1.319","anchor":"chrome-bridge-refuses-to-use-a-socket-opened-for-a-different","canonical_anchor":"chrome-bridge-refuses-to-use-a-socket-opened-for-a-different","heading":"Chrome connection refuses to work for a different account than the one signed in","tier":"notice","area":"Claude in Chrome","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/chrome-bridge-refuses-to-use-a-socket-opened-for-a-different","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Chrome connection refuses to work for a different account than the one signed in\n\nClaude Code now closes its Chrome connection if it was opened for another account, and will not connect when nobody is signed in\n\n**What**\n\nClaude Code talks to Chrome through a connection tied to a signed-in account. It now checks that the account signed in matches the account the connection was opened for:\n\n- On a mismatch, it closes the connection, refuses new connections and blocks any further messages.\n\n- When nobody is signed in, it does not connect at all.\n\nA program hosting Claude Code can switch this check off. When it does, a warning is logged.\n\n**Why**\n\nAfter you switch accounts, browser actions can no longer go out over a connection made for the previous account.\n\n- Area: Claude in Chrome\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}