Fork this vibe
Claude Code · 1.2k forks
one-pager-saas
A complete one-page SaaS, spec to deploy. Fork the whole vibe and ship your own variant in 20 minutes.
AI-native version control
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
How It Works
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.
1Spec & prompts
2Agent transcript
3Model config
4Code diff
5Eval + artifact
VibeHub.com
Where vibes get hosted, forked, reviewed, and discovered. Publish a vibe the way you publish a repo — others remix the whole thing.
levelsio/one-pager 1.2k
The Shift
Git was built for human-written code. The world moved on.
Prompts vanish the second you close the tab. The spec lives in a doc, the eval in a notebook, the deploy in a dashboard. Nobody can roll it back together — until now.
Our bet
The unit of version control is no longer the file — it's the vibe. A content-addressed bundle of everything that produced your build, that you can fork, replay, and roll back as one.
+50
Built with indie hackers shipping in public
0%
Of all new code is AI-generated
0%
Of US developers use AI tools daily
0%
Annual growth in the vibe-coding market
0
Places one vibe is scattered today
Featured Vibes
Fork a whole vibe
Real builds published with their spec, prompts, and config intact. Clone the result and the reasoning that got there.
Fork this vibe
v0 + Cursor · 840 forks
ai-photobooth
An image-gen app with the exact prompts, model, and seeds baked in. Replay it end to end and remix the look.
Fork this vibe
Lovable · 2.3k forks
launch-landing
A high-converting launch page with every prompt and eval included. Keep the structure, rewrite the copy.
Integrations
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.
C
LiveClaude Code
Transcript API
C
LiveCursor
Composer logs
R
BetaReplit
Agent + DB state
W
SoonWindsurf
Cascade history
v
Soonv0
Generations
L
SoonLovable
Build history
B
SoonBolt
Project state
C
SoonCopilot
Chat + edits
Workflow
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.
Pricing
Free to vibe. Pay to scale.
Free
$0/mo
For solo vibecoders & indie hackers
Includes:
- Full vb CLI (git superset)
- Unlimited public vibes
- Mirror to GitHub on push
- Fork & replay any public vibe
- Community support
Pro
$12/mo
For builders shipping every day
Everything in Free, plus:
- Unlimited private vibes
- Full vibe history & rollback
- Eval tracking across runs
- Priority transcript capture
- Private profile & vibe pages
Popular
Team
$32/mo / seat
For teams that need an audit trail
All Pro features, plus:
- Shared private vibe registry
- Audit trails & access control
- Review & approve vibes
- SSO + dedicated support
Builders
Shipped in public.
Notes from the vibecoders and indie hackers already living inside their vibes.
"I forked someone's published vibe, swapped the model, and shipped a variant in 20 minutes. That used to be a weekend."
Mara Vance
Solo Founder
"Finally my prompts don't die when I close the tab. vb commit grabs the whole transcript, and I can roll the bad runs back."
Diego Ramos
Indie Hacker
"We needed an audit trail for AI-generated code and VibeHub just had it. Every diff links to the prompt that wrote it."
Priya Nathan
Engineering Lead
"vb replay is wild. I re-ran an old vibe on a newer model and it rebuilt the feature — cleaner than my original."
Sam Whitfield
Vibecoder
"It's git, but it actually remembers how the code got written. The vibe page is the link I drop now instead of a repo."
Tom Becker
Product Engineer
"I forked someone's published vibe, swapped the model, and shipped a variant in 20 minutes. That used to be a weekend."
Mara Vance
Solo Founder
"Finally my prompts don't die when I close the tab. vb commit grabs the whole transcript, and I can roll the bad runs back."
Diego Ramos
Indie Hacker
"We needed an audit trail for AI-generated code and VibeHub just had it. Every diff links to the prompt that wrote it."
Priya Nathan
Engineering Lead
"vb replay is wild. I re-ran an old vibe on a newer model and it rebuilt the feature — cleaner than my original."
Sam Whitfield
Vibecoder
"It's git, but it actually remembers how the code got written. The vibe page is the link I drop now instead of a repo."
Tom Becker
Product Engineer
Compare
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
FAQs
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 and Cursor today, Replit in beta, with Windsurf, v0, Lovable, Bolt, and Copilot on the way. vb captures the vibe straight from the editor you already use — there's no new workflow to adopt.
Public vibes are public; private vibes stay private to you or your team. You decide what to publish. Team plans add access control and audit trails so you always know which prompt produced which diff.
Early Access
Get the vb alpha.
We're onboarding alpha users in waves, starting with indie hackers shipping in public. Tell us what you're building and we'll get you an invite.