{"version":"2.1.246","anchor":"interrupting-from-a-remote-client-also-stops-background-task","canonical_anchor":"interrupting-from-a-remote-client-also-stops-background-task","heading":"Interrupting from a remote client also stops background tasks","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/interrupting-from-a-remote-client-also-stops-background-task","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Interrupting from a remote client also stops background tasks\n\nInterrupting from mobile, Slack or desktop now also stops your background tasks.\n\n**What**\n\nInterrupting a session from mobile, Slack or the desktop bridge used to abort only the current turn. It now aborts with an explicit \"remote-cancel\" reason and then sweeps the background task registry, so in-flight background tasks are stopped rather than left running. Live for any session with Remote Control enabled; no feature flag guards it, only the pre-existing check that a turn is in flight.\n\n**Details**\n\n- The sweep is wrapped in try\/catch; a throw is reported to the existing per-task-stop telemetry counter under `bridge_interrupt_sweep_throw`.\n\n**Evidence**\n\n`bridge_interrupt_sweep_throw`\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}