VibeHub vs Claude Code checkpoints: undo vs history
/rewind (or Esc twice) restores code, conversation, or both to an earlier prompt. Anthropic is explicit that they are not a replacement for version control. VibeHub is that long-term layer — it attaches the Claude Code transcript to real git commits you can share and mirror to GitHub — so the two are complementary, not competing.Last reviewed 2026-10-31
| Feature | VibeHub | Claude Code checkpoints |
|---|---|---|
| Built into Claude Code | Plugin install + API token | Yes — on by default |
| Rewind code mid-session | No — works at commit granularity | Yes — every prompt is a checkpoint |
| Rewind or summarize the conversation | No | Yes |
| Long-term history | Yes — attached to git commits | Snapshots cleaned up after ~30 days by default |
| Tracks Bash-only file changes | Yes — the git commit captures them | No |
| Shareable with a team | Yes — vibe pages, forks, GitHub mirror | No — local to the session |
| Other AI tools | Cursor, VS Code, Windsurf, Replit and more | Claude Code only |
| Cost | 1 credit per transcript-captured commit | Included |
What checkpoints do
Claude Code automatically snapshots your code before each prompt that starts a turn. Run /rewind or press Esc twice on an empty prompt to pick an earlier point and restore code and conversation, just the conversation, or just the code — or summarize part of the conversation to free context.
It keeps file snapshots for the 100 most recent checkpoints in a session, and they survive resuming a session. By default, snapshots are cleaned up about 30 days after the session last saved one (configurable via cleanupPeriodDays).
Where checkpoints stop
Per Anthropic, files changed only by Bash commands are not tracked, most subagent edits are not restored, and manual edits or other concurrent sessions are normally not captured. The docs say it directly: checkpoints are for quick, session-level recovery — keep using version control such as Git for permanent history and collaboration.
How VibeHub complements them
The VibeHub Claude Code plugin uses hooks (SessionStart, UserPromptSubmit, PostToolUse, Stop, SubagentStop, SessionEnd) to stream prompts, tool calls, and assistant turns into a VibeHub session, and a /vibehub:capture skill attaches the conversation to a git commit. Capture is fail-open — it never blocks Claude Code.
So use checkpoints to undo a bad turn in the moment, and commit with vb when the work is good: the commit lands in git, mirrors to GitHub, and carries the transcript that produced it.
Choose Claude Code checkpoints if…
- You just need to undo a bad turn or try an alternative inside the current session — checkpoints are faster and built in.
- You want to rewind or compress the conversation itself, which VibeHub does not do.
- You only use Claude Code and do not need to share session history with anyone.
Choose VibeHub if…
- You want the transcript to outlive the session and stay attached to the commit it produced.
- You need teammates or reviewers to see the prompts behind a change.
- You also use other AI tools and want one history across all of them.
Questions, answered.
- Should I turn off checkpoints if I use VibeHub?
- No. They solve different problems — checkpoints are in-session undo, VibeHub is versioned history attached to git commits. Use both.
- Are Claude Code checkpoints a replacement for git?
- Anthropic says no: checkpoints are designed for quick, session-level recovery, and you should keep using version control for permanent history and collaboration.
- How does VibeHub capture Claude Code sessions?
- Through a Claude Code plugin with hooks that stream each prompt, tool call, and assistant turn into VibeHub, plus a
/vibehub:captureskill for attaching a conversation to a commit.
More comparisons
Version the whole vibe.
The vb CLI, public vibes, and GitHub mirroring are free forever.