{"version":"2.1.300","anchor":"rewind-allowassistanttarget-and-interrupt-if-running-option","canonical_anchor":"rewind-allowassistanttarget-and-interrupt-if-running-option","heading":"Rewind requests can target assistant messages and interrupt a running turn","tier":"use","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/rewind-allowassistanttarget-and-interrupt-if-running-option","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Rewind requests can target assistant messages and interrupt a running turn\n\nrewind_conversation accepts allow_assistant_target to rewind to one of Claude's replies and interrupt_if_running to rewind mid-turn\n\n**What**\n\nThe `rewind_conversation` request, which programs driving Claude Code send to take a conversation back to an earlier message, accepts two more options:\n\n- `allow_assistant_target` lets a rewind land on one of Claude's replies (an assistant message). The step that works out where to cut the conversation gained the matching `allowAssistantTarget` option and marks the cut with an `assistantTarget` flag. When a rewind is refused, the reason now also says whether the target was an assistant message.\n\n- `interrupt_if_running` interrupts a turn that is still running so the rewind can go ahead.\n\nBefore, only `allow_summarized_target` and `refuse_if_usage_limited` were handled.\n\n**Why**\n\nPrograms built on Claude Code can rewind to Claude's own replies, not only to messages the user sent, and can rewind while Claude is still working instead of waiting for the turn to end.\n\n- Area: SDK\n- Names: `rewind_conversation`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}