{"version":"2.1.295","anchor":"transcript-tombstone-removal-repairs-the-replay-index-on-fai","canonical_anchor":"transcript-tombstone-removal-repairs-the-replay-index-on-fai","heading":"Removing a message from a transcript now recovers from failed writes","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/transcript-tombstone-removal-repairs-the-replay-index-on-fai","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Removing a message from a transcript now recovers from failed writes\n\nIf removing a message from a session file fails partway, Claude Code now rebuilds its in-memory index instead of ignoring the error\n\n**What**\n\nClaude Code saves each session (one conversation) to a transcript file on disk and keeps an index of it in memory for replaying it later. When a message is removed from that file, Claude Code now checks whether the write was cut short. If the write fails or is incomplete, it rebuilds the index. Before, such errors were silently ignored.\n\n**Why**\n\nThis stops the in-memory index from going out of step with the file after a removal only partly succeeds.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}