{"version":"2.1.291","anchor":"transcript-compact-and-tombstone-removal-no-longer-take-a-pe","canonical_anchor":"transcript-compact-and-tombstone-removal-no-longer-take-a-pe","heading":"Shrinking a transcript and removing messages from it skip an opening wait","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.291\/e\/transcript-compact-and-tombstone-removal-no-longer-take-a-pe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.291","markdown":"### Shrinking a transcript and removing messages from it skip an opening wait\n\nCompacting a session transcript and deleting messages from it no longer start by waiting on the file, which may have been a lock\n\n**Unclear.** It is not clear whether the removed step actually locked the file or did nothing at all.\n\n**What**\n\nClaude Code can rewrite a session's transcript file to make it smaller, called compacting. It can also mark individual messages in it as removed. Both operations used to begin by waiting on the file. That step is gone, and both now start their work straight away.\n\nCompacting still checks whether the file changed underneath it, or was caught partway through a line, before it finishes. Message removal still refuses to run on a session file that is too large.\n\n**Why**\n\nIf the removed step was a lock, other writes to the same transcript could now overlap with compacting or message removal. The checks that remain may be what guards against that now.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}