{"version":"2.1.311","anchor":"rewind-restore-warning-text","canonical_anchor":"rewind-restore-warning-text","heading":"Warning text for restoring files from a checkpoint","tier":"notice","area":"Checkpoints","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/rewind-restore-warning-text","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Warning text for restoring files from a checkpoint\n\nA warning says restored files go back whole, losing later changes, and that Bash changes to other files are not undone\n\n**What**\n\nClaude Code has a new warning for restoring files to an earlier checkpoint (a saved point in the session you can rewind to). It reads: \"Restored files go back whole, losing later changes by anyone. Bash changes to other files are not undone.\"\n\n**Why**\n\nThe warning belongs to the checkpoint restore screen. A restore replaces each file completely, so edits made after the checkpoint are lost, whoever made them. Files changed by shell commands that Claude ran through Bash stay as they are.\n\n- Area: Checkpoints\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}