{"version":"2.1.304","anchor":"remote-control-owner-check-can-be-vouched-by-the-server","canonical_anchor":"remote-control-owner-check-can-be-vouched-by-the-server","heading":"Remote Control reattach has a stricter account check","tier":"notice","area":"Remote Control","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/remote-control-owner-check-can-be-vouched-by-the-server","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Remote Control reattach has a stricter account check\n\nWhen reattaching a Remote Control session, Claude Code can refuse if it cannot confirm the session belongs to your account\n\n**Unclear.** Whether this stricter check is switched on is not stated.\n\n**What**\n\nRemote Control lets you keep using a Claude Code session from another device. Reattaching means reconnecting to a session that was already running.\n\nWhen reattaching, Claude Code may find a saved record that points to a session that is no longer running. If nothing confirms that the session belongs to your account, it now refuses to reattach. There is also a new option that lets the server confirm who owns the session. Before, the check only compared the sign-in stored in a local file.\n\n**Why**\n\nReattaching to a session that belonged to another account may now be refused.\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"}