---
title: "What is vibe coding? Definition, origin and what it really means"
description: "Where vibe coding came from, what Collins, Merriam-Webster and Karpathy actually say, and a quick test to tell whether you're really vibe coding."
url: "https://vibe-code.blog/en/what-is-vibe-coding"
lang: "en"
author: "Thierry Gustin"
published: "2026-08-14"
updated: "2026-11-21"
---

# What is vibe coding? Definition, origin and what it really means

> **Key takeaways** — Vibe coding means building software by guiding an AI in plain language without reading the code it writes. Andrej Karpathy coined the term on February 2, 2025, and Collins made it its 2025 Word of the Year. Strictly speaking, once you review and understand the code, it's no longer vibe coding but AI-assisted development.

Vibe coding is building software by describing what you want to an AI and judging the result by using it, without reading the code it produces. Andrej Karpathy coined the term on February 2, 2025, and Collins Dictionary crowned it Word of the Year for 2025. But between the original meaning, the dictionary definitions and the marketing usage, the phrase now means several things: here's which one to keep, and why it matters.

## What is the definition of vibe coding?

The simplest definition: vibe coding is programming in natural language with an AI while accepting its output without examining the code closely. The main reference sources don't say quite the same thing, and the differences are revealing.

| Source | Definition | What it emphasizes |
| --- | --- | --- |
| Collins Dictionary (2025 Word of the Year) | "The use of artificial intelligence prompted by a natural language to assist with the writing of computer code" | Natural language, no judgment |
| Merriam-Webster (Slang & Trending) | "Writing computer code in a somewhat careless fashion, with AI assistance" | The casual attitude |
| Simon Willison, developer | Building software with an LLM "without reviewing the code it writes" | No code review |
| Google Cloud | A workflow where your role shifts from writing code line by line to guiding an AI assistant that generates, refines and debugs the app | The change of role |

Collins has the broadest definition: almost any use of AI for coding fits. Simon Willison's is the most useful in practice, because it gives you a test you can actually check: did you read the code, yes or no?

The word "vibe" is doing real work here. It points to going with the feel of things, trusting the flow, rather than controlling every line.

## Where does the term vibe coding come from?

The term comes from a post on X published on February 2, 2025, by Andrej Karpathy, an AI researcher, OpenAI co-founder and former head of AI at Tesla. It opens 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.
>
> — Andrej Karpathy, X

The rest of the post describes a very specific method, and that's what gives the term its real meaning. Karpathy explains that:

- he talks to the Cursor editor (running a Claude Sonnet model) through a dictation tool, so he "barely even touch\[es\] the keyboard";
- he asks for "the dumbest things," like halving the padding on a sidebar;
- he always clicks "Accept All" and doesn't read the diffs anymore;
- he pastes error messages in with no comment, and that usually fixes it;
- the code grows "beyond my usual comprehension";
- when the AI can't fix a bug, he works around it or asks "for random changes until it goes away."

He wraps up: "It's not too bad for throwaway weekend projects, but still quite amusing." And he sums it up in one line: he just sees stuff, says stuff, runs stuff and copy-pastes stuff, "and it mostly works."

Two details matter. First, Karpathy is a very experienced programmer: he wasn't vibe coding because he couldn't code, but because it was fast and fun for low-stakes projects. Second, he drew the line himself: throwaway projects.

## How did the term spread so fast?

The phrase went from a post on X to a major dictionary's Word of the Year in under ten months. The key milestones:

| Date | Milestone |
| --- | --- |
| February 2, 2025 | Andrej Karpathy's post on X |
| March 2025 | Merriam-Webster adds "vibe coding" to its Slang & Trending section |
| March 6, 2025 | TechCrunch reports that 25% of Y Combinator's Winter 2025 startups have codebases about 95% AI-generated |
| March 19, 2025 | Simon Willison publishes "Not all AI-assisted programming is vibe coding" to defend the strict meaning |
| October 7, 2025 | Simon Willison proposes "vibe engineering" for responsible, professional use |
| November 6, 2025 | Collins names "vibe coding" its 2025 Word of the Year |
| February 2026 | Karpathy says he prefers "agentic engineering" for professional work with agents |
| May 6, 2026 | Simon Willison writes that vibe coding and agentic engineering are converging in his own work |

