{"version":"2.1.232","anchor":"remote-control-tells-you-when-another-terminal-already-holds","canonical_anchor":"remote-control-tells-you-when-another-terminal-already-holds","heading":"Remote Control tells you when another terminal already holds the conversation","tier":"use","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/remote-control-tells-you-when-another-terminal-already-holds","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Remote Control tells you when another terminal already holds the conversation\n\nYou're now told when another terminal holds Remote Control, and pointed at \/remote-control.\n\n**What**\n\nWhen another Claude Code on the same machine already has Remote Control for a conversation, you now get a message saying so and pointing at `\/remote-control` to move it to the current terminal.\n\n**Details**\n\n- The remote control request gained two fields: one naming a session to reattach to, and one asking that the session not be archived when it exits.\n- The receiving side reads those as a reattach session id and a never-archive flag.\n\n**Evidence**\n\n`already has Remote Control for this conversation \u00b7 run \/remote-control to move it to this terminal`\n\n- Area: Remote Control\n- Names: `\/remote-control`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}