{"version":"2.1.277","anchor":"new-cancel-async-message-bridge-control-request","canonical_anchor":"new-cancel-async-message-bridge-control-request","heading":"New cancel_async_message bridge control request","tier":"use","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/new-cancel-async-message-bridge-control-request","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### New cancel_async_message bridge control request\n\nA new cancel_async_message control request lets a bridge client cancel one queued message by its ID\n\n**What**\n\nA new control request called `cancel_async_message` lets a connected bridge client cancel a message it previously sent and queued for later processing, by specifying that message's `message_uuid`. Claude Code checks that the ID is valid and that a callback is registered for it, then reports back whether the cancellation succeeded or failed.\n\n**Why**\n\nThis gives a client a way to withdraw one specific queued message on its own, rather than only being able to cancel everything queued at once. If the message can't be found or was already handled, the request reports failure instead of doing nothing silently.\n\n- Area: Remote Control\n- Names: `cancel_async_message`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}