{"version":"2.1.300","anchor":"rewind-target-can-fall-back-to-an-assistant-message","canonical_anchor":"rewind-target-can-fall-back-to-an-assistant-message","heading":"Rewind can land on an assistant message and clears its own queued rerun","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/rewind-target-can-fall-back-to-an-assistant-message","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Rewind can land on an assistant message and clears its own queued rerun\n\nRewind can fall back to an assistant message, and it removes queued prompts and saved MCP task endings left by the rewound turn\n\n**Unclear.** It is not clear whether any rewind action in this release actually switches the new option on.\n\n**What**\n\nRewind takes a conversation back to an earlier message. Two changes affect it:\n\n- The lookup that finds where to rewind to takes a new `allowAssistantTarget` option. When no message you sent matches, it can now return one of Claude's replies (an assistant message) instead. Before, it returned only a message you sent, or nothing.\n\n- New helpers clean up what the rewound turn left in the message queue, the list of prompts waiting to run. One withdraws saved endings of MCP tasks (long jobs run by tools connected through the Model Context Protocol). Another removes queued prompt commands that the rewound turn itself produced, depending on a switch. When it declines, it records why: `not_a_prompt`, `opener_unknown`, `turn_unseen`, `answers_for_others`, `others_queued`, `no_cut`, or `switch_<state>`.\n\n**Why**\n\nA turn you rewind away from should not run again from the queue afterwards. Where the option is used, a rewind can also land on one of Claude's replies rather than only on your own messages.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}