{"version":"2.1.310","anchor":"inbound-attachments-written-without-clobbering-existing-file","canonical_anchor":"inbound-attachments-written-without-clobbering-existing-file","heading":"Saving incoming attachments no longer overwrites files already there","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/inbound-attachments-written-without-clobbering-existing-file","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Saving incoming attachments no longer overwrites files already there\n\nIncoming attachments are now saved without replacing files of the same name, and names held by links, pipes or folders are left alone\n\n**What**\n\nWhen Claude Code saves an attachment sent to it, it no longer simply writes over whatever has that name. It now:\n\n- writes the file only if nothing with that name exists yet, or prepares it separately and then puts it in place\n\n- compares contents when a file with that name is already there, and keeps the existing file when its content differs\n\n- refuses to save when the name belongs to something that is not an ordinary file, such as a link, a pipe or a folder, and says it was left as it is\n\nBefore, saving overwrote whatever was at that path.\n\n**Why**\n\nYour own files in the uploads folder are no longer replaced by an incoming attachment that happens to share their name.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}