{"version":"2.1.321","anchor":"transcript-storage-nfs-flush-detection-and-tolerant-replay","canonical_anchor":"transcript-storage-nfs-flush-detection-and-tolerant-replay","heading":"Saved conversation records hold up better on network drives and low memory","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/transcript-storage-nfs-flush-detection-and-tolerant-replay","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Saved conversation records hold up better on network drives and low memory\n\nClaude Code now detects NFS transcript folders, tolerates unreadable transcript lines, and limits retries on a full disk\n\n**What**\n\nClaude Code saves each conversation to a transcript file so it can be reopened later. Several things about how it stores these files have changed:\n\n- On Linux and WSL, it checks whether the transcript folder is on NFS, a kind of network drive, and logs whether new lines are written straight to disk.\n\n- When rebuilding its index of a transcript, it now skips lines it cannot read and logs that this is probably for lack of memory.\n\n- Writing to a full disk is retried only a limited number of times.\n\n**Why**\n\nSaved conversations are less likely to break on network drives or on machines short of memory.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}