{"version":"2.1.288","anchor":"transcript-writes-now-serialize-behind-the-previous-write","canonical_anchor":"transcript-writes-now-serialize-behind-the-previous-write","heading":"Conversation history is now saved one write at a time","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/transcript-writes-now-serialize-behind-the-previous-write","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Conversation history is now saved one write at a time\n\nClaude Code now waits for one save of the conversation history to finish before the next, so overlapping saves can't split it\n\n**Unclear.** What a split history looked like to someone using Claude Code is not known.\n\n**What**\n\nClaude Code saves a running record of each conversation, which is what lets you resume it later. If a new update to that record arrives while an earlier save is still in progress, Claude Code now queues it and writes it once the earlier save finishes. Previously each save started straight away. Updates that end at a compaction point (where older messages were replaced by a summary) are skipped. Claude Code also records usage data on how long saves take, how many updates were overtaken and whether it waited at exit.\n\n**Why**\n\nOverlapping saves could split the saved conversation into two branches. Saving in order stops that from happening.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}