Stop burning tokens.
Ship better code.

One command gives your AI-generated codebase a full senior engineering team. Saves $20-40/day in tokens. Finds and fixes every problem.

Get Started See How It Works
npx vibe-crew
4.3M
Tokens saved in 2 days
$40
Saved per day (heavy use)
$3
Cache server per month
95%
Fix confidence target
$ npx vibe-crew --key ABCD-EF12-GH34-IJ56 ✔ License: starter plan ✔ Found: Next.js project Detected: Framework: Next.js Database: Supabase Auth: Supabase Auth Payments: Stripe API routes: yes Agents: build-gate haiku Build verification qa-signoff haiku Final QA gate regression-checker haiku Side effect detection orchestrator opus 3-solution finder vibe-audit opus Code audit + auto-fix security-reviewer sonnet DB security audit auth-verifier sonnet Auth flow validation ✔ Agent team generated! ✔ Agent hooks configured! Inside Claude Code, just type: /vibe-audit Audit + fix your entire codebase /vibe-review Quick agent team fitness check /vibe-launch Parallel orchestrator mode /vibe-crew Show all available commands

Getting Started Guide

From zero to a fully audited codebase in under 5 minutes. Follow every step below.

PREREQUISITES

What you need before you start

vibe-crew works inside Claude Code (Anthropic's CLI for Claude). Make sure you have these installed:

Node.js 18+

Required to run npx and the CLI

$ node --version
v22.0.0

Claude Code

The AI coding CLI from Anthropic

$ npm install -g @anthropic-ai/claude-code
$ claude

A codebase

Any project with code in it. We detect 15+ stacks automatically.

$ cd ~/my-project

Anthropic API key

Claude Code needs this to run agents. Set it in your environment.

$ export ANTHROPIC_API_KEY=sk-ant-...
STEP 1

Get your license key

Pick a plan below and complete checkout. Your license key will be emailed to you immediately. It looks like this:

ABCD-EF12-GH34-IJ56

Check your inbox (and spam folder) for an email from noreply@picvaultpro.com with the subject "Your CodeCrew license key".

Want to preview first? Run npx vibe-crew --dry-run to see what agents would be generated for your project, without needing a license key.

STEP 2

Activate your license

Open your terminal, navigate to your project directory, and run:

$ cd ~/your-project $ npx vibe-crew --key ABCD-EF12-GH34-IJ56

This does three things at once:

1. Saves your license to ~/.vibe-crew/license so you never need to enter it again
2. Scans your codebase to detect your framework, database, auth, payments, and more
3. Generates your agent team with specialized agents tailored to your exact stack

Your key works on all your projects. Once activated, just run npx vibe-crew (no --key flag) in any new project. The license is stored globally.

STEP 3

Watch it scan and generate

The CLI will output everything it finds and creates. Here's what a typical run looks like:

# It scans your codebase first ✔ Found: Next.js project Detected: Framework: Next.js Database: Supabase Auth: Supabase Auth Payments: Stripe API routes: 14 routes Components: 47 files Tests: 3 test files # Then generates agents matched to your stack Agents to generate: build-gate haiku Build + lint verification qa-signoff haiku Final QA with physical proof regression-checker haiku Side effect detection orchestrator opus 3-solution finder (97% confidence) security-reviewer sonnet Supabase RLS + auth audit api-prober haiku API endpoint testing # Then sets up hooks so agents run automatically ✔ Agent team generated! ✔ Agent hooks configured! ✔ Slash commands installed!

The generated files go into your project's .claude/ directory:

.claude/ agents/ # Agent definitions build-gate.md qa-signoff.md regression-checker.md orchestrator.md security-reviewer.md ... settings.json # Auto-trigger rules CLAUDE.md # Project instructions
STEP 4

Open Claude Code and use your commands

Start Claude Code in your project directory. Your new slash commands are ready immediately:

$ claude # Now inside Claude Code, type any of these: /vibe-audit Full codebase audit. Finds security holes, dead code, bad patterns, missing error handling. Fixes everything to 95% confidence. Generates a report. /vibe-review Quick check: are your agents right for this codebase? Finds coverage gaps. Suggests new agents if your stack has changed. /vibe-launch Give it a list of problems. Each gets its own orchestrator with 3 competing solutions. Picks the best one automatically. /vibe-init Re-run the setup. Use this after adding a major new dependency or changing your stack. /vibe-crew Show all available commands and your current agent team status.
STEP 5

Run your first audit

This is where the magic happens. Inside Claude Code, type:

/vibe-audit

The audit team will:

1. Scan every file in your project for issues
2. Categorize findings: security, performance, dead code, patterns, architecture
3. Fix each issue automatically with the appropriate agent
4. Validate every fix passes build + tests via the build-gate agent
5. Report a summary of everything found and fixed

First audit can take 5-15 minutes depending on codebase size. Subsequent runs are much faster thanks to caching.

AUTOMATIC

Agents run automatically too

vibe-crew configures hooks so certain agents trigger without you doing anything:

# When you edit a file: build-gate runs automatically to verify the build # When you commit: qa-signoff verifies changes before the commit lands regression-checker scans for side effects # When you push: The full agent team validates the branch

You can customize which agents auto-trigger by editing .claude/settings.json in your project.

You vibe coded your app. Now what?

Reddit knows the feeling. Here's what developers are saying:

"I have this constant low-grade anxiety that somewhere in the codebase there's a function that's one wrong input away from catastrophic failure."

r/vibecoding

"Built my SaaS in 3 days. Last week I sat down to add one small feature. One day gone. 30k lines I can't navigate."

r/startups

"Each fix introduces two new problems because the LLM has no memory of why it made those architectural decisions."

r/vibecoding — 572 upvotes

"If you've vibe coded Supabase Row Level Security and it actually works, you're lying."

r/vibecoding

What linters catch vs. what we catch

ESLint is spell-check. This is an editorial board.

What linters find

  • Unused variable
  • Missing semicolon
  • Wrong indentation
  • Import order
  • Trailing whitespace
  • Inconsistent quotes

What /vibe-audit finds (and fixes)

  • 3 API routes with zero auth
  • SQL injection in search endpoint
  • 2,400 lines of dead code
  • Duplicated fetch logic in 8 files
  • God component with 847 lines
  • Missing error boundaries everywhere

How it works

Three steps. Five minutes. Zero config.

1

Scan

Detects your language, framework, database, auth, payments, storage, mobile — everything. Works with Next.js, Python, Go, Rust, Swift, and 15+ stacks.

2

Generate

Creates specialized AI agents tailored to YOUR stack. Build gate, QA signoff, security reviewer, orchestrator — each knows your tools.

3

Audit + Fix

Sends the team through your codebase. Finds dead code, security holes, bad patterns. Fixes everything to 95% confidence. Writes a report.

/vibe-audit

Full codebase scan. Finds every problem. Fixes them all. Validates the build. 95% confidence.

/vibe-review

Quick check — are your agents right for this codebase? Coverage gaps? Wrong tiers?

/vibe-launch

Give it multiple problems. Each gets its own orchestrator with 3 solutions. Wake up to fixes.

/vibe-init

Re-run setup. Regenerate agents after your codebase evolves.

The math on token savings

Your agents repeat each other's work. The cache fixes that.

Without cache: build-gate runs → npm run build (1 min) → 24KB output qa-signoff runs → npm run build (1 min) → 24KB output ← DUPLICATE regression runs → npm run build (1 min) → 24KB output ← DUPLICATE With cache ($3/month): build-gate runs → npm run build (1 min) → Caches 250-byte summary qa-signoff runs → Reads cache (instant) → 250 bytes ← SAVED regression runs → Reads cache (instant) → 250 bytes ← SAVED Tokens saved per cycle: 33,750 (~99.3%) Daily savings (heavy use): $20-40 Monthly savings: $600-1,200

Pricing

The preview is free. The full tool pays for itself in an hour.

Pro Cache
$9/month
Starter + managed cache server
  • Everything in Starter
  • Managed Fly.io cache server
  • Token savings dashboard
  • 1,000 cache keys, 24hr TTL
  • Saves $20-40/day in tokens
  • Priority support
Team
$29/month
For teams shipping daily
  • Everything in Pro
  • 5,000 cache keys, 48hr TTL
  • Shared agent configs across repos
  • Team savings analytics
  • Slack integration
Have a code? Enter it before checkout.

Help & FAQ

Everything you need to know about vibe-crew.

What exactly does vibe-crew generate?
It generates a .claude/ directory in your project containing: agent definitions (Markdown files that tell Claude Code how each specialized agent behaves), a settings.json with auto-trigger hooks, and a CLAUDE.md with project-level instructions. These are plain text files you can read, edit, and commit to your repo.
Does vibe-crew modify my source code?
The npx vibe-crew setup command only writes files inside .claude/. It never touches your source code. However, when you run /vibe-audit inside Claude Code, the audit agents will make changes to fix the issues they find. You can review every change before accepting it, just like any Claude Code edit.
What languages and frameworks are supported?
The scanner auto-detects: Next.js, React, Vue, Svelte, Angular, Express, Fastify, Django, Flask, FastAPI, Rails, Go, Rust, Swift/SwiftUI, Kotlin/Compose, and more. It also detects databases (Supabase, Postgres, MongoDB, Prisma), auth providers (Supabase Auth, Clerk, NextAuth), payment processors (Stripe), and deployment platforms (Vercel, Fly.io, AWS). If your stack isn't detected, the agents still work with a general-purpose configuration.
I didn't get my license email. What do I do?
Check your spam/junk folder for an email from noreply@picvaultpro.com. The email is sent immediately after Stripe checkout completes. If you still can't find it after 5 minutes, email support@picvaultpro.com with your checkout email address and we'll resend your key.
Can I use my license key on multiple projects?
Yes. Your license key is stored globally at ~/.vibe-crew/license. Once activated, run npx vibe-crew in any project directory and it will generate agents for that project automatically. No per-project limits.
What's the difference between Starter and Pro?
Starter ($29 one-time) gives you the full agent team, all slash commands, and auto-trigger hooks. This is everything you need to audit and fix your code.

Pro ($9/mo) adds a managed Fly.io cache server. The cache prevents agents from repeating each other's work (like re-running builds). If you use Claude Code heavily (multiple agents running per session), the cache saves $20-40/day in tokens. It pays for itself within the first hour of heavy use.
How do I preview what agents would be generated?
Run npx vibe-crew --dry-run in your project directory. This scans your codebase and shows you exactly which agents would be created, what they'd do, and which Claude model tier each would use — without writing any files or requiring a license key.
What does /vibe-audit actually check?
The audit scans for: security vulnerabilities (unprotected API routes, SQL injection, XSS, missing auth checks, weak RLS policies), dead code (unused functions, unreachable branches, orphan files), code quality (duplicated logic, god components, missing error boundaries), architecture issues (circular dependencies, leaky abstractions), and performance problems (N+1 queries, missing indexes, bundle size). Each finding is fixed automatically and validated by the build-gate agent.
Can I customize which agents run automatically?
Yes. Open .claude/settings.json in your project. You'll see a hooks section that maps file patterns to agents. Remove an entry to stop that agent from auto-triggering, or add new patterns. You can also edit the agent Markdown files in .claude/agents/ to change what each agent does.
How do I regenerate agents after my stack changes?
Run /vibe-init inside Claude Code, or run npx vibe-crew again from your terminal. Both will re-scan your codebase and update the agent definitions to match your current stack.
Does it work offline?
License validation requires an internet connection the first time. After that, if you go offline, the CLI will use your cached license and allow full functionality. The agents themselves run through Claude Code, which also requires internet access to communicate with the Claude API.
How do I cancel my Pro or Team subscription?
Email support@picvaultpro.com with your account email and we'll cancel immediately. Your agents and slash commands continue to work (those are local files), but the cache server will be deprovisioned at the end of your billing period.
I'm getting "License no longer valid" — what happened?
This means your license was cancelled or expired (usually from a failed payment on a Pro/Team subscription). Check your email for a payment failure notice from Stripe. If you believe this is an error, email support@picvaultpro.com. Starter licenses (one-time payment) never expire.
Where can I get help or report bugs?
Open an issue on GitHub, or email support@picvaultpro.com. Include the output of npx vibe-crew --dry-run so we can see your stack detection results.

Your code deserves a senior engineering team.

One command. Zero config. Start in 30 seconds.

npx vibe-crew --dry-run