01
Sign In
Create a free account with your email. Your dashboard is tied to that identity.
✦FREE · HUMAN REVIEWED · GITHUB NATIVEA safer repair loop
A safer repair loop
for your codebase
Connect the GitHub projects you choose. VibeCode watches for repairable failures, gathers the relevant context, applies hard guardrails, and can open a draft pull request for you to review. It never auto-merges.
No trial · No credit card · You decide what gets merged
Explainable repairs
See what broke. See what changed.
✦Workflow
FROM FAILURE TO A REVIEWABLE DRAFT
The model is one part of the system. Repository identity, deterministic policy, verification, and human review stay outside it.
02
Connect GitHub
Choose the repositories VibeCode is allowed to monitor. You can pause any project at any time.
03
Guard + Repair
VibeCode gathers the failing file and relevant evidence, then hard policy decides whether a repair is allowed, blocked, or needs a person.
04
Review the PR
Allowed repairs become draft pull requests. CI checks the proposal; you inspect the diff and choose whether to merge.
✦Guardrails
THE AI DOESN’T GET THE KEYS TO THE HOUSE
VibeCode uses source-backed engineering rules for context, but the boundaries that matter are enforced in normal application code.
01
Protected paths
Secrets, package manifests, CI workflows, database migrations, infrastructure, and core configuration are blocked from autonomous edits.
02
Sensitive changes escalate
Authentication, authorization, billing, webhooks, security boundaries, and unusually broad rewrites require human review.
03
No phantom code
Missing files, packages, APIs, or version facts are not guessed. Unknown context becomes an explicit stop or targeted lookup.
04
Minimal repairs
The agent is instructed to fix the demonstrated failure without unrelated refactors, formatting churn, dependency additions, or architecture changes.
05
Stale-write protection
The target file is re-read before a write. If it changed after analysis, the automated repair stops instead of overwriting newer work.
06
Drafts, checks, people
Repairs go to separate branches as draft PRs. Existing CI verifies them and the repository owner remains the merger.
✦FREE. THAT'S IT.
$0forever
No free-trial countdown, no credit card, and no Stripe wall. The monthly repair allowance is simply a fair-use limit for the public service.
✓Email account + private dashboard
✓Connect multiple GitHub projects
✓5 automated repair PRs per month
✓Project monitoring controls
✓Repair history and PR links
✓Source-backed developer rules
✓Deterministic repair guardrails
✓CI verification + human merge
✦FAQ
BUILT TO BE INSPECTABLE
Does VibeCode merge code automatically?＋
No. Allowed repairs open as draft pull requests. Your existing checks can run, and a person decides whether to merge.
Is it really free?＋
Yes. There is no trial or paid upgrade path in this version. Free accounts currently have a five-repair-per-month fair-use limit.
What happens when VibeCode is unsure?＋
It should stop. Missing context, protected paths, security-sensitive code, stale files, or an overly broad proposed change are reasons to block or require human review instead of guessing.
What does the dashboard show?＋
Your signed-in email, connected GitHub projects, monitoring state, recent repair activity, successful PRs, and links back to the real repositories and pull requests.
✦YOUR REPO. YOUR DECISION.See the repair before
See the repair before
you trust the repair.
Create your account, connect a project, and use the dashboard to watch the guarded workflow happen.