{"version":"2.1.287","anchor":"transcript-gc-rewind-cut-computed-from-last-boundary","canonical_anchor":"transcript-gc-rewind-cut-computed-from-last-boundary","heading":"Rewinding works from the last boundary when transcript cleanup is on","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/transcript-gc-rewind-cut-computed-from-last-boundary","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Rewinding works from the last boundary when transcript cleanup is on\n\nWith transcript cleanup on, Claude Code works out where to rewind using only messages after the last boundary\n\n**Unclear.** What turns the transcript cleanup option on is not known.\n\n**What**\n\nRewinding takes a conversation back to an earlier point. When an option for transcript cleanup is on, Claude Code now works out the rewind point using only the messages after the last boundary in the transcript, then maps that point back to its place in the full list. Transcript cleanup removes older material from the saved conversation. Before, the whole message list was always used.\n\n**Why**\n\nRewinding keeps working after older parts of the transcript have been cleaned up.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}