{"version":"2.1.296","anchor":"resume-detects-interrupted-turns-by-assistant-message-id","canonical_anchor":"resume-detects-interrupted-turns-by-assistant-message-id","heading":"Resuming a session judges unfinished turns differently","tier":"notice","area":"Resume","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/resume-detects-interrupted-turns-by-assistant-message-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Resuming a session judges unfinished turns differently\n\nOn resume, Claude Code now traces back through the transcript by response, so some turns it used to call interrupted now count as complete\n\n**Unclear.** Which interrupted turns now count as complete is not spelled out.\n\n**What**\n\nWhen you resume a session (pick up an earlier conversation), Claude Code checks whether the last turn was cut off partway. A session's transcript is its saved record of the conversation. To decide, Claude Code now walks back through the transcript and groups entries by the response they belong to. As a result, some turns it used to treat as interrupted are now treated as complete.\n\nThe lookup that finds the prompt behind a turn can now also use a summarized version of that prompt.\n\n**Why**\n\nThis can change which resumed sessions carry on by themselves and which wait for you.\n\n- Area: Resume\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}