Claude Certified Architect – Foundations Practice Question 75: Checkpoint Rewind Limits
Claude Certified Architect, Foundations · Test 8 · question 5 of 10
During a Claude Code session, Claude edited several source files with its file editing tools and then ran "rm old-config.json" through the Bash tool. The developer dislikes the whole direction and wants to go back to how things were before that prompt. What happens if they press Esc twice (or run /rewind), pick that earlier prompt and choose "Restore code and conversation"?
Show answer and explanation
Answer:
Claude Code checkpoints the state of code touched by its file editing tools before each prompt. Rewinding (Esc twice on an empty input, or /rewind) offers to restore code, conversation, or both. A documented limitation is that files changed by Bash commands (rm, mv, cp) are not tracked, so those changes cannot be undone by rewind. Checkpoints are session-level recovery, not a replacement for version control.
- B is wrong: checkpoints do not snapshot the whole directory; they track edits made through file editing tools. - C is wrong: code restore is a core rewind option ("Restore code" and "Restore code and conversation"). - D is wrong: checkpointing is automatic; --fork-session is for branching a session and is unrelated to enabling snapshots.
Reference: Checkpointing