Home / Errors
Vibe Coding Errors: The Encyclopedia
47 documented errors across Lovable, Bolt, Replit, Cursor, v0, and Claude Code. Each page: what you are seeing, why it happens, and the exact steps to fix it.
Lovable
Errors in Lovable apps and their Supabase backends: error loops, RLS misfires, broken auth, lost backends.
5 errorsBolt.new
Bolt errors: token burn, WebContainer boot failures, context limits, vanished projects.
7 errorsReplit
Replit and Replit Agent errors: deleted databases, rollback surprises, dev vs production confusion.
7 errorsCursor
Cursor errors: deleted files, mangled edits, context loss, checkpoint and worktree traps.
3 errorsv0 by Vercel
v0 errors: stuck deployments, exports that will not build, missing environment variables.
4 errorsClaude Code
Claude Code errors: destructive commands, memory loss after compaction, unwanted git pushes.
6 errorsSupabase
Supabase errors in AI-built apps: RLS policy violations, edge function failures, paused projects, wiped tables.
8 errorsVibe coding (any tool)
Cross-tool failure patterns: leaked keys, missing auth, injection flaws, hallucinated packages, surprise bills.
Most damaging errors
Lovable Supabase RLS not enabled: anyone can read your app's data (CVE-2025-48757)
Lovable left Supabase RLS off? Anyone can read your users' data with the anon key (CVE-2025-48757). Fix it with exact SQL from the Supabase docs.
LovableLovable API key exposed: secrets visible in your client-side code
Lovable API key exposed? Anything in frontend code or a VITE_ variable is compromised. Rotate now, then proxy via an edge function, per Lovable's docs.
SupabaseAI-run migration or SQL wiped the Supabase database (tables and data gone)
An AI migration or 'db reset' wiped your Supabase tables? Stop prompting immediately. What's recoverable on each plan, from real incident reports.
ReplitReplit Agent deleted my database (the SaaStr incident)
Replit Agent deleted your database? The checkpoint rollback often works even when the agent says it can't. Recovery steps from the July 2025 SaaStr incident.
ReplitReplit API key exposed: secrets leaking from a public Repl
Replit API key exposed in a public Repl? Rotate it first, then move secrets to the Secrets pane and behind a server. Based on documented scraping incidents.
Bolt.newBolt.new project disappeared (or chat history gone, or rollback made it worse)
Bolt.new project disappeared? It's usually in your StackBlitz account under another login. Recovery steps plus the rollback database trap, from Bolt's docs.
The Vibe Oops briefing
One email when something ships to production that should not have. New incidents, new error guides, no filler.