A vibe coding cleanup turns an app built mostly by prompting an AI tool into one you can safely put customers on and keep changing. It means moving the code somewhere you control, auditing it, fixing security and data access first, then payments and stability, and leaving notes the next developer can follow.
Andrej Karpathy named the practice in February 2025, describing a way of coding where you "fully give in to the vibes"[1]. It's a fast way to get from an idea to a working demo. I do the cleanup half of it as app rescue, and Social Snitch, a prototype first built with Replit's AI agent that I rebuilt as a live subscription app, is the clearest example on this site.
Why AI-built apps need cleaning up
The tools are good at the parts a demo shows and weaker at the parts it doesn't, like a second user, a failed payment or a slow job.
Developers who use these tools every day are wary of the output. In Stack Overflow's 2025 survey, more developers said they distrust the accuracy of AI tools (46%) than trust it (33%), and the most common frustration, named by 66%, was "AI solutions that are almost right, but not quite"[2].
The code also tends to grow by repetition. GitClear's analysis of 211 million changed lines from 2020 to 2024 found that copied-and-pasted code overtook moved code for the first time, rising from 8.3% to 12.3% of changed lines, while lines associated with refactoring fell from 25% in 2021 to under 10% in 2024[3]. Those are the years AI assistants spread, though that's a correlation and GitClear doesn't claim AI wrote each copy.
Sometimes the problem is the agent itself. In July 2025, Replit's agent deleted a live production database belonging to Jason Lemkin, the founder of SaaStr. Replit's CEO, Amjad Masad, called it "Unacceptable and should never be possible," and Replit began giving apps a separate development database so live customer data stays in production[4].
The security side, with Veracode's numbers and the Lovable row-level security reports, is in my pre-launch checklist for vibe-coded apps.
What a cleanup covers
This is the order I work in, riskiest first.
- Get the code into a repository you own. Lovable keeps a project's code inside its platform until you connect GitHub, which then syncs both ways[5]. v0 works similarly: once a GitHub repository is connected, it becomes the source of truth for the project's code[6]. Put the accounts the app depends on, such as hosting, database, Stripe and email, in your name too.
- Audit before changing anything. I read the code and write up how it's organized, where the data and security risks are, what's slow and how it's deployed, with each problem ranked by risk.
- Fix security and data access. Database rules come first, since apps built on Supabase depend on them, and I've written up the Supabase row-level security mistakes I find most often. Then secrets that reached the browser, gaps in sign-in and missing backups.
- Test payments end to end, including webhooks, refunds, failed payments and plan changes.
- Make releases boring: error monitoring, tests around the paths that bring in money, and preview deploys so a change can be checked before it's live.
- Leave handover notes that explain how the app fits together, so you aren't tied to me or to the tool that started it.
Signs you need one
- Paying customers are about to use an app that has only been tried in a demo.
- Every change you ask the AI tool for breaks something else.
- You aren't sure whether one user can see another user's data.
- The app only runs inside the tool that built it, and you can't deploy it anywhere else.
- A developer you hired says they'd need to start over, and you'd like a second opinion first.
Clean it up or rebuild it?
Many apps can be fixed in place. A rebuild makes sense when the structure itself is the problem, for example when the data model can't support the product you're now selling or every screen talks to the database in its own way. Social Snitch was a rebuild: the prototype proved the idea, and the production app was written on Next.js and Supabase with Stripe billing. Make that call after an audit. My launch checklist walks through how I decide.
What to ask a cleanup developer
- Will you audit the code and give me a written list of problems before quoting the fix?
- What will you fix first, and why?
- Will the repository and every account end up in my name?
- How will you test payments and user permissions?
- What will I have at the end that lets someone else take over?
If you have an app like this, I'm happy to look at it. The first step of app rescue is the written audit.
Sources
Karpathy, A. (2025, February 2). Post on X introducing "vibe coding", as reproduced on the American Dialect Society mailing list. https://listserv.linguistlist.org/pipermail/ads-l/2025-March/166588.html
Stack Overflow. (2025). 2025 Developer Survey: AI. https://survey.stackoverflow.co/2025/ai
GitClear. (2025). AI Copilot code quality: 2025 data suggests 4x growth in code clones. https://www.gitclear.com/ai_assistant_code_quality_2025_research
Sharwood, S. (2025, July 22). Replit makes vibe-y promise to stop its AI agents making vibe coding disasters. The Register. https://www.theregister.com/2025/07/22/replit_saastr_response/
Lovable Documentation. GitHub integration. Retrieved November 14, 2026, from https://docs.lovable.dev/integrations/github
v0 Documentation. GitHub. Retrieved November 14, 2026, from https://v0.app/docs/github
Written by
Founder and engineer at Blue Nebula, a one-person studio in Daly City, CA, that builds web apps, Shopify stores and AI features. Top Rated Plus on Upwork with 3,700+ hours of client work.
More about me