{"version":"2.1.293","anchor":"context-edit-check-can-report-whether-the-missing-target-was","canonical_anchor":"context-edit-check-can-report-whether-the-missing-target-was","heading":"Rewind can now report that the point you asked for was not found","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/context-edit-check-can-report-whether-the-missing-target-was","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Rewind can now report that the point you asked for was not found\n\nWhen a rewind target is missing and was asked for, Claude Code now reports that the target was not found\n\n**Unclear.** It is not clear which rewind action a reader takes that leads to this new not-found result, or what they see when it happens.\n\n**What**\n\nThe check that runs before a rewind or cut of the conversation history now returns a result saying whether the target was found. When the target cannot be found and it was specifically asked for, the check now reports that the target was not found. Before, this check could only answer that the rewind could go ahead or that it was skipped because there was nothing to cut.\n\n**Why**\n\nA missing target can now be told apart from the case where there was simply nothing to cut.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}