{"version":"2.1.307","anchor":"transcript-fold-copy-holding-in-persistence","canonical_anchor":"transcript-fold-copy-holding-in-persistence","heading":"Session transcripts can hold back copies of queued messages until they are settled","tier":"internal","area":"Session Transcripts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/transcript-fold-copy-holding-in-persistence","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Session transcripts can hold back copies of queued messages until they are settled\n\nThe session transcript writer can now hold copies of queued messages until it decides to keep or drop them, and settles them before compaction\n\n**What**\n\nClaude Code keeps a transcript of each session, a saved record of the conversation. The part that writes it now works with the queue of messages waiting to be sent. Copies of those queued messages can be held back instead of written straight away, until Claude Code decides whether each one should keep waiting, be dropped or be written. Any held copies are settled before compaction, the step where Claude Code shortens a long conversation to save space.\n\n**Why**\n\nThis can stop the same queued message from being written to the transcript twice.\n\n- Area: Session Transcripts\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}