~/.claude/file-history/

See every file Claude edited, and put it back

Q: How is this different from /rewind?

/rewind (or Esc twice) rolls back inside a session, conversation and code together. The Checkpoints tab works from the saved file versions on disk, so you can diff or restore a single file at any time, even after the session ended.

Before Claude Code edits a file it keeps a copy in ~/.claude/file-history/. The Checkpoints tab lists those versions per session, opens a diff against what's on disk now, and restores the one you want.

Install from the Marketplace Get it on Open VSX

~/.claude/file-history/<session-id>/

Restore a file Claude Code changed

Open the Checkpoints tab and pick the session. You'll see each file Claude edited and the versions it saved.
Diff a version against the file as it is now, in VS Code's diff view.
Restore it after a confirmation. A closed file is written back byte for byte; an open one goes through your editor, so you can undo.

What checkpoints cover

Claude Code saves a copy of a file before it edits it, for its own /rewind feature (Esc twice). Those copies are what this tab reads. According to Anthropic's docs, checkpoints don't include files changed by shell commands that Claude ran, or edits made outside Claude Code — for those, use git.

FAQ

Questions, answered

How is this different from /rewind?

/rewind (or Esc twice) rolls back inside a session, conversation and code together. The Checkpoints tab works from the saved file versions on disk, so you can diff or restore a single file at any time, even after the session ended.

Does it cover changes made by shell commands?

No. Claude Code's checkpoints don't track files changed by Bash commands (like rm or mv) or by editing outside Claude Code, so there's no copy to restore.

Free, open source, and it stays on your machine.

Apache-2.0. No telemetry, no account, no network client. Works with the Claude Code CLI and the official extension.