{"version":"2.1.323","anchor":"transcript-fsync-after-rewriterename-and-a-shared-flush-hel","canonical_anchor":"transcript-fsync-after-rewriterename-and-a-shared-flush-hel","heading":"Session transcripts are saved more safely after being rewritten","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/transcript-fsync-after-rewriterename-and-a-shared-flush-hel","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Session transcripts are saved more safely after being rewritten\n\nClaude Code now makes sure a rewritten or renamed transcript is fully written to disk, so it is less likely to be lost in a crash\n\n**What**\n\nA transcript is the file where Claude Code saves a session's conversation. After Claude Code rewrites or renames a transcript file or its folder, it now tells the system to write the change all the way to disk. How it handles a failure to save pending writes is also now done in one shared way.\n\n**Why**\n\nTranscripts are less likely to be lost or damaged if your computer crashes or loses power right after a save.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}