VibeHub vs Shift Log (claudit): git notes vs hosted
Last reviewed 2026-11-12
| Feature | VibeHub | Shift Log |
|---|---|---|
| How it captures | Claude Code plugin hooks; vb commit | Runs on commit after shiftlog init |
| Where history lives | VibeHub, linked to the git commit | Git notes in your repository |
| Linked to git commits | Yes | Yes — one note per commit |
| Agents supported | Claude Code plugin; MCP and editor setups for Cursor, Windsurf, VS Code, Zed, JetBrains | Claude Code, Codex CLI, Copilot CLI, Gemini CLI, OpenCode |
| Search and resume | Browse sessions per project and commit; vb show <sha> | List, search (including regex), summarize, and resume by commit |
| Sharing | Public vibe pages and forks | Anyone with access to the repository's notes |
| Open source | Hosted service; plugins MIT | Yes |
| Pricing | CLI and transcript capture free | Free |
What Shift Log does
Shift Log, which started out as claudit, hangs agent history on git itself. Run shiftlog init in a repository, and whenever you or the agent commit, the conversation since the previous commit is attached to the new commit as a git note.
It works with Claude Code, Codex CLI, Copilot CLI, Gemini CLI, and OpenCode, and it can list, search (including by regular expression), summarize, and resume past sessions by commit. It is a small project, so weigh that if you need long-term support.
What VibeHub does differently
VibeHub keeps the same link between a session and its commit, but stores the session on VibeHub instead of in the repository. The Claude Code plugin streams each prompt, tool call, and assistant turn into a session as you work, and the /vibehub:capture skill or vb commit attaches it to the commit. Sessions are encrypted at rest and private unless you publish them.
Published vibes are public pages that show the prompts behind a build, and others can fork them with lineage back to the original. vb push mirrors your commits to GitHub, so code review stays where it is.
Which to pick
If everything should stay in your own git remote and you want no new account, Shift Log is the simpler fit. Keep in mind that anything stored in git notes is visible to everyone with access to those notes, so check transcripts for secrets before you share them.
If you want reviewers, teammates, or the public to read a session without cloning the repository, or you want to publish and fork AI-built work, VibeHub is built for that.
Choose Shift Log if…
- You want session history stored in the repository itself, with no hosted service.
- You switch between several CLI agents and want one tool that covers them.
- You want an open-source tool you can read and change.
Choose VibeHub if…
- You want to share a session as a page without giving people access to the repository.
- You want to publish AI-built work as vibes others can fork.
- You want sessions kept out of your repository rather than in git notes.
Questions, answered.
- Is Shift Log the same as claudit?
- Yes. Shift Log is the current name of the project that started as claudit, and its repository is still at github.com/re-cinq/claudit.
- Where does Shift Log store conversations?
- As git notes attached to each commit, in the same repository as your code. VibeHub stores them on VibeHub, linked to the commit.
- Can I use both?
- They capture at different points, Shift Log on commit and VibeHub through its plugin and
vb commit, but we have not tested them together, so try it on a scratch repository first.
Sources
- Shift Log repo (GitHub) (checked on )
More comparisons
Version the whole vibe.
The vb CLI, public vibes, and GitHub mirroring are free forever.