What Is Vibe Coding? Where It Works and Where It Breaks

Vibe coding is building software by describing it to an AI and using the code it writes without reading it. Here is where that works and where it fails.

Firevibe Team13 min read

Vibe coding means building software by describing what you want to an AI in plain words and using the code it writes without reading or understanding that code yourself. Andrej Karpathy coined the term in a post on X in February 2025. It works well for prototypes, personal tools and simple apps you can fully test by using them. It breaks down when nobody checks security, when the app holds data you cannot afford to lose, and when nobody understands the code well enough to fix it.

What does vibe coding mean?

Vibe coding is writing software through prompts instead of through code. You say what the app should do, the AI writes it, you run it, and when something is wrong you describe the problem rather than open the file. Karpathy put it this way in his 2025 year in review: AI had become able "to build all kinds of impressive programs simply via English, forgetting that the code even exists." He added that with vibe coding, "programming is not strictly reserved for highly trained professionals, it is something anyone can do."

Stack Overflow used a plainer definition when it asked about it in its 2025 Developer Survey: "the process of generating software from LLM prompts."

In practice people use the word two ways: for any AI-assisted coding, or in the original sense, where you accept what the AI writes and judge it only by whether the app behaves. This post uses the second, because that is the sense that changes who can build software and what can go wrong.

Where did the term come from?

The term came from a single post on X by Andrej Karpathy, published on February 2, 2025. In his year in review, dated December 19, 2025, he wrote: "Amusingly, I coined the term 'vibe coding' in this shower of thoughts tweet totally oblivious to how far it would go."

A few months after that post he tried it on a real product. In Vibe coding MenuGen, dated April 27, 2025, he describes an app where "you take a picture of a menu and it generates images for all the menu items." He wrote that "100% of the code was written by Cursor+Claude" and that he did not really know how the app worked "in the conventional sense." It is a clear first-hand account of where vibe coding is easy and where it gets hard.

What is the difference between an AI code editor and an AI app builder?

An AI code editor helps you write code that you keep and run yourself. An AI app builder takes a description and gives you a running app, with the hosting and the backend handled for you. Both can be used to vibe code, but they leave you different jobs.

AI code editor or coding agentAI app builder
ExamplesCursor, Claude CodeLovable, Bolt, Firevibe
What you start fromA project on your computer or in your repositoryA description of the app
Who sets up servers, database and sign-inYouThe builder
How the app goes liveYou choose and set up hostingThe builder publishes it
Best suited toPeople who will look after a codebasePeople who want the app, not the code

Here is how each vendor describes its product, as of November 2026:

  • Cursor calls itself "a coding agent for building ambitious software" and you download it to your computer to work on your codebase.
  • Claude Code is described as "an agentic coding tool that reads your codebase, edits files, runs commands, and integrates with your development tools."
  • Lovable says it "generates a working application that includes frontend, backend, database, authentication, and integrations," and that you can publish it to a live URL.
  • Bolt says "Create stunning apps & websites by chatting with AI," and that Bolt Cloud provides "hosting, databases, integrations, and more."

The difference shows up in Karpathy's MenuGen story. The local prototype, built in Cursor, "took very little time." Getting it live was another matter: he summed it up as "exhilarating and fun escapade as a local demo, but a bit of a painful slog as a deployed, real app," listing "services, docs, API keys, configurations, dev/prod deployments, team and security features, rate limits, pricing tiers." Much of that glue work is what app builders take on for you. For what a builder's backend really includes, see Do AI App Builders Give You a Real Backend?.

Who is doing vibe coding?

The primary data points to two groups: a large share of people at work who are not developers, and a minority of professional developers.

People without a programming background

A survey run by Centiment for Zapier was fielded from May 8 to May 11, 2026, with 818 completed responses from U.S. workers who had personally built or deployed a working tool for their job in the previous 12 months using AI coding tools. The data is unweighted, with a margin of error of about 4 points at 95% confidence. Zapier sells tools for building with AI and promotes them in the same article, so read this as a vendor's survey. Its main findings:

  • 34% of the people building with AI tools at work have no formal programming background, which Zapier defines as no college coursework in it and no past job as a developer or engineer.
  • The most common things they build are data analysis or visualization tools (41%), forms, surveys or data collection tools (39%), and AI chatbots or assistants (37%).
  • 56% of these non-traditional builders are making something that customers or the general public will see. 44% build only for internal use.
  • 54% say most or all of the tools they built are still in use.
  • 92% of those without formal experience have run into a major challenge coding with AI. The most common were code errors or bugs (38%), security and data privacy concerns (37%), and incorrect or unusable outputs (29%).

Professional developers

The 2025 Stack Overflow Developer Survey asked directly: "In your own words, is 'vibe coding' part of your professional development work?" Of the 26,564 people who answered, 72.2% said no and another 5.3% said no emphatically. About 15% said yes in some form, and 2.1% said they had tried it. The survey ran from May 29 to June 23, 2025, and its methodology page says it used 49,009 responses, recruited mainly through Stack Overflow's own channels.

The same survey shows heavy use without much trust: 84% of respondents were using or planning to use AI tools, yet only 3.1% said they highly trust the accuracy of AI output, while 45.7% said they somewhat or highly distrust it (33,244 answers). In the 2026 survey results, based on more than 30,000 people, Stack Overflow reports that "73% of respondents who indicate using AI coding assistants/agents use them daily."

Read together, the two surveys suggest that most professional developers do not call their work vibe coding, while many people outside engineering now build working tools with AI, more than half of them for an outside audience.

