{"version":"2.1.281","anchor":"filesystem-abstraction-placecreated-with-no-replace-rename","canonical_anchor":"filesystem-abstraction-placecreated-with-no-replace-rename","heading":"Filesystem abstraction: placeCreated with no-replace rename","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/filesystem-abstraction-placecreated-with-no-replace-rename","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Filesystem abstraction: placeCreated with no-replace rename\n\nClaude Code's internal file layer can now move a newly created file into place without overwriting an existing one\n\n**Unclear.** The finding does not say which Claude Code features use `placeCreated`.\n\n**What**\n\nClaude Code has an internal layer it uses to read and write files. That layer gains `placeCreated`, which moves a newly created file to its final name with a rename that refuses to replace a file already there (`renameNoReplace`). When that kind of rename is not available, it falls back to creating a link instead.\n\nTwo smaller changes: reading a file's details (`lstat`) and checking whether a file exists now both go through a file-system object that can be swapped out.\n\n**Why**\n\nA move that refuses to overwrite means a file placed this way cannot silently replace one that is already at the same path."}