{"version":"2.1.295","anchor":"interrupted-turn-resume-sets-a-carry-over-flag","canonical_anchor":"interrupted-turn-resume-sets-a-carry-over-flag","heading":"Resumed interrupted turns are now marked as continuing the cut-off turn","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/interrupted-turn-resume-sets-a-carry-over-flag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Resumed interrupted turns are now marked as continuing the cut-off turn\n\nWhen Claude Code resumes a turn that was cut off, it now marks the resumed request as carrying that turn forward\n\n**Unclear.** It is not stated what Claude Code does differently once a resumed turn is marked this way.\n\n**What**\n\nA turn is one round of you asking and Claude Code answering. When a turn is cut off partway and then resumed, Claude Code now marks the resumed request as carrying the cut-off turn forward before it builds the prompt.\n\n**Why**\n\nThis affects how a turn interrupted midway is picked up again, particularly in remote sessions.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}