{"version":"2.1.295","anchor":"a-transcript-dedupe-set-can-carry-record-hashes-forward-to-a","canonical_anchor":"a-transcript-dedupe-set-can-carry-record-hashes-forward-to-a","heading":"Duplicate tracking for conversation records can carry over","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/a-transcript-dedupe-set-can-carry-record-hashes-forward-to-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Duplicate tracking for conversation records can carry over\n\nThe list Claude Code keeps to avoid duplicate conversation records now tracks more entries and can be passed on to a successor\n\n**What**\n\nClaude Code keeps track of which entries it has already written to a conversation record (transcript), so it does not write them twice. That tracking now covers a second set of entries, and it can be handed on to a fresh copy that keeps some of what the old one knew.\n\n**Why**\n\nThis likely affects how duplicate entries are avoided when a conversation is branched or resumed.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}