{"version":"2.1.277","anchor":"remote-bridge-gains-an-oncancelasyncmessage-rpc-handler","canonical_anchor":"remote-bridge-gains-an-oncancelasyncmessage-rpc-handler","heading":"Remote bridge gains an onCancelAsyncMessage RPC handler","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/remote-bridge-gains-an-oncancelasyncmessage-rpc-handler","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Remote bridge gains an onCancelAsyncMessage RPC handler\n\nRemote clients can now cancel a queued background message instead of only interrupting an active turn\n\n**What**\n\nThe remote-bridge transport, which lets a remote client control a Claude Code session, gained a new `onCancelAsyncMessage` handler. It lets a remote client cancel a message it previously sent asynchronously (in the background) by removing it from the queue by its ID, or by withdrawing it before it's processed.\n\n**Why**\n\nBefore this, a remote client could interrupt an active turn but had no way to take back a background message it had already queued. Now it can cancel a queued message directly.\n\n- Area: Remote Control\n- Names: `onCancelAsyncMessage`\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 2\/5"}