You'll notice
Useful4 Signal2
Interrupting from mobile, Slack or desktop now also stops your background tasks.
What's wrong with this entry?
Anonymous. No account, no email.
What
Interrupting 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.
Details
- The sweep is wrapped in try/catch; a throw is reported to the existing per-task-stop telemetry counter under
bridge_interrupt_sweep_throw.
Evidence
bridge_interrupt_sweep_throw
Strings lifted out of the shipped bundle, so the claim above can be checked against them.