{"version":"2.1.314","anchor":"transcript-parent-chain-timestamp-fallback-made-faster-com","canonical_anchor":"transcript-parent-chain-timestamp-fallback-made-faster-com","heading":"Faster repair of broken conversation histories, and compaction keeps later messages","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/transcript-parent-chain-timestamp-fallback-made-faster-com","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Faster repair of broken conversation histories, and compaction keeps later messages\n\nRepairing a broken saved conversation is faster, and compaction can keep messages dated after the point where it summarised\n\n**What**\n\nClaude Code saves each conversation as a transcript, a file where every message points back to the one before it. When those links are broken, Claude Code falls back to ordering messages by their timestamps. That fallback used to scan the whole transcript every time. It now uses a sorted index, which is much quicker on long transcripts.\n\nCompaction is the step that shrinks a long conversation by replacing older messages with a summary. It now records the time at which it drew that line. In some cases it then keeps any messages dated after that time instead of pruning them.\n\n**Why**\n\nResuming a very large or damaged conversation should be faster. Messages written after a compaction are also less likely to be lost.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}