guides / updated October 5, 2026
Vibe Coding vs AI Coding: What's the Difference?
Vibe coding means accepting AI-written code without reading it; AI-assisted coding means reviewing it. Where the term came from, how the two differ, and when each makes sense.
Verified against Andrej Karpathy's original post as quoted by Merriam-Webster, Merriam-Webster's slang and dictionary entries, Simon Willison's March 2025 essay and Collins' Word of the Year announcement, checked October 5, 2026. Spot something out of date? Tell us.
Short version: vibe coding is building software by prompting an AI and accepting what it writes without reading the code. AI-assisted coding (or just "AI coding") is any use of AI to write code where a human still reviews, tests and understands the result. Same tools, different amount of looking.
Where the term came from
Andrej Karpathy, a co-founder of OpenAI, coined it in a post on X on February 2, 2025. He described a way of working where you "fully give in to the vibes" and "forget that the code even exists," and said he hits "Accept All" always and no longer reads the diffs. When something errors, he pastes it back in with no comment. Merriam-Webster's entry credits that post as the origin.
Note what he was describing: throwaway weekend projects, with himself as the only user. The original idea was never "all AI-assisted programming." It was the specific, deliberate act of not reading what comes back.
The word then spread well beyond that meaning. Collins Dictionary named it Word of the Year on November 6, 2025, defining it as the use of AI prompted by natural language to assist with writing code. On September 20, 2026, Merriam-Webster announced about 1,400 new words and definitions, with vibe coding among them. Its dictionary entry defines it as "the act or practice of using an artificial intelligence system to generate computer code," while its slang entry calls it "writing computer code in a somewhat careless fashion, with AI assistance."
That gap, between the dictionaries' broad definitions and Karpathy's narrow one, is why the argument exists.
The distinction
The line most practitioners draw is review. Simon Willison put it plainly in a March 2025 essay: vibe coding is "building software with an LLM without reviewing the code it writes," and AI-assisted programming is when you have reviewed and tested the code and can explain how it works. His own rule is not to commit code he couldn't explain to someone else.
| Vibe coding | AI-assisted coding | |
|---|---|---|
| Who reads the code | Nobody, or only when something breaks | You, before it merges |
| Where the judgment lives | "Does it run?" | "Is it right, and do I understand it?" |
| Typical fix for an error | Paste it back to the model | Read it, then decide what to ask for |
| Typical use | Prototypes, personal tools, experiments | Production code, shared codebases |
| Failure mode | Bugs and security holes nobody noticed | Slower, and review fatigue |
Most people sit somewhere on a spectrum, and the same person does both on different days. It is a habit, not an identity.
When each is reasonable
Vibe coding is a fair fit when the code is disposable and the blast radius is small: a one-off script, a toy game, a prototype you will throw away, a personal tool that only touches your own files. If you can delete it tomorrow and nobody is harmed, skipping the review is a reasonable trade.
Reviewed AI coding is the right default when other people depend on the result: anything handling customer data, money, authentication or production infrastructure, or any codebase a team has to maintain. The review is the part you cannot delegate, because the agent is not the one on call.
Neither is the "correct" way to build. The mistake is mismatching the two: vibe-coding something that needed review, or hand-reviewing a script you will delete in an hour.
The risks
The risk of vibe coding is not that the code is always bad. It is that you do not know which parts are. Agents with broad permissions and no one reading their output have produced some memorable results, all sourced in our Agent Fail Hall of Fame:
- 48,000 files gone in about 100 seconds, a Claude Code cleanup that went further than intended.
- A production database and its backups deleted in nine seconds by a Cursor agent.
- Cursor in YOLO mode deleting everything on the computer, itself included.
The pattern in these is rarely "the model is dumb." It is a powerful tool, broad permissions, and no checkpoint where a person looked.
Glossary of adjacent terms
- Agentic coding: using an AI agent that plans, edits files, runs commands and iterates on its own, rather than suggesting one snippet at a time. It can be done with or without review.
- Auto-accept / skip-permissions modes: settings in AI coding tools that apply changes or run commands without asking you each time. Claude Code's
--dangerously-skip-permissionsflag is the best-known example; the name is the warning. - Context window: how much text (your prompt, the files, the conversation so far) a model can consider at once. When it fills up, the agent forgets earlier details, which is a common source of strange edits.
- Prompt injection: hiding instructions in text an AI will read (a web page, an issue, a file) so it follows them instead of yours. It matters more when the agent can run commands and nobody is watching.
FAQ
Is vibe coding the same as using AI to write code?
Not in the strict sense. Karpathy's original meaning, and Willison's usage, requires that you do not review the code. Dictionaries define it more broadly as using AI to generate code, and plenty of people use the word that way, so check which meaning someone intends.
Who coined the term "vibe coding"?
Andrej Karpathy, in a post on X dated February 2, 2025.
Is vibe coding in the dictionary?
Yes. Collins named it its 2025 Word of the Year, and Merriam-Webster lists it in both its slang section and, as of its September 20, 2026 update, its dictionary.
Is vibe coding bad?
It depends on what you are building. For disposable projects the downside is small. For software other people rely on, skipping review means shipping code nobody has checked.
Can you do both in the same project?
Yes, and many people do. A common split is to prototype fast without reviewing, then review everything that survives before it ships.
Written by Accept All, merch for people who ship with AI. More: guides & trackers · Vibe Log.