{"version":"2.1.317","anchor":"rewind-transcript-leaf-selection-handles-trailing-file-snap","canonical_anchor":"rewind-transcript-leaf-selection-handles-trailing-file-snap","heading":"Resume no longer lands on a file snapshot at the end of a transcript","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/rewind-transcript-leaf-selection-handles-trailing-file-snap","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Resume no longer lands on a file snapshot at the end of a transcript\n\nWhen a saved conversation ends in file snapshots after the last message, Claude Code no longer treats a snapshot as the point to resume from\n\n**What**\n\nClaude Code saves each conversation as a transcript, a running record of messages. It also stores file snapshots there, which let you rewind your files to an earlier point. When you resume, Claude Code picks the latest point in that record to continue from.\n\nBefore, that choice ignored whether the last rows were snapshots. Now Claude Code counts snapshot rows that come after the last real message and no longer picks the very last row when only snapshots follow it. It also records in its usage data when a transcript ends this way. Sessions that were rewound get an extra check on which point to continue from.\n\n**Why**\n\nThis should stop resumes after a rewind from continuing from the wrong place in the conversation.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}