{"version":"2.1.319","anchor":"document-save-refuses-to-overwrite-files-with-no-save-record","canonical_anchor":"document-save-refuses-to-overwrite-files-with-no-save-record","heading":"Saving documents no longer overwrites files it did not write itself","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/document-save-refuses-to-overwrite-files-with-no-save-record","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Saving documents no longer overwrites files it did not write itself\n\nWhen saving documents to a folder, Claude Code now leaves alone any existing file that has no record of an earlier save, and asks for another `out_dir`\n\n**Unclear.** It is not clear whether documents that other people may have written are still kept from being saved to files.\n\n**What**\n\nThe tool that saves documents to files in a folder has a new refusal reason, `existing_file`. It applies to files that are already in the target folder and carry no record of being written by an earlier save. Older versions of Claude Code left no such record, so files from those versions count too.\n\nThose files are left untouched. The message tells you to pass a different `out_dir`, the setting that names the folder to save into.\n\nThe fixed message saying that documents other people may have written are not saved to files is gone from this place.\n\n**Why**\n\nFiles you already have in a folder are protected from being silently replaced. It also changes which documents end up written to disk, so a save into a folder you have used before may now be refused until you pick a new one.\n\n- Area: Elsewhere\n- Names: `existing_file`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}