The vibe is the new commit.
Git versions text files. Your AI work is bigger than that — the spec, the prompts, the agent transcript, the model config, the code diff, the eval, the deployed artifact. VibeHub versions all of it as one forkable bundle.
Spec
The intent behind the build
Prompts
Every prompt that shaped it
Agent transcript
The full reasoning trail
Model config
Model, params & seeds
Code diff
A real git commit inside
Eval result
Did it actually work?
Deployed artifact
The live URL & screenshots
Spec
The intent behind the build
Prompts
Every prompt that shaped it
Agent transcript
The full reasoning trail
Model config
Model, params & seeds
Code diff
A real git commit inside
Eval result
Did it actually work?
Deployed artifact
The live URL & screenshots
Works with the tools you already vibe in
Claude Code
Cursor
Replit
Windsurf
v0
Lovable
Bolt
Copilot
Claude Code
Cursor
Replit
Windsurf
v0
Lovable
Bolt
Copilot
Three pieces, one workflow.
A CLI that captures the whole vibe, a bundle format that holds it together, and a hub where it gets shared.
The vb CLI
A git superset for your terminal. Every vibe wraps a real git commit, so adopting vb is incremental — never a migration.
$ vb init
$ vb commit -m "add auth"
$ vb push # mirrors to GitHub
The vibe object
A content-addressed bundle of spec, prompts, transcript, model config, diff, eval, and artifact. Roll it back together. Fork it together.
VibeHub.com
Where vibes get hosted, forked, reviewed, and discovered. Publish a vibe the way you publish a repo — others remix the whole thing.
Works with your whole stack
vb captures the vibe straight from the editor you already use. We're a substrate, not a replacement — no new workflow to learn.
Claude Code
Session hooks
Cursor
Native MCP
Windsurf
Cascade MCP
Replit
Agent + commits
v0
Browser capture
Lovable
Browser capture
Bolt
Browser capture
Copilot
VS Code extension
From vb init to vb fork
The CLI operates on vibes the way git operates on commits. If you know git, you already know vb.
$ vb init
Wrap your repo. Every commit from here carries its full vibe.
$ vb commit
Bundle the code diff with its prompts, transcript, and model config.
$ vb log
Browse vibes, not just commits — see why each change happened.
$ vb diff
Compare specs and prompts, not only the code that changed.
$ vb replay
Re-run a vibe against a new model and watch it rebuild itself.
$ vb fork
Clone someone's whole vibe — spec, prompts, and all — then remix.
Free to vibe. Credits to scale.
The vb CLI, public vibes, and GitHub mirroring are free forever. Premium actions — agent chat, transcript capture, eval runs, and vibehub-remote pushes — cost credits. Buy what you need, top up whenever.
Free
Everything you need to ship public vibes.
Includes:
- Full vb CLI (git superset)
- Unlimited public vibes
- Mirror to GitHub on push
- Fork & replay any public vibe
- Read the dashboard, browse history
Starter
250 credits
$0.02 per credit · one-time
For trying out premium features
Builder
1,000 credits
$0.015 per credit · one-time
For builders shipping every day
Pro
5,000 credits
$0.010 per credit · one-time
For teams running heavy eval loads
What costs credits
- Vibe agent turn1 credit
- Transcript-captured commit1 credit
- vibehub-remote git push2 credits
- Eval run5 credits
Everything else — reading commits, browsing the dashboard, public-vibe forks — is free.
Why credits, not seats
- Pay for what you use. No monthly minimums, no surprise seat charges.
- Credits never expire. Top up once, draw down across months.
- One wallet, every app. Powered by cred.diy — your credits work anywhere we integrate.
- Team-friendly. Need a shared pool or invoicing? Reach out — we'll set you up.
Why not just…?
Everyone's building a better prompt box or another AI editor. The real gap is versioning the whole vibe.
Git alone
- Versions text files, nothing else
- Prompts & transcripts vanish
- Can't roll back the spec or eval
- No way to share the reasoning
Prompt tools & AI editors
- A nicer prompt box, nothing more
- Code and prompts stay siloed
- Locked into a single editor
- Asks you to migrate everything
VibeHub
- Versions the whole vibe as one bundle
- Git superset — wraps a real commit
- Works with every AI tool you use
- Fork, replay & roll back together
- Mirrors to GitHub — no migration
Questions, answered.
The short version of how VibeHub fits into the way you already build.
A vibe is a content-addressed bundle of everything that produced a build: the spec, the prompts, the agent transcript, the model and parameters, the code diff, the eval result, and the deployed artifact. It's the unit vb versions — the way git versions a commit.
No. vb is a git superset. Every vibe wraps a real git commit, and vb push mirrors straight to GitHub. You get more without giving anything up, and teammates still on plain git aren't affected at all.
Claude Code, Cursor, Windsurf, and Replit are Live today. v0, Lovable, Bolt, and GitHub Copilot are in Beta via a browser bookmarklet or VS Code extension. vb captures the vibe straight from the tool you already use — there's no new workflow to adopt.
Public vibes are public; private vibes stay private to you. You decide what to publish. Captured transcripts are encrypted at rest and only ever returned to you — never to other accounts.
The vb CLI, public vibes, GitHub mirroring, and reading the dashboard are free forever. Credits power premium actions: 1 credit per Vibe agent turn, 1 credit per transcript-captured commit, 2 credits per vibehub-remote push, 5 credits per eval run. Credits never expire — top up whenever from /dashboard/upgrade.
Get the vb alpha.
VibeHub is in private beta. Tell us what you're building and we'll send you an invite as we open up the alpha.