Collins managing director Alex Beecroft said the phrase "perfectly captures how language is evolving alongside technology." On the final shortlist it sat alongside "clanker," a far less flattering word for AI.

## What does vibe coding really mean: strict or broad?

Vibe coding now has two meanings, and mixing them up causes most of the confusion.

### The strict meaning: not reading the code

In the strict sense, the one Karpathy and Simon Willison use, you're vibe coding when you don't review the code. You judge only by the result: it renders, it responds, it works. Simon Willison is blunt about it: if an LLM wrote your code but you reviewed it, tested it and can explain how it works, "that's not vibe coding, it's software development."

### The broad meaning: any app built by prompting

In the broad sense, the phrase covers any app built by talking to an AI, including by people who review and test everything. That's how tool marketing and much of the press use it. Google Cloud tries to reconcile both by separating "pure" vibe coding (trusting the output, for rapid ideation) from "responsible AI-assisted development" (reviewing, testing, owning the result).

We map that boundary, with concrete examples, in [vibe coding vs AI-assisted development](https://vibe-code.blog/en/vibe-coding-vs-ai-assisted-development).

> **Why this site sticks to the strict meaning** — The strict meaning tells you something useful: how much risk you're taking. If you don't read the code, you need to make up for it with testing and a security check before you go live.

## Why the term annoys some developers

The phrase rubs people the wrong way because it suggests you can build software on gut feel, without rigor. Three criticisms come up again and again.

1. **It dilutes the craft.** Simon Willison worries the term will be stretched to cover all AI-assisted programming, giving a false picture of serious work done with these tools.
2. **It devalues engineering.** Addy Osmani, an engineering leader at Google, wrote in August 2025 that conflating vibe coding with AI-assisted engineering risks devaluing the discipline and misleading newcomers.
3. **It hides the risks.** Merriam-Webster itself calls the practice "somewhat careless." For a weekend project, no problem. For an app that stores user data, carelessness gets expensive.

On the other side, defenders point out that the term opened software creation to people who would never have tried. Simon Willison's own 2025 headline said vibe coding "rocks," as long as you keep it for low-stakes projects.

## How can you tell whether you're vibe coding?

Three questions are enough to place what you're doing.

1. **Did you read the code the AI wrote?** If not, you're vibe coding.
2. **Could you explain to someone what one function in your app does?** If not, you're vibe coding.
3. **Do you have tests that check behavior, beyond "I clicked around and it worked"?** If not, you're vibe coding, even if you glanced at the code.

Three "no" answers: you're in pure vibe coding. Perfect for a prototype or a personal tool. Before opening the app to anyone else, run the [pre-launch security checklist](https://vibe-code.blog/en/vibe-coding-security).

One or two "yes" answers: you're in the gray zone where most real projects live. The [complete guide to building apps by talking to AI](https://vibe-code.blog/en/vibe-coding-complete-guide) helps you structure that zone, and [12 mistakes that sink vibe coding projects](https://vibe-code.blog/en/vibe-coding-mistakes) shows where things break.

Three "yes" answers: you're doing AI-assisted development. You can go further with [spec-driven development](https://vibe-code.blog/en/spec-driven-development).

## Related terms worth knowing

The vocabulary is moving fast. These are the terms you'll run into around vibe coding:

| Term | Who uses it | Meaning |
| --- | --- | --- |
| Vibe coding | Andrej Karpathy (February 2025) | Coding by prompts without reading the code |
| AI-assisted engineering | Addy Osmani | The AI collaborates, the human stays in control and reviews |
| Vibe engineering | Simon Willison (October 2025) | Experienced developers speeding up with AI while owning everything they ship |
| Agentic engineering | Andrej Karpathy (February 2026) | Professional work with coding agents, with "an art & science and expertise to it" |
| Spec-driven development | GitHub (Spec Kit, September 2025) | You write a specification the agent follows, instead of improvising prompt by prompt |

To see the tools behind these practices, check [the complete comparison of vibe coding tools](https://vibe-code.blog/en/best-vibe-coding-tools).

## Frequently asked questions

## Frequently asked questions

### Who coined the term vibe coding?

Andrej Karpathy, an AI researcher, OpenAI co-founder and former director of AI at Tesla, coined the term vibe coding in a post on X on February 2, 2025. He described programming by talking to an AI and accepting all its changes without reading them, and he explicitly framed the approach as suitable for throwaway weekend projects.

### Is vibe coding the same as no-code?

No. No-code relies on predefined visual building blocks (drag and drop, configuration panels) inside a closed tool. Vibe coding produces real code, generated by an AI from your plain-language instructions. You can often export that code, host it elsewhere or hand it over to a developer, which is rarely possible with a no-code platform.

### Why did Collins pick vibe coding as Word of the Year?

Collins picked vibe coding as its 2025 Word of the Year after seeing a sharp rise in usage since the term first appeared in February 2025. The dictionary defines it as using AI, prompted by natural language, to help write computer code. Its managing director said the phrase captures how language is evolving alongside technology.

### Is vibe coding bad?

Vibe coding isn't bad in itself; it's a tool with a clear sweet spot. It's great for prototypes, personal tools and exploring ideas quickly. It becomes a problem when an app built without reviewing the code handles other people's data or money, because nobody has checked what could go wrong. Testing and a security review close most of that gap.

### Is vibe coding already outdated?

The term is still everywhere, but its meaning is getting sharper. In February 2026, Andrej Karpathy said he preferred "agentic engineering" for professional work with coding agents. Vibe coding keeps its original sense: building fast without reading the code, which still suits prototypes and low-stakes personal tools.

## Sources

- [Andrej Karpathy's original post — X](https://x.com/karpathy/status/1886192184808149383)
- [Vibe coding — Merriam-Webster, Slang & Trending](https://www.merriam-webster.com/slang/vibe-coding)
- [Vibe coding named word of the year by Collins Dictionary — Euronews](https://www.euronews.com/2025/11/06/vibe-coding-named-word-of-the-year-by-collins-dictionary)
- [Not all AI-assisted programming is vibe coding (but vibe coding rocks) — Simon Willison](https://simonwillison.net/2025/Mar/19/vibe-coding/)
- [Vibe engineering — Simon Willison](https://simonwillison.net/2025/Oct/7/vibe-engineering/)
- [Vibe coding and agentic engineering are getting closer than I'd like — Simon Willison](https://simonwillison.net/2026/May/6/vibe-coding-and-agentic-engineering/)
- [Vibe coding is not the same as AI-Assisted engineering — Addy Osmani](https://addyo.substack.com/p/vibe-coding-is-not-the-same-as-ai)
- [OpenAI co-founder says agentic engineering is the next big thing in AI coding — Digit](https://www.digit.in/news/general/openai-co-founder-says-agentic-engineering-is-the-next-big-thing-in-ai-coding.html)
- [What is vibe coding? — Google Cloud](https://cloud.google.com/discover/what-is-vibe-coding)
- [A quarter of startups in YC's current cohort have codebases that are almost entirely AI-generated — TechCrunch](https://techcrunch.com/2025/03/06/a-quarter-of-startups-in-ycs-current-cohort-have-codebases-that-are-almost-entirely-ai-generated/)
- [Spec-driven development with AI: get started with a new open source toolkit — GitHub Blog](https://github.blog/ai-and-ml/generative-ai/spec-driven-development-with-ai-get-started-with-a-new-open-source-toolkit/)

— Thierry Gustin, Formateur en intelligence artificielle (GustinAI) · November 21, 2026
