{"version":"2.1.319","anchor":"file-history-first-backup-parent-directory-anchoring-behind","canonical_anchor":"file-history-first-backup-parent-directory-anchoring-behind","heading":"Safer first backups of files for rewinding edits","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/file-history-first-backup-parent-directory-anchoring-behind","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Safer first backups of files for rewinding edits\n\nClaude Code can now abort and clean up a file's first backup if its parent folder changes partway through, behind a remote switch\n\n**What**\n\nClaude Code keeps backups of files it edits so you can undo changes with `\/rewind`. When it makes the first backup of a file, it can now record the real folder the file sits in and that folder's identity. Then:\n\n- If the folder changes while the backup is being taken, the backup is aborted and the partial copy is removed.\n\n- If a folder above the file is a broken shortcut (a symlink that points at nothing), the backup is refused.\n\nA new message can appear when you try to restore too soon: \"The file backups are still being copied. Nothing was changed. Try again in a moment.\"\n\nThis behaviour is controlled by a switch the server can turn on.\n\n**Why**\n\nIt closes a gap where a folder swapped in at the wrong moment could send a backup to the wrong place. When the check is active, a backup that would have been unsafe is recorded as a failure instead.\n\n- Area: Sessions\n- Names: `\/rewind`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}