How to undo in Claude Code

Claude Code has real undo machinery built in. Knowing exactly where it stops is the difference between a thirty-second fix and a lost week.

1. Rewind to a checkpoint

Claude Code snapshots your files as it works. Press Escape twice (or use the /rewind command) to open the rewind menu, pick the point before things went wrong, and choose whether to restore the code, the conversation, or both. This is the fastest undo and handles most mid-session accidents.

Limit: checkpoints are a working convenience tied to your recent sessions on that machine. They're not a permanent archive of the project, and they only cover changes Claude made, not edits from other tools or your own hand-edits.

2. Ask before it acts

Half of undo is not needing it. Claude Code asks permission before file edits by default; read those prompts on risky operations instead of reflex-approving. For a big restructuring, say "make a checkpoint of everything first", so rewind has somewhere good to return to.

3. When the damage predates the session

"It worked on Tuesday" needs history that outlives sessions. If the project has a home with a timeline, open it, find Tuesday, restore. If it doesn't, this is the moment people discover the difference between a checkpoint and an archive, usually expensively.

Project-wide undo in two minutes

Plyo gives the project a permanent timeline that Claude Code maintains itself:

(The key comes from your free Plyo account: Settings → AI keys.) Every saved state becomes a restorable version with a plain-English note, off your machine, visible in a browser, one click to restore from any session (or any tool) forever after.