{"version":"2.1.296","anchor":"rewind-limit-question-waits-for-an-ending-run","canonical_anchor":"rewind-limit-question-waits-for-an-ending-run","heading":"Rewind in remote sessions waits for a finishing turn before answering","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/rewind-limit-question-waits-for-an-ending-run","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Rewind in remote sessions waits for a finishing turn before answering\n\nWhen a remote rewind is refused over a turn that is finishing, Claude Code now waits for it and reports the turn as still running if it does not end\n\n**Unclear.** It is not clear what you see differently when you rewind in a remote session.\n\n**What**\n\nRewinding takes a conversation back to an earlier point. In remote sessions there is a guard on how far back you can go. When that guard refuses and the point you picked is during a turn that is just ending, Claude Code now waits for the turn to finish. If it does not finish in time, the answer is that a turn is still running. Claude Code also checks the state again afterwards. Before, there was a single recheck only.\n\n**Why**\n\nThis fixes a timing problem in the remote rewind guard, where the answer could depend on whether a turn happened to finish at that moment.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}