{"version":"2.1.290","anchor":"rate-limit-pre-check-before-rewinding-rewind-limit-question","canonical_anchor":"rate-limit-pre-check-before-rewinding-rewind-limit-question","heading":"Usage-limit check before rewinding a conversation","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/rate-limit-pre-check-before-rewinding-rewind-limit-question","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Usage-limit check before rewinding a conversation\n\nClaude Code has code to ask the server whether a request would hit a usage limit before rewinding\n\n**Unclear.** Nothing showing where this check is called or what switches it on was found, so it may not run yet.\n\n**What**\n\nRewinding means going back to an earlier point in a conversation. Claude Code now has code that, before a rewind, asks the server whether a request would be accepted. If the server refuses, Claude Code sorts the refusal into one of several kinds.\n\nThe check is skipped for:\n\n- connections that do not go directly to Anthropic\n\n- low-priority sessions\n\n- sessions that are busy\n\n- sessions being watched for retries\n\nOnly a refusal tied to the five-hour or seven-day usage limit produces a report. Every other answer lets the rewind go on.\n\n**Why**\n\nA rewind could avoid sending a request that would only run into your usage limit.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}