Vibe coding is building software by describing what you want to an AI tool in plain language, running what it produces, and steering it with more descriptions until the result does what you meant. You judge the app by how it behaves, not by reading every line of code. That is the whole idea, and it is why people who have never written a program can now get a working website or small app running in an evening.
Where the term came from
Andrej Karpathy, an AI researcher who co-founded OpenAI and led AI work at Tesla, coined the phrase in a post on X on 2 February 2025. He described a way of working where you "fully give in to the vibes" and "forget that the code even exists": you ask for changes, accept them without reading the diff, and paste error messages back until things work.
The phrase spread fast and its meaning widened. Simon Willison, a well-known developer and writer, argued in March 2025 that vibe coding should mean only building with AI without reviewing the code, and that careful AI-assisted programming is a different thing. His post, read on 12 November 2026, quotes Karpathy's original text in full. In everyday use today, people say vibe coding for almost any building with AI where the prompt does most of the work. The vibe coding book by Gene Kim and Steve Yegge uses it in that wider sense.
What it looks like in practice
A typical first session goes like this:
- You open a tool and write a paragraph: "A page where I log the books I read, with a star rating and a list sorted by date."
- The tool writes the code, and a preview of the app appears next to the chat.
- You click around, notice what is wrong ("the stars do not save when I reload"), and say so.
- The tool changes the code. You check again. Repeat.
You never have to open a file. Most tools let you, though, and the people who get furthest are the ones who start looking at what changed once they are comfortable.
The tools people use
Vibe coding tools come in two shapes. Browser builders such as Replit, Lovable, Bolt and v0 start from an empty prompt box and give you a running app on a web address. Editor tools such as Cursor, GitHub Copilot and Claude Code work inside a folder of code on your own computer. Our comparison of the best vibe coding tools for a first working app goes through the free tiers and real costs.
What vibe coding is good for
- Personal tools: a habit tracker, a budget sheet that does the sums, a page for your club.
- Prototypes: showing an idea working instead of describing it in a meeting.
- Learning by doing: seeing real code appear for something you asked for is a gentler way into programming than a blank editor.
Where it gets hard
The first version is fast. Problems show up as the project grows:
- Changes break other things. A fix in one place quietly breaks something that worked yesterday. Saving working versions (checkpoints, or git) is the habit that saves you.
- Security is easy to miss. An app that stores other people's data needs logins and database rules set up correctly, and the AI does not always do it unasked. Our Lovable guide covers the database rules part.
- Costs grow with use. Most tools charge in credits or tokens. A long session of small fixes can cost more than you expect.
None of this means you need to learn to code first. It means that after your first few projects, learning a little about what the code does starts paying off.
How to start
Pick one tool, one small idea you would use yourself, and one evening. Vibe coding with Claude and Replit Agent are both good first stops, and the femcode get started guide helps with the idea. When it works, share it in femcode projects so others at the same stage can see it.