Insights / October 25, 2026

What is vibe coding? A definition from the engineers who fix it

Vibe coding is building software by describing what you want to an AI tool in plain language and accepting the code it writes without reading it. You judge the result by whether the app works when you try it, not by reviewing the code behind it.

That makes it the fastest way yet to go from an idea to a working app, and it’s how many of our clients got their first users. It also means nobody has checked the parts of the app you can’t see. We’re the engineers founders call when a vibe-coded app needs to survive real customers.

Where the term “vibe coding” comes from

Andrej Karpathy, a founding member of OpenAI and former head of AI at Tesla, coined the term in a post on X on February 2, 2025. He described a new kind of coding where you give in to the vibes and “forget that the code even exists.”

In the same post he described the workflow: he talked to Cursor’s AI by voice, accepted every change without reading the diffs, pasted error messages back in with no comment, and asked for random changes when a bug wouldn’t go away. He said it was fine for throwaway weekend projects.

The phrase spread fast. Collins Dictionary named “vibe coding” its Word of the Year for 2025.

Vibe coding meaning: then and now

The meaning has stretched. Many people now use “vibe coding” for any app built with an AI app builder like Lovable or Replit, especially by someone who doesn’t write code.

The original meaning is the more useful one. Developer Simon Willison put it plainly: vibe coding is “building software with an LLM without reviewing the code it writes.” If an AI wrote every line but a developer read, tested and understood it, that’s AI-assisted programming, not vibe coding.

So the test isn’t which tool you used. It’s whether anyone reads and owns the code.

How vibe coding works in practice

The loop is the same in every tool:

  1. Describe what you want: “a booking page where clients pick a time and pay a deposit.”
  2. The AI writes or edits the code and shows you a live preview.
  3. You click around. If something’s wrong, you describe it or paste the error.
  4. Repeat until it works. If a change makes things worse, roll back to an earlier version.

At no point do you open the code, and the output adds up fast. On an AI design platform for businesses that a founder prototyped with Replit Agent, his Agent sessions produced more than 1,500 commits, about half the repository’s history. On a media delivery app a non-technical founder built in Lovable, about 99 of every 100 commits still come from Lovable, because the founder keeps building there while we run engineering.

The tools people use for vibe coding

Type Examples What you get
AI app builders in the browser Lovable, Replit, Bolt.new, v0 A hosted app, often with a database and sign-in built in. No setup, no code required
AI coding agents Cursor, Claude Code and similar Edits to a real codebase on your machine. More control, but you need to run the project yourself

App builders are where non-technical founders usually start. Coding agents are where developers vibe code, and where many projects move once they grow. Our guide to the best vibe coding tools compares them in detail.

What vibe coding is great for

  • Prototypes. A clickable, working version of an idea in days instead of months.
  • Validating demand. Put a real product in front of users and find out whether they’ll sign up or pay before spending on engineering.
  • Internal tools. Dashboards and admin screens used by a handful of trusted people, where the data is low-risk.
  • Designing the product. The screens and flows a founder builds this way are usually the best-thought-out part of the app, because they’re the part the founder actually looked at.

Both of the apps above reached real users this way. When we took over, we kept nearly all the screens and flows. The work was underneath.

Where vibe-coded apps break

AI tools optimize for what you can see: does the button work, does the page load. A demo never tests the requests nobody is supposed to make, so the code that blocks them never gets asked for. These are the problems we find most often:

  • Database rules left open. Lovable and Bolt store data in Supabase, which relies on row-level security rules to stop one user reading another’s records. In 2025 a researcher found 170 of 1,645 scanned Lovable apps letting anyone read or change their data. Our article on vibe coding security risks covers the full list.
  • Permissions checked only in the browser. The admin button is hidden, but nothing on the server stops someone calling the action directly.
  • Payments that can be faked. Checkout works once, but the app doesn’t verify that payment notifications really came from Stripe, or handle failed payments and cancellations.
  • Secrets and paid APIs exposed. Keys shipped to the browser, or server functions anyone can call, so a stranger can run up your AI bill.
  • Costs that grow faster than users. On the media delivery app, live updates (45%) and data sent to browsers (41%) made up most of the running costs, because screens subscribed to more changes than they displayed. More in our Lovable Cloud pricing guide.
  • Fix loops. Each prompt fixes one thing and breaks another. With no tests, nobody can tell what changed until a user finds it.
  • No safe way to ship. Changes go straight to the live app, with no staging copy and no review.

None of this means the tools are bad. They build exactly what you ask for.

Vibe coding vs AI-assisted engineering

Professional engineers use the same AI tools. We use them every day. The difference is what happens around the AI.

Vibe coding AI-assisted engineering
Who reads the code Nobody An engineer reviews every change
How changes are checked Clicking around the preview Tests, plus review before merging
Where changes go Straight to the live app A branch, then staging, then production
Database changes Made by the AI as it goes Written as files, reviewed, and run on purpose by a person
Who owns the result The tool’s output, as is A team that can explain and maintain it

How to take a vibe-coded app to production

You don’t need to stop vibe coding to get there. You need someone to own the parts the AI can’t see.

  1. Get the code into a GitHub repository you own. Lovable, Bolt, v0 and Replit can all sync or export to GitHub. Everything else depends on this.
  2. Lock down data and identity. Turn on row-level security for every table, move permission checks to the server, and move secret keys out of the browser.
  3. Make payments verifiable. Verify Stripe webhooks and handle failed payments, upgrades and cancellations.
  4. Add a review step and a staging copy. On the AI design platform, staging and production deploy from separate branches and features reach staging by pull request. The founder kept building in Replit on his own branch, and developers merged his work into staging. Our guide to building in Lovable or Replit after you hire a developer covers the setup.
  5. Replace platform pieces only when there’s a reason. For the AI design platform we replaced Replit Auth and moved file storage from Replit’s object storage to Cloudflare R2. The media delivery app still runs on Lovable Cloud, and its founder still builds in Lovable. Our guide to taking a Replit app to production goes deeper.
  6. Put tests around the flows that make money. Sign-up, payment and the core thing your product does. After that, changes stop being a gamble.
  7. Watch running costs. Check which usage line is growing before you upgrade anything.

If you’re unsure whether your app is worth fixing at all, see rescue or rebuild. Usually it is.

FAQ

Is vibe coding real programming?

It produces real, working code, often lots of it. What’s missing is the understanding: by Karpathy’s own description, the code grows beyond what the person building it has read. That’s fine for a prototype. A product people pay for needs someone who can explain how it works.

Can you build a business on a vibe-coded app?

Yes, and plenty of founders start that way. Vibe coding is a good way to find out whether people want the product. Before you take payments or store personal data, have an engineer review security, payments and deploys. Most of the vibe-coded app usually stays.

Is vibe coding safe?

Building a prototype that way is safe. Shipping it to the public without review often isn’t, because the most common gaps let users see each other’s data or skip payment. A security and payments review before launch closes most of them.

Do professional developers vibe code?

For throwaway experiments, often. For production code, the professional version is AI-assisted engineering: the AI writes, an engineer reviews, tests and owns the result.


If you’ve vibe coded your way to real users and want the parts underneath made solid, that’s what our vibe coding rescue is for.

LET’S TALK.

Book a free 30-minute call with Virgil

Pick a time that suits you. You’ll get a straight answer on what you need, what it should cost and the fastest path to launch.

Loading available times…

Open the calendar in a new tab

Send us your project

Virgil replies personally within one business day.

Book a free strategy call