{"version":"2.1.307","anchor":"interrupt-can-requeue-a-prompt-new-internal-field-requeue-i","canonical_anchor":"interrupt-can-requeue-a-prompt-new-internal-field-requeue-i","heading":"Programs driving Claude Code can ask for an interrupted prompt to be requeued","tier":"use","area":"Agents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/interrupt-can-requeue-a-prompt-new-internal-field-requeue-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Programs driving Claude Code can ask for an interrupted prompt to be requeued\n\nA new internal option asks Claude Code to put a prompt back in its queue if an interrupt arrives just as the prompt is being picked up\n\n**What**\n\nThe SDK is the toolkit other programs use to drive Claude Code. Messages sent through it can now carry an internal option, `requeue_if_interrupted_within_ms`. It asks Claude Code to put a prompt back in its queue if an interrupt arrives at the same moment the prompt is being taken in.\n\nClaude Code ignores the option unless it announces `interrupt_requeue_taken_v1` in the `system\/init` message it sends at startup.\n\n**Why**\n\nIn remote or host-driven sessions, a prompt that collides with an interrupt is less likely to be lost.\n\n- Area: Agents\n- Names: `requeue_if_interrupted_within_ms`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}