{"version":"2.1.232","anchor":"remote-control-reattach-checks-who-owned-the-conversation","canonical_anchor":"remote-control-reattach-checks-who-owned-the-conversation","heading":"Remote Control reattach checks who owned the conversation","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/remote-control-reattach-checks-who-owned-the-conversation","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Remote Control reattach checks who owned the conversation\n\nReattaching to Remote Control now verifies you own the conversation before reusing it.\n\n**What**\n\nReattaching to a Remote Control conversation now verifies that the recorded owner is the account currently logged in. If it cannot be confirmed, Claude Code either refuses with a warning or attaches with history channels suppressed, rather than silently reusing the old pointer.\n\n**Details**\n\n- Reattach now distinguishes a session named by the host from a restored pointer, and records why it reattached: owner match pinned, owner match, identity unreadable, or owner unknown.\n- Suppressing history channels means the reattached session does not replay prior conversation content.\n\n**Evidence**\n\n`Host-directed reattach: this conversation\\u2019s recorded owner could not be confirmed as the current login \\u2014 attaching with history channels suppressed`\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}