What /rewind misses: a measured test
Last updated: 7 October 2026
In a test on 7 October 2026 with Claude Code 2.1.292, /rewind restored the Write edit and none of the four shell commands: rm, mv, sed -i and npm install. That is what the checkpointing documentation says it does: "Checkpointing does not track files modified by Bash commands." (checkpointing). Each command ran in its own fresh project, once for /rewind and once for /turnslip:undo:
rm notes/old.txt: /rewind did not restore it; /turnslip:undo did.mv src/config.js src/settings.js: /rewind did not restore it; /turnslip:undo did.sed -i 's/3000/8080/' src/config.js: /rewind did not restore it; /turnslip:undo did.npm install is-number: /rewind did not restore it; /turnslip:undo restored package.json and removed package-lock.json, and left node_modules.- A Write tool edit of
README.md: both restored it.
Method
Claude Code 2.1.292 with Opus 5.5 on Windows 11, interactive, with permission prompts switched off and turnslip 0.3.7 loaded; the mv run for /turnslip:undo was repeated with turnslip 0.3.8 (see below). Ten fresh projects, none of them a git repository, each holding the same four files: README.md, package.json, src/config.js (export const PORT = 3000) and notes/old.txt. One prompt per project, asking for one command and nothing else, or for a Write tool edit of README.md. That is one run per command for each way back, so a sample of one each.
After the turn, in five of the projects: /rewind, the turn's prompt, then Restore code where the menu offered it and Restore conversation where it did not. In the other five: /turnslip:undo. Then the files on disk were listed. Every result on this page is what was on disk afterwards, captured in the run, not taken from the documentation.
What the rewind menu showed
For every shell turn the menu listed the prompt with "No code changes", and its confirm screen said "The code will be unchanged." and offered no code option. The documentation describes this: "The two code restore options appear only when the selected checkpoint has tracked file changes to revert." (rewind and summarize).
For the Write turn the list showed "README.md +1 -3", and the confirm screen offered Restore code with a warning underneath: "⚠ Rewinding does not affect files edited manually or via bash." Restore code put README.md back.
Two details from the run. Claude Code drew the sed -i call as Update(src\config.js), the way it draws a file edit, and the menu still said "No code changes": the port stayed 8080. On Windows, Claude ran the install through its PowerShell tool, PowerShell(npm install is-number), and rewind did not restore that either. The documentation's own example names rm, mv and cp, and says: "These file modifications cannot be undone through rewind. Only direct file edits made through Claude's file editing tools are tracked."
Without turnslip
Commit before a request that runs shell commands. The checkpointing documentation puts it this way: "Checkpoints are designed for quick, session-level recovery. For permanent version history and collaboration, continue using version control, such as Git, for commits, branches, and long-term history." (not a replacement for version control).
To make Claude Code ask before the destructive commands: Stop Claude Code from running rm -rf and git reset --hard. If files are already gone: Claude Code deleted my files: what can still come back.
What /turnslip:undo did
turnslip snapshots the project's files and compares them at the end of each turn (its README), so its undo does not depend on which tool made the change. In the same test it restored the rm, the mv, the sed -i and the Write edit in full, and the npm install in part:
mv: with turnslip 0.3.7 the undo broughtsrc/config.jsback but keptsrc/settings.js, because a renamed file keeps its creation time and undo removed only files created after the turn started. turnslip 0.3.8, fixed after this test, removes the new name when its content is exactly what undo writes back; the repeated run printed "restored 1 file, removed 1" and left onlysrc/config.js.npm install: it restoredpackage.json, removed the newpackage-lock.json, and leftnode_modules, which turnslip never tracks, whatever your.gitignoresays (gitignore.mjs). The line names the command under "not undone".
Limits of this test
- One run per command, on one Windows 11 machine, with one model and one Claude Code version. Another version may behave differently; the date and version are at the top for that reason.
- turnslip helps only if it was installed before the turn. It leaves out what your
.gitignoreexcludes, and the free version undoes the last turn; undoing an earlier one is part of Pro.
Related: How to undo Claude Code changes · All guides · Install turnslip, free