{"version":"2.1.287","anchor":"interrupt-gains-send-now-and-message-uuid-fields","canonical_anchor":"interrupt-gains-send-now-and-message-uuid-fields","heading":"Interrupt requests can push a queued message through instead of stopping the turn","tier":"notice","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/interrupt-gains-send-now-and-message-uuid-fields","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Interrupt requests can push a queued message through instead of stopping the turn\n\nInterrupt requests gain internal `send_now` and `message_uuid` fields so a queued message can reach the model without stopping the session\n\n**Unclear.** It is not clear whether anything in this release acts on the new `send_now` field yet.\n\n**What**\n\nPrograms and remote apps that drive Claude Code can send an interrupt request to stop what Claude is doing. That request can now do something else instead:\n\n- New fields: the interrupt request gains two internal fields. `send_now` asks that waiting messages from you reach the model now, either by moving the blocking work to the background or by stopping the turn. `message_uuid` names the queued message that was pressed.\n\n- Advertised: support is announced by the `interrupt_send_now_v1` capability in the `system\/init` message.\n\n- Handling: when Claude Code runs without its own screen and gets an interrupt naming a pressed queued message, it now pushes that message through instead of stopping the turn.\n\n- Combining requests: when two interrupt requests are merged, `send_now` is kept only if the earlier one set it, `message_uuid` is kept only when both refer to the same message, and `cancel_queued` is carried through as before.\n\n- Recognition: a request counts as send-now when `send_now` is true and `cancel_queued` is not.\n\n- Removed: the old paths that answered an interrupt early during a file download, and a turn handoff early, are gone. Messages are now held until the start or result message has been written (`writeAfterInit`).\n\n**Why**\n\nThis makes a \"send now\" action possible in remote apps and SDK hosts: a message you queued can reach Claude mid-turn without ending the session.\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}