Introduction

Checkpoints allow you to save conversation state and rewind to previous points in your Claude Code session. This is invaluable for exploring different approaches, recovering from mistakes, or comparing alternative solutions.

Think of checkpoints like save points in a video game. As you work with Claude Code, every tool call — file edits, terminal commands, new files — creates an automatic checkpoint. If Claude goes down a path you don't like, you can rewind to any earlier point and try a different direction without losing your place.

Why Checkpoints Matter

When you ask Claude Code to refactor a function or implement a feature, the changes might not turn out the way you expected. Without checkpoints, you'd need to manually undo each change or rely on git to restore files. Checkpoints let you instantly roll back the entire conversation state — including all file modifications — to exactly where things were before.

How to Use Checkpoints

Checkpoints are created automatically after each tool use. To rewind, look for the checkpoint indicator in your conversation history and select the point you want to return to. You can also use the keyboard shortcut:

• Press Shift+Tab to open the checkpoint selector
• Choose the checkpoint you want to restore
• Claude Code reverts all file changes made after that point

A Practical Workflow

Say you ask Claude to restructure a component two different ways. After seeing the first approach, rewind to the checkpoint before the changes were made, then ask for the second approach. Now you can compare both results from the same starting point — no git stashing or branch juggling required.

Key takeaway: Checkpoints remove the fear of experimentation. Because you can always rewind, you're free to try bold refactors, test risky changes, and explore multiple solutions without worrying about cleaning up if things go wrong.