{"version":"2.1.293","anchor":"rewind-refusal-with-missing-target-when-usage-limited","canonical_anchor":"rewind-refusal-with-missing-target-when-usage-limited","heading":"Rewind requests can report a missing target when usage limits are reached","tier":"notice","area":"Agents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/rewind-refusal-with-missing-target-when-usage-limited","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Rewind requests can report a missing target when usage limits are reached\n\n`rewind_conversation` accepts `refuse_missing_target_if_usage_limited`, and wrongly refuses fewer rewinds over later turns\n\n**What**\n\nThe `rewind_conversation` request, which programs driving Claude Code use to take a conversation back to an earlier message, has two changes:\n\n- It accepts a further option, `refuse_missing_target_if_usage_limited`, and the `usage_limited` reply can now include `target_not_found`, saying the message to rewind to was not found.\n\n- When checking for later turns it has not seen, rewind now compares turns by their text, so it refuses fewer rewinds by mistake.\n\n**Why**\n\nPrograms driving Claude Code get a clearer answer when a rewind is refused, and fewer rewinds are wrongly blocked.\n\n- Area: Agents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}