Where does vibe coding work well?

Vibe coding works best when you can tell whether the app is right just by using it, and when a mistake costs little. Good fits:

  • Prototypes. A clickable version of an idea to show people before anyone spends real money on it.
  • Personal and small-team tools. A tracker, a calculator, a form that feeds a list, a dashboard over numbers you already have.
  • Simple public sites. A business site, a portfolio, an event page, where the content is public anyway.
  • Throwaway tools. Karpathy wrote that he built "entire ephemeral apps just to find a single bug," because code had become "free, ephemeral, malleable, discardable after single use."

In each case the result is easy to check: if a chart shows the wrong total, you see it. How to Write a Prompt That Builds the App You Want covers what to put in the first message.

Where does vibe coding break?

Vibe coding breaks where the important part of the app is invisible when you click around: who can see what, what happens to stored data, and whether anyone can fix the app later.

Security and privacy

Security is the risk you cannot test by looking at the screen. An app can look perfect while one user can open another user's records, or while a secret key sits in code that runs in the browser. In the Zapier survey, 37% of non-traditional builders named security and data privacy concerns as a challenge they hit. Stack Overflow's respondents are cautious too: in its 2025 survey, more respondents distrusted the accuracy of AI output than trusted it.

Data you cannot afford to lose

Vibe coding is risky for data that has no other copy or that costs money when it goes wrong: payments, orders, customer records, anything you must keep by law. A prompt that says "clean up old entries" can be read more broadly than you meant. Keep this kind of data in a place you understand, and test every path that changes or deletes it.

Apps nobody can maintain

An app nobody understands is hard to fix when it fails. Karpathy wrote that AI models "make subtle but critical design mistakes when you watch them closely, and sometimes they hallucinate or gaslight you about solutions." In April 2025 he concluded that "vibe coding full web apps today is kind of messy and not a good idea for anything of actual importance," while adding that he saw "clear hints of greatness." By December 2025 he wrote that "Vibe coding will terraform software and alter job descriptions." Either way, if the app matters, someone has to be able to read it, or the tool that built it has to keep changing it safely.

What should you check before customers use an app you vibe coded?

Before customers use it, check the things you cannot see by clicking around as yourself:

  1. Create two test accounts and confirm that each one sees only its own data.
  2. Sign out and open the app's pages and links directly. Anything private should ask you to sign in.
  3. Find out where the data is stored, whose account it sits in, and what happens to it if you stop paying for the tool.
  4. Make sure secret keys (for payments, email or AI) live on the server, never in the browser or in the phone app.
  5. Test every action that moves money or deletes data, including what happens when it fails halfway.
  6. List the personal data the app collects and publish a privacy policy that matches it.
  7. Decide who will fix the app when it breaks, and confirm that person or tool can read and change the code.
  8. Launch to a small group first, and watch what they actually do.

Where does Firevibe fit?

We make Firevibe, an AI app builder: you describe what you want in plain words, an AI agent builds it, and you change it by asking in chat. You choose one of three kinds of project before you start: a website or web app, a mobile app for iPhone and Android, or a mobile app design.

Every website and mobile app comes with a backend, a database, sign-in and file storage, built and connected for you, which covers much of the glue work Karpathy describes. Web apps are real React and TypeScript, you watch a live preview as it builds, and you can change things by chat or by pointing at an element on the preview. Mobile apps are React Native with Expo, and you open them on your own phone through Expo Go by scanning a QR code.

The limits, as of November 2026:

  • On paid plans you can read the full source code in the workspace, but you cannot download or export the web code.
  • Web app sign-in is email and password.
  • Publishing a website needs a paid plan (Starter and up), and connecting your own domain needs Pro. Publishing a mobile app needs Pro.
  • The mobile app builder is new in November 2026. iPhone is the platform it is built and tested for first; the same app runs on Android, but sending it to Google Play from Firevibe is not available yet.
  • For the App Store, on Pro, Firevibe hands the app to Expo's build service under your own Expo account. You finish there with your own Apple developer account and submit for review yourself.

The checklist above applies to Firevibe apps too. To try it, sign up free with no credit card; the free plan includes 200 credits, once.


Frequently asked questions

Who coined the term vibe coding? Andrej Karpathy coined the term in a post on X in February 2025. In his 2025 year in review he wrote that he coined it in a 'shower of thoughts' tweet, without expecting it to spread as far as it did.

Is vibe coding the same as using an AI coding assistant? Not quite. Vibe coding means building by prompts and accepting the AI's code without working through it yourself, while AI-assisted coding can also mean a developer who reads and reviews every change. In the 2025 Stack Overflow Developer Survey, 72% of the 26,564 people who answered said vibe coding was not part of their professional work.

Do you need to know how to code to vibe code? No. You describe what you want in plain words and the AI writes the code. Some basic knowledge still helps you test the result, check who can see which data, and describe problems clearly.

Is vibe coding safe for an app that holds customer data? It can be, but only if someone checks it before customers arrive. At a minimum, test that each user sees only their own data, keep secret keys off the browser and the phone, and know where the data is stored and whose account it sits in.

What is the difference between an AI code editor and an AI app builder? An AI code editor or coding agent, such as Cursor or Claude Code, works on a codebase that you keep and run yourself, including where it is hosted. An AI app builder, such as Lovable, Bolt or Firevibe, takes a description and builds, hosts and runs the app for you.

Generate any product

Build web apps, mobile apps, SaaS, internal tools, marketplaces and more.

Start for free