Two meanings of the word
Karpathy meant a way of working where you "fully give in to the vibes" and "forget that the code even exists". Simon Willison, writing on March 19, 2025, keeps that strict sense: "building software with an LLM without reviewing the code it writes". He adds that code you review, test and can explain is software development, whatever tool wrote it. Source. Wording via Wikipedia's transcription of the post.
Collins Dictionary defines the term more widely, as "the use of artificial intelligence prompted by natural language to assist with the writing of computer code". When an article says vibe coding, check which of the two it means. The risks below apply to the strict one. Source.
Where the term came from
- February 2, 2025
- Andrej Karpathy posts on X about "a new kind of coding I call vibe coding", describing his own work with Cursor Composer and Sonnet. He calls it "not too bad for throwaway weekend projects, but still quite amusing". Andrej Karpathy, post on X Wording via Wikipedia's transcription of the post.
- March 19, 2025
- Simon Willison argues that vibe coding is not the same as writing code with the help of LLMs, and ties the word to code that nobody reviews. Simon Willison, "Not all AI-assisted programming is vibe coding"
- November 6, 2025
- Collins Dictionary names vibe coding its Word of the Year for 2025. CNN Business, "Vibe coding named Collins Dictionary's Word of the Year" (syndicated by KVIA)
What it looks like in practice
Karpathy described his own loop in the original post. It has four steps. Source. Wording via Wikipedia's transcription of the post.
- Ask for a change in plain words, by voice or text. His examples include "decrease the padding on the sidebar by half".
- Accept every change. In his words: "I 'Accept All' always, I don't read the diffs anymore."
- When an error appears, paste it back with no comment. "Usually that fixes it."
- When the model cannot fix a bug, work around it or ask for random changes until it goes away.
That is one developer describing one tool in early 2025. The tools in use today are on the tools page.
What vibe coding does not solve
- You lose track of the code. Karpathy wrote that the code "grows beyond my usual comprehension". That is the trade, stated by the person who named it. Source. Wording via Wikipedia's transcription of the post.
- Working code can still be unsafe. In a Veracode study published July 30, 2025, more than 100 LLMs completed 80 coding tasks. Veracode reports that "while AI produces functional code, it introduces security vulnerabilities in 45 percent of cases". Source.
- Feeling faster is not being faster. In a METR randomized trial published July 10, 2025, 16 experienced open-source developers took 19% longer on 246 tasks when AI tools were allowed, and afterwards still believed AI had sped them up by 20%. That study tested AI-assisted work in mature codebases, not vibe coding, and METR now calls its result out of date and has published newer data from February 2026, which we have not read. Source.