Claude Code · Live

Save Claude Code session history and transcripts

The VibeHub plugin for Claude Code captures every session automatically: each prompt, tool call, and assistant turn streams into a VibeHub session as you work. It also adds a /vibehub:capture skill so you can ask Claude to attach a conversation to a commit or save a transcript on demand.

Set it up

Install the plugin (recommended)

claude plugin marketplace add aw3-technology/wanderly
claude plugin install vibehub@vibehub
export VIBEHUB_TOKEN=vbh_…   # Settings → API tokens in the dashboard

Legacy hooks, no plugin

npx vibehub-claude-code install
export VIBEHUB_TOKEN=vbh_…

What gets captured

  • A new VibeHub session for every Claude Code session (SessionStart)
  • Every prompt you submit, stored as a user message (UserPromptSubmit)
  • Every tool call, with its input and output (PostToolUse)
  • The assistant’s final turn (Stop) and subagent turns (SubagentStop)
  • Session end, so the run is marked complete (SessionEnd)

How it works

Claude Code hooks fire on session start, prompt submit, tool use, stop, subagent stop, and session end, and each event is sent to the VibeHub API.

The hook keeps a map of Claude session ids to VibeHub session ids in ~/.vibehub/claude-code/sessions.json, so parallel Claude Code sessions don’t collide.

The /vibehub:capture skill handles attach-to-commit, one-shot commit + transcript capture, ad-hoc output sessions, and project create/list.

Open a new Claude Code session after installing and it appears under Runs in the dashboard.

Claude Code + VibeHub FAQ

Will VibeHub slow down or block Claude Code if something goes wrong?
No. Capture is fail-open: if the token is missing or the API is unreachable, the hook logs to stderr and exits 0 — it never blocks Claude Code.
Can I attach a Claude Code conversation to a git commit?
Yes. Ask Claude to “attach this conversation to the last commit” and the /vibehub:capture skill calls the VibeHub API to link the transcript to that commit.
What does the legacy installer change on my machine?
npx vibehub-claude-code install merges hook entries into ~/.claude/settings.json, writing a .vibehub.bak backup first. You can also merge settings.template.json by hand.
Can I point it at a self-hosted VibeHub?
Yes. Set VIBEHUB_API_URL (default https://vibehub.co) alongside the required VIBEHUB_TOKEN.

Other integrations

VS CodeCursorWindsurfReplitZedJetBrainsAll integrations →

Version the whole vibe.

The vb CLI, public vibes, and GitHub mirroring are free forever.

Get started freeRead the quickstart