{"version":"2.1.315","anchor":"remote-bridge-sign-in-change-detection-and-refactor","canonical_anchor":"remote-bridge-sign-in-change-detection-and-refactor","heading":"Remote Control no longer starts a session when the signed-in account has changed","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/remote-bridge-sign-in-change-detection-and-refactor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Remote Control no longer starts a session when the signed-in account has changed\n\nRemote Control now refuses to start a session if the account behind its credentials changed or could not be confirmed\n\n**What**\n\nRemote Control lets you follow and steer a Claude Code session from another device. When Remote Control refreshes its settings, it now checks the account behind its sign-in. Instead of starting a session, it can return one of these outcomes:\n\n- the sign-in has changed to a different account\n\n- the sign-in could not be read\n\n- the sign-in is in doubt\n\n- no sign-in check was available\n\nThe check that the live preview belongs to you has moved into a shared helper. It works as before.\n\n**Why**\n\nRemote Control should be less likely to carry on under an account you are no longer signed in as.\n\n- Flag `tengu_bridge_requires_action_details`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.315; this account: on, anonymous baseline: on, 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: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}