{"version":"2.1.290","anchor":"remote-control-stop-can-name-which-turn-it-is-for","canonical_anchor":"remote-control-stop-can-name-which-turn-it-is-for","heading":"A Stop from Remote Control can say which turn it is meant for","tier":"use","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/remote-control-stop-can-name-which-turn-it-is-for","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### A Stop from Remote Control can say which turn it is meant for\n\nA Remote Control Stop request can now name the messages it targets, and is ignored if none of them belong to the current turn\n\n**Unclear.** How the Remote Control service decides when to send this list is not known.\n\n**What**\n\nRemote Control lets you follow and drive a Claude Code session from another device, including pressing Stop to interrupt Claude. A Stop request can now include `for_user_message_uuids`, a list of the messages it is meant to interrupt. If none of those messages belong to the turn Claude is working on right now, the Stop does nothing and that turn carries on.\n\n**Why**\n\nA Stop that arrives late, after you have already sent a new message, no longer cancels the newer reply by mistake.\n\n- Area: Remote Control\n- Names: `for_user_message_uuids`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}