{"version":"2.1.321","anchor":"remote-control-session-policy-and-login-teardown","canonical_anchor":"remote-control-session-policy-and-login-teardown","heading":"Signing in to a different account now disconnects an attached Remote Control link","tier":"notice","area":"Remote Control","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/remote-control-session-policy-and-login-teardown","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Signing in to a different account now disconnects an attached Remote Control link\n\nWhen the signed-in account changes, Claude Code disconnects a Remote Control link attached through the SDK, and reconnects are marked as recovered\n\n**What**\n\nRemote Control lets you reach a Claude Code session from somewhere else, through a link called a bridge. When the bridge is attached through the SDK (the kit for building apps on Claude Code), it is now disconnected if a sign-in changes the account. Claude Code notes that the login left the bridge with no proven owner.\n\nOther changes:\n\n- When the bridge reconnects, its status update now says it recovered.\n\n- The reason recorded when the bridge is shut down now varies. Before, it was always that Remote Control was disabled.\n\n**Why**\n\nSigning in as someone else no longer leaves an existing remote link in place under the new account.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}