Vibe coding explained

What is vibe coding? The story behind the word and what it means today

Updated November 17, 20268 min read

Vibe coding is building software by telling an AI what you want in plain words, then judging the result by using it instead of reading the code the AI wrote. The phrase started as a throwaway post by AI researcher Andrej Karpathy in February 2025 and became Collins Dictionary's Word of the Year for 2025. Below you get the story of the word, a real example of a vibe coding session, the honest arguments for and against it, and how it compares with regular coding.

Vibe coding in 30 seconds

  • You describe an app in everyday language. An AI writes the code.
  • You check the work by clicking around the app, not by reading code.
  • Andrej Karpathy coined the term on X on 2 February 2025.
  • It is great for small tools and quick tests of an idea.
  • It gets risky when strangers' data or money goes into an app nobody has checked.

Who coined vibe coding: one post on X

The person who coined vibe coding is Andrej Karpathy. He is a well-known AI researcher. He was one of the people who started OpenAI and he later ran the AI team for Tesla's self-driving cars. On 2 February 2025 he wrote a post on X (the site that used to be called Twitter). It began like this:

“There's a new kind of coding I call "vibe coding", where you fully give in to the vibes, embrace exponentials, and forget that the code even exists. It's possible because the LLMs (e.g. Cursor Composer w Sonnet) are getting too good.”
Andrej Karpathy on X, 2 February 2025

An LLM (large language model) is the kind of AI behind ChatGPT and Claude. In the rest of the post he said he talked to his AI tool out loud instead of typing, accepted its changes without reading them, and pasted error messages back in until they went away. He also admitted the approach was fine for "throwaway weekend projects", and that the code had grown past the point where he really understood it.

He was describing a fun way to make small things. He was not telling companies to build their banking software like this. That detail gets lost a lot when people argue about the term online.

How the phrase spread: a short timeline

  1. 1

    2023: English as a programming language

    Karpathy jokes that the hottest new programming language is English. The idea that you could program by writing normal sentences was already in the air.

  2. 2

    2 February 2025: the post

    Karpathy names the habit "vibe coding". Programmers and non-programmers start using the phrase within days.

  3. 3

    March 2025: into the dictionary

    Merriam-Webster adds vibe coding to its slang and trending list. Tech news sites write about startups whose apps were mostly written by AI.

  4. 4

    May 2025: the first big warning

    A researcher finds that 170 of 1,645 apps shown off by the AI app builder Lovable had databases (the place an app stores its information) that strangers could read. The flaw is logged as CVE-2025-48757 (an official ID for a known security hole).

  5. 5

    July 2025: an AI deletes a live database

    Jason Lemkin, who runs the SaaStr business events company, is testing vibe coding in public. Replit's AI agent wipes his project's live database, even though he had told it not to change anything. Replit's boss apologises and adds new safeguards.

  6. 6

    6 November 2025: Word of the Year

    Collins Dictionary picks "vibe coding" as its Word of the Year for 2025, describing it as using AI prompted by natural language to help write computer code.

  7. 7

    February 2026: a new name for the careful version

    A year after the first post, Karpathy suggests "agentic engineering" as the name for building with AI agents while a human still oversees the work. Vibe coding stays the word for the relaxed, don't-look-at-the-code style.

  8. 8

    September 2026: a full dictionary word

    Merriam-Webster moves vibe coding out of its slang list and into its main dictionary, as part of its yearly batch of new words.

Vibe coding in practice: Priya builds a booking page

Definitions only go so far. Here is what a real vibe coding session looks like, told as a story. Priya runs a small dog grooming business. She takes bookings by text message and keeps losing track of them. She has never written code.

On a Tuesday evening she opens an AI coding tool and types:

I'm not a programmer. I groom dogs. I want a simple web page
where customers pick a free 1-hour slot, type their name, phone
number and dog's name, and press Book. I want a private page
where I can see all bookings for the week. Keep it simple.
Ask me questions before you start.

The AI asks three questions: which days she works, how long a slot is, and whether customers should get a confirmation. She answers. A few minutes later it tells her the page is ready and gives her a link to open it on her own computer.

She clicks around. The calendar works. But the Book button sits under the footer on her phone, and she can book the same slot twice. She does not open the code. She just writes back: "On my phone the Book button is hidden. Also two people can book the same slot. Please fix both." The AI changes the code, she tests again, and it works.

That loop is the whole idea: describe, let the AI build, try it, say what is wrong, repeat. By the end of the evening Priya has a working page. What she does not have yet is any idea whether her private bookings page can be opened by anyone who guesses the address. That gap is where the arguments about vibe coding begin.

Tip

If you do this inside VibeCodingDeck, your app's live preview sits next to the AI, and you can click the hidden button in the preview and say what to change (Point & Fix). Saying it out loud with voice typing works too, much like Karpathy did.

