What /rewind Can't Undo
Mid-session, Claude runs rm old-config.json via Bash to clean up,
then makes several more changes to other files using the Edit tool.
You open /rewind and restore code back to before all of this.
What happens to old-config.json?
The correct answer is "It stays deleted — /rewind doesn't track Bash side effects."
Checkpointing only captures file state changed through Claude's own
Edit and Write tools. A shell command that touches the filesystem —
rm, mv, or anything else run via Bash — is invisible to /rewind
entirely; only edits made through Claude's own editing tools are
tracked and reversible. A deleted file via rm is gone as far as
/rewind is concerned, and getting it back requires git or a backup,
not the rewind menu.
The distractors misdescribe the mechanism: rewind doesn't restore
Bash-deleted files alongside the Edit-tool changes it does track; it
doesn't block dangerous Bash commands from running in the first
place; and whether the file happened to be tracked in git doesn't
change what /rewind itself is able to restore.
Share this question