{"version":"2.1.238","anchor":"remote-clients-can-stop-a-single-task","canonical_anchor":"remote-clients-can-stop-a-single-task","heading":"Remote clients can stop a single task","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/remote-clients-can-stop-a-single-task","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Remote clients can stop a single task\n\nRemote clients can now stop one specific task rather than interrupting the whole turn.\n\n**What**\n\nThe remote-control transport gained an `onStopTask` handler next to the existing interrupt handler, so a remote client can stop one specific task instead of interrupting the whole turn. It is plumbed from the REPL bridge host through the bridge session, unconditionally.\n\n**Details**\n\n- User messages relayed into a remote session can now also carry a `priority` field.\n\n**Evidence**\n\n`onStopTask`\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}