{"version":"2.1.296","anchor":"rewind-refusal-now-distinguishes-a-running-turn-turn-runnin","canonical_anchor":"rewind-refusal-now-distinguishes-a-running-turn-turn-runnin","heading":"Rewind requests are refused while a usage-limited turn is still running","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/rewind-refusal-now-distinguishes-a-running-turn-turn-runnin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Rewind requests are refused while a usage-limited turn is still running\n\nWith `refuse_if_usage_limited`, a `rewind_conversation` request now gets a separate `turn_running` refusal if a turn is still running\n\n**What**\n\nWhen a `rewind_conversation` request uses `refuse_if_usage_limited`, Claude Code now also checks whether the current turn is still running or about to end. If a turn is still running, it refuses the rewind with a `turn_running` result. Before, the check could only end the turn or let the rewind go ahead.\n\n**Why**\n\nA program asking to rewind during a running turn under a usage limit now gets a clear refusal, instead of the rewind racing with the turn.\n\n- Area: Sessions\n- Names: `refuse_if_usage_limited`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}