{"version":"2.1.318","anchor":"atomic-file-write-ebusy-retry-on-nfs-and-safer-in-place-fal","canonical_anchor":"atomic-file-write-ebusy-retry-on-nfs-and-safer-in-place-fal","heading":"Safer file saving on network drives and when another program changes the file","tier":"notice","area":"File Writes","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/atomic-file-write-ebusy-retry-on-nfs-and-safer-in-place-fal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Safer file saving on network drives and when another program changes the file\n\nSaving a file now retries once when an NFS network drive reports the file as busy, and no longer clobbers a file another program has replaced\n\n**What**\n\nClaude Code saves some files in two steps. It first writes a temporary copy, then swaps it in place of the original. Two parts of that process are different now:\n\n- Busy files on NFS: if the swap fails, Claude Code retries it once. NFS is a way of sharing folders over a network.\n\n- Fallback writing: when Claude Code falls back to writing straight into the existing file, it now checks whether another program has replaced that file in the meantime. If it has, Claude Code leaves the file as it is, and the error message says another writer replaced it.\n\nBefore, the fallback deleted the target file, and the error always said the file had been truncated, meaning emptied.\n\n**Why**\n\nFewer saves should be lost or overwritten when you work in a network folder or when another program writes to the same file at the same time.\n\n- Area: File Writes\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}