AgentdexBlog · · Agentdex Editorial
Andrej Karpathy and Vibe Coding: What He Said and What Changed (2026)
"Vibe coding" started as a single post. On February 2, 2025, Andrej Karpathy, a founding member of OpenAI and former head of AI for Tesla Autopilot, described a new way of building software where you talk to an AI, accept what it writes and stop reading the code. The phrase spread fast, became Collins Dictionary's Word of the Year for 2025, and is now the name for a whole category of tools. This guide covers what Karpathy actually said, what he meant, how his view has evolved and what it means for how you build. Sources were checked on October 24, 2026.
Key Takeaways
- Karpathy coined "vibe coding" on February 2, 2025, describing coding where you "fully give in to the vibes, embrace exponentials, and forget that the code even exists."
- He meant it for low-stakes work. In the same post he said it was "not too bad for throwaway weekend projects."
- His own workflow was Cursor (Agentdex profile)'s Composer with a Claude Sonnet model, talking by voice through SuperWhisper, hitting "Accept All" and pasting error messages back without comment.
- In February 2026 he named "agentic engineering" his preferred term for serious AI-assisted development, saying "there is an art & science and expertise to it."
- The lesson: vibe coding is a great way to prototype, but production software still needs review, tests and judgment.
Who is Andrej Karpathy?
Karpathy is one of the best-known researchers and teachers in AI. He was a founding member of OpenAI in 2015, led the AI team for Tesla's Autopilot, and returned to OpenAI briefly before leaving to start Eureka Labs, which he describes as an AI-native school. Many developers know him from his free deep learning lectures and open-source projects. When he describes a shift in how software is written, people listen, which is a big part of why "vibe coding" caught on.
What Karpathy actually said
The original post on X described a style of coding he'd been trying. The key lines:
- "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."
- He said it was possible because the models had become good enough, naming Cursor Composer with Sonnet, and that he barely touched the keyboard, talking to Composer through SuperWhisper instead.
- He described clicking "Accept All" without reading the diffs, copying error messages back in with no comment, and asking for small changes he was too lazy to find himself.
- When the AI couldn't fix a bug, he'd work around it or ask for random changes until it went away.
- He was clear about the limits: "It's not too bad for throwaway weekend projects, but still quite amusing."
In other words, the original idea was half confession, half observation. It wasn't a recommendation to build production systems this way.
Why the term took off
The timing was right. AI editors like Cursor and Windsurf, and app builders like Bolt (Agentdex profile), Lovable (Agentdex profile) and v0 (Agentdex profile), had just made it possible for people with little coding experience to build working apps from prompts. "Vibe coding" gave that experience a name. Within months, startups were marketing themselves as vibe coding tools, and Collins Dictionary named it Word of the Year for 2025. For a full definition and how it works in practice, see what is vibe coding.
How his view has evolved
Karpathy has continued to talk about AI-assisted programming, and his position has become more nuanced. In February 2026, about a year after the original post, Business Insider reported that he'd settled on "agentic engineering" as his favourite term for the professional version: you orchestrate AI agents that write the code, but you remain responsible for the design, the oversight and the result. As he put it, "there is an art & science and expertise to it."
That distinction is useful:
| Vibe coding | Agentic engineering | |
|---|---|---|
| Goal | Get something working fast | Ship reliable software with AI agents |
| Reading the code | Optional, often skipped | Expected, at least at review time |
| Testing | Try it and see | Tests, checks and reviews |
| Best for | Prototypes, personal tools, weekend projects | Production apps, team codebases, anything with users' data |
| Skill needed | Clear descriptions of what you want | Architecture, specs, review and debugging |
What this means for AI coders
Karpathy's own framing gives you a simple rule: match the method to the stakes. A few practical habits come straight from that:
- Vibe freely on throwaway work. Prototypes, internal tools and experiments are exactly what the original post described.
- Switch modes before real users arrive. Once an app handles logins, payments or personal data, read the code that matters, add tests and review security. Our guide to AI-generated code covers what to check.
- Give the AI context. Rules files like .cursorrules and CLAUDE.md make agents more reliable. See how to write agent rules.
- Use Git as your safety net. Commit before every big AI change so "Accept All" is always reversible.
- Pick tools for your level. App builders suit non-developers. Agents like Claude Code (Agentdex profile) and Cursor suit people who will review the code. Browse our vibe coding tools roundup.
The free Vibe Coder Starter Kit bundles starter rules files and prompts for moving from quick prototypes to safer, reviewable projects.
Common misreadings
- "Karpathy says you don't need to learn to code." Not quite. He described a fun way to build small things, and his later comments stress expertise for serious work.
- "Vibe coding means using AI to code." Most developers who use AI review what it writes. Vibe coding, as he defined it, specifically means not looking closely at the code.
- "It was a product launch." It was a personal post on X, not a product or a framework.
FAQ
When did Andrej Karpathy coin vibe coding?
On February 2, 2025, in a post on X describing a style of coding where you "fully give in to the vibes" and "forget that the code even exists."
What tools did Karpathy use for vibe coding?
In his original post he mentioned Cursor's Composer with a Claude Sonnet model, and SuperWhisper for talking to it by voice.
Does Karpathy think vibe coding is good for production code?
He said it was "not too bad for throwaway weekend projects." In 2026 he described "agentic engineering" as the better term for serious AI-assisted work, which needs expertise and oversight.
What is agentic engineering?
It's the term Karpathy said in February 2026 he preferred for professional AI-assisted development, where you direct AI agents to write code but stay responsible for design, review and quality.
Who is Andrej Karpathy?
An AI researcher and educator. He was a founding member of OpenAI, led AI for Tesla Autopilot and now runs Eureka Labs, an AI-native education company.
Was vibe coding really Word of the Year?
Yes. Collins Dictionary named "vibe coding" its Word of the Year for 2025.
Written by Agentdex Editorial. Agentdex is an independent directory reviewing AI coding tools; we are not affiliated with the companies mentioned. Prices and features are as of October 24, 2026, from official sources linked above. Always confirm on the vendor's site.