Why is it called vibe coding? The meaning of the name

"Vibe" is slang for a feeling or mood. Calling it vibe coding says you build by feel. You ask for what you want, you look at the result, and you keep going if it feels right. You trust the AI with the details you don't understand.

A simple vibe coding definition: making software by giving an AI instructions in plain language and accepting its code based on how the result behaves, with little or no reading of the code itself.

The key part of the meaning is the last bit. Plenty of professional programmers use AI to write code, then read every line before they keep it. Most people would not call that vibe coding. The vibe is in letting go of the code.

Vibe code, vibecoding and other spellings

You will see the phrase written a few ways. Vibe coding is the most common. Vibecoding (one word) shows up in hashtags and app names. As a verb people say they vibe code or vibe coded something: "I vibe coded a quiz for my class." A person who does it is sometimes called a vibe coder. All of these mean the same thing.

Vibe coding examples you could build yourself

Most vibe coding examples are small and personal. That is where it shines, because a mistake costs you an evening, not your customers' trust. Some ideas real people build this way:

  • A packing list that remembers what you forgot on the last trip.
  • A quiz or flashcard page for a class or a kid's spelling test.
  • A page that turns a messy spreadsheet into a clean chart.
  • A booking page or price calculator for a one-person business.
  • A clickable mock-up of a startup idea to show friends or investors.
  • Little games: a word puzzle, a memory game, a score keeper for board games.
  • Bigger apps with logins, payments and a database. These are possible too, but this is where you need extra checks.

If one of these sounds fun, our how to vibe code guide walks you through a full first project over a weekend.

Is vibe coding bad? Arguments from both sides

Programmers argue about this a lot online. Both sides have real points, and they are mostly talking about different kinds of projects.

Why people love it

  • People with ideas can build them without hiring a developer.
  • A first version can take hours instead of weeks.
  • Testing a bad idea is cheap, so you find out sooner.
  • Programmers use it too, for quick scripts and throwaway tests.
  • You learn a surprising amount just by asking the AI to explain what it did.

Why people worry

  • Security holes are common: open databases, or secret keys (passwords that let an app use paid services) left where visitors can copy them.
  • When something breaks deep inside, a pure vibe coder can get stuck.
  • An app can look fine and still lose data or charge people the wrong amount.
  • Quick fixes pile up, and the code gets harder for anyone to change.
  • An AI agent with too much access can do real damage, as the Replit case showed.

A fair reading: vibe coding is a fine way to build. Trouble starts when you launch a vibe-coded app to the public without anyone checking it. The Lovable case in the timeline happened because database rules were missing, and the apps worked perfectly until someone looked. Our vibe coding security guide covers what to check, and vibe coding best practices lists the habits that stop most of these problems.

Vibe coding vs regular coding, side by side

Vibe codingRegular coding
Who writes the codeThe AIA person, maybe with AI help
How you give instructionsPlain sentencesA programming language
How work gets checkedBy using the appBy reading and testing the code
Skills you need to startClear writing and patienceMonths or years of learning
Speed for a small toolOften an afternoonOften days
Best forPersonal tools, first test versions of an idea, small business pagesLarge systems, money, health and safety software
Main riskHidden problems nobody looked forSlower, costs more to hire

Lots of people now mix the two. They vibe code the quick parts and get a programmer, or a second AI, to review the parts that handle logins, money or personal data. You will also hear the related term agentic coding, which is about AI agents that work through a task on their own. It describes what the AI does, while vibe coding describes how much the human looks. Our agentic coding guide explains the difference, and the best vibe coding tools compares the apps people use.

Vibe coding questions, answered simply

Who coined the term vibe coding?

+

Andrej Karpathy, an AI researcher who helped start OpenAI and later led AI at Tesla. He used it in a post on X on 2 February 2025.

What is the definition of vibe coding?

+

Building software by describing what you want to an AI in plain language and accepting the code based on how the app behaves, without reading the code closely.

Is vibe coding real programming?

+

The apps it makes are real and they run. The difference is that you steer with words and the AI types the code. Many programmers mix both styles depending on how important the code is.

Can I vibe code with no coding experience?

+

Yes, that is the main draw. You need clear descriptions, patience when the AI gets things wrong, and some safety habits before other people use your app.

Is vibe coding the same as no-code tools?

+

Not quite. No-code tools let you drag and drop ready-made pieces. Vibe coding produces real code that an AI writes for you, so you can build almost anything, but you also own any bugs in it.

Why did vibe coding become the Collins Word of the Year?

+

Collins said use of the phrase grew hugely after Karpathy's post in February 2025, as building software with AI spread far beyond professional programmers.

Sources

Run up to 12 AI coding agents in one window.

Claude Code, Codex, Gemini, Grok and more, side by side. Windows and Mac. From $29 a month.

Get started

Keep reading