The vibe is the new commit.
Git keeps the code and loses the conversation that wrote it. VibeHub saves every commit with its prompts, agent transcript, and model, from Claude Code, Cursor, and more. Search it, restore it, ask an agent about it, fork it, or sell it as a template.
Prompts
Every prompt that shaped it
Agent transcript
Replies, reasoning & tool calls
Model & tool
Which model, in which editor
Code diff
A real git commit inside
Branch & mirror
Pushed to GitHub as usual
Spec
The intent behind the build
Deployed URL
Where it runs today
Prompts
Every prompt that shaped it
Agent transcript
Replies, reasoning & tool calls
Model & tool
Which model, in which editor
Code diff
A real git commit inside
Branch & mirror
Pushed to GitHub as usual
Spec
The intent behind the build
Deployed URL
Where it runs today
Works with the tools you already vibe in
Three pieces, one workflow.
A CLI and editor plugins that capture the vibe, a vibe 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
One record for a build: its spec, prompts, transcript, model, code diff, eval status, and deployed URL. Restore it from any commit. Fork it whole.
VibeHub.co
Where vibes get hosted, forked, and discovered. Publish a vibe the way you publish a repo, or list a project in the marketplace with its full history.
More than a commit log.
Capture from the tools you use, read and restore history with its reasoning attached, put an agent to work on it, and share the result.
Every commit keeps the conversation that wrote it.
Transcript-captured commits
Livevb commit uploads the diff with the agent session that produced it: prompts, replies, tool calls, model, and source tool.
Learn moreClaude Code plugin
LiveHooks attach each Claude Code session to the commit it led to, with no extra command to run.
Learn moreEditor + MCP connectors
LiveCursor, VS Code, Windsurf, and Replit are live; Zed, JetBrains, Visual Studio, and Copilot are in beta.
Learn moreSDK and MCP server
LiveStream live sessions from any agent with @vibehub/sdk, or give it 19 VibeHub tools over MCP.
Learn moreGit operations that know why the code changed.
Commit history with conversations
LiveBrowse commits per project with per-file diffs and the conversation beside each one.
Learn moreBlame, branches, and restore
Livevb blame maps each line to the commit, and so the conversation, that last changed it; vb branch and vb checkout restore any recorded commit.
Learn moreGitHub mirror
Livevb push mirrors to GitHub, and a webhook keeps the mirror in sync both ways. Teammates on plain git see nothing new.
Learn moreEncrypted transcripts
LiveCaptured transcripts are encrypted at rest and only returned to their owner. Signed links share read-only access.
Learn moreAn AI agent that works across your whole workspace.
Ask about your code history
LiveThe Vibe agent reads commits, diffs, blame, branches, and mirrors, so you can ask why something changed.
Learn moreActs, not just answers
Live48 tools: create, fork, and compare vibes, manage collections and workflows, buy from the marketplace, and triage notifications. Every write waits for your Approve click.
Learn moreMemory
LiveTell the agent to remember a preference or fact and it carries over to later conversations.
Learn morevb ai in the terminal
LiveDescribe what you want in plain English; Claude turns it into vb steps and runs them.
Learn moreShare the work, and the reasoning behind it.
Public vibes and profiles
LivePublish a vibe with its spec, model, and deployed URL. Each builder gets a public profile page.
Learn moreMarketplace
LiveSell a project for credits or give it away. Buyers get a copy with its commits, conversations, and branches. Sellers earn credits on each sale.
Learn moreForks, collections, and following
LiveFork a public vibe, save vibes into collections, and follow the builders you like.
Learn moreAnalytics and notifications
LiveSee activity, forks, and run spend across your vibes, with in-app notifications and a Cmd+K command palette.
Learn moreReplays, evals, and workflows, as a simulated preview.
Runs and replays
Simulated previewQueue a replay of a vibe and track its status, tokens, and cost. Execution is simulated while the real runner is built: no model is called, and runs are free.
Learn moreEvals
Simulated previewAttach eval results to a vibe and show pass or fail on it. Scoring is simulated for now: results are generated, not measured, and evals are free.
Learn moreWorkflows
Simulated previewDefine a trigger and an action and run it from the dashboard. Triggers are recorded and notify you; the action itself is not executed yet. Automatic triggers on commit, publish, and fork are coming.
Learn moreWorks 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
Plugin: hooks + skill
VS Code
Editor extension
Cursor
Native MCP
Windsurf
Cascade MCP
Replit
Agent + commits
Zed
Context server MCP
JetBrains
AI Assistant MCP
Visual Studio
MCP via .mcp.json
Copilot
Chat import
v0
Browser capture
Lovable
Browser capture
Bolt
Browser capture
From vb init to vb ai
The CLI operates on vibes the way git operates on commits. If you know git, you already know vb, and any git command it doesn't define passes straight through.
$ vb init
Register the repo as a project. Every commit from here carries its full vibe.
$ vb commit
Commit and upload the diff with its prompts, transcript, and model.
$ vb log
Recent commits with their conversation counts, so you see why each change happened.
$ vb show
One commit's diff and the conversation that produced it, side by side.
$ vb blame
Map each line of a file to the commit, and conversation, that last changed it.
$ vb checkout
Restore the working tree to any recorded commit, optionally on a new branch.
$ vb branch
List, create, switch, and sync branches between git and the hub.
$ vb push
Push to origin and mirror to GitHub. Plain git stays in the loop.
$ vb ai
Say what you want in English; Claude turns it into vb steps and runs them.
Built in the open
Public vibes people have published, each with the prompts, model, and tool behind it.
Stripe-style pricing page
Stripe-style pricing page — generated, evaluated, and deployed as a single vibe.
Auth flow with magic links
Auth flow with magic links — generated, evaluated, and deployed as a single vibe.
AI photobooth with style presets
AI photobooth with style presets — generated, evaluated, and deployed as a single vibe.
Dashboard charts refactor
Dashboard charts refactor — generated, evaluated, and deployed as a single vibe.
Eval harness v2
Eval harness v2 — generated, evaluated, and deployed as a single vibe.
Landing hero rewrite
Landing hero rewrite — generated, evaluated, and deployed as a single vibe.
Free to vibe. Credits to scale.
The vb CLI, public vibes, and GitHub mirroring are free forever, and so is capturing the conversation behind every commit. Two premium actions, agent chat and vibehub-remote pushes, cost credits. Marketplace templates cost whatever the seller sets. Buy what you need, top up whenever.
Free
Everything you need to ship public vibes.
Includes:
- Full vb CLI (git superset)
- Unlimited public vibes
- Transcript-captured commits
- Mirror to GitHub on push
- Fork any public vibe
- Read the dashboard, browse history
- Free listings in the marketplace
- Claude Code transcript viewer
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
- vibehub-remote git push2 credits
Everything else is free: reading commits, browsing the dashboard, and public-vibe forks.
Free right now
Transcript capture: 0 credits
Every commit captured with vb commit or vb capture, conversation included.
Free with no end date: capture is the core loop and stays unmetered.
Simulated preview runs: 0 credits
Runs and evals, from the dashboard, the API or the agent's run tool. They're a simulated preview: nothing executes against a model yet.
Free while run execution is simulated. Runs will cost credits once they execute for real.
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 keeping the reasoning with the code.
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
- Every commit keeps its conversation
- Git superset — wraps a real commit
- Captures from Claude Code, Cursor, VS Code, and more
- Blame, restore & fork with the context intact
- Mirrors to GitHub — no migration
Questions, answered.
The short version of how VibeHub fits into the way you already build.
A vibe is the record of everything that produced a build: the spec, the prompts, the agent transcript, the model and tool, the code diff, the eval status, and the deployed URL. Under the hood every commit you make with vb, the Claude Code plugin, or an editor connector keeps the conversation that wrote it, so you can read, blame, restore, and fork the work with its reasoning attached.
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 (via a plugin with hooks and a capture skill), VS Code, Cursor, Windsurf, and Replit are Live today. Zed, JetBrains IDEs, and Visual Studio connect over MCP, and GitHub Copilot chats import through the VS Code extension — all in Beta. Capture from v0, Lovable, and Bolt is planned. 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. To share something private, send a signed read-only link.
The in-app agent has 48 tools across your workspace. It reads commits, diffs, blame, branches, and mirror status, so you can ask why a change was made. It also acts: creating, forking, and comparing vibes, managing collections and workflows, browsing and buying from the marketplace, following builders, and clearing notifications. Nothing that writes runs until you click Approve in the chat. Ask it to remember a preference and it carries over to later chats. In the terminal, vb ai does the same for CLI steps.
List a project for a credit price, or for free. Each listing is reviewed before it goes live. A buyer gets their own copy of the project with its commits, attached conversations, branches, and vibes, so they can see how it was built, not just the final code. Sellers earn credits on each sale.
Yes. The TypeScript SDK (@vibehub/sdk) streams a live session into VibeHub and attaches it to a commit, and the MCP server gives any MCP client 19 VibeHub tools. Both use the REST API documented on the developers page.
The vb CLI, public vibes, GitHub mirroring, free marketplace listings, and reading the dashboard are free forever, and so are transcript-captured commits and simulated preview runs. Credits power two premium actions: 1 credit per Vibe agent turn and 2 credits per vibehub-remote push. Paid marketplace templates cost what the seller sets. Credits never expire — top up whenever from /dashboard/upgrade.
Talk to us.
VibeHub is open to everyone: create a free account and run vb init. Want help setting up a team, a shared credit pool, or an integration we don't list yet? Tell us what you're building.