Claude Code /rewind didn't undo everything? What checkpoints don't track
Ship ItChecked against the official source
Source checked 10 Oct 2026 · Published 23 Oct 2026 · Last reviewed 23 Oct 2026 · By Ctrl+Z Therapy (how we test)
The short answer
Claude Code checkpoints its own file edits, so you can rewind them. But its docs say "Checkpointing does not track files modified by Bash commands", like rm, mv and cp, and "These file modifications cannot be undone through rewind". Only direct edits made through Claude's file editing tools are tracked. The docs say checkpoints are for quick, session-level recovery: for permanent version history, keep using version control such as Git.
What to do
- To go back, run /rewind, or press Esc twice when the prompt input is empty.
- Know what rewind skips: files changed by Bash commands like rm, mv and cp, and most subagent edits.
- Commit to Git before anything risky, so you always have a real copy to go back to.
- Ask your AI tool: "Before you run any command that deletes, moves or overwrites files, stop and tell me, and commit the current state to Git first so I can always go back."
Good to know
- Changes you make outside Claude Code, and edits from other sessions running at the same time, are normally not captured either.
Source
Checked on 10 Oct 2026. Prices, limits and settings change, so check the source before you rely on them.