Checkpoints & rewind

Every time Claude edits your files, it quietly records a checkpoint. If a change made things worse, you can rewind to a known-good moment without losing the rest of the conversation. It's a safety net that lives *inside* the session — separate from, and faster than, undoing things by hand.

Every time Claude edits your files, it quietly records where things stood just before. You don’t set anything up; the safety net is simply there. When a change makes things worse — a layout breaks, a refactor goes sideways — you say so, and the files snap back to the last good moment.

The part that surprises people: rewinding restores your files without throwing away the conversation. You keep everything you’ve discussed and learned; you just undo the edits. That’s what makes it safe to experiment boldly on a hard task — there’s always a clean way back that doesn’t cost you the context you built up.

Think of it as session-level undo, and git as your durable, shareable undo — use both. Checkpoints are fast and live inside the session, perfect for “try it and see”; git is what you reach for once a change is good and you want it recorded for keeps. It’s the natural companion to plan mode: plan to avoid the wrong turn, checkpoint to recover quickly when one slips through anyway.

That last change broke the layout — rewind to before it.