---
title: "What Is Vibe Coding?"
description: "Vibe coding is building software by describing what you want in plain language and letting an AI write the code, focusing on the result over the syntax."
type: "glossary"
locale: "en"
term: "Vibe Coding"
canonical: "https://agenticschool.dev/glossary/vibe-coding"
dateModified: "2026-06-13"
---

# What Is Vibe Coding?

- Definition: Vibe Coding
- Updated: 2026-06-13
- Keywords: vibe coding, what is vibe coding, vibe coding meaning, vibe coding definition, andrej karpathy vibe coding
- Canonical URL: https://agenticschool.dev/glossary/vibe-coding
- Locale: en

> Vibe coding is building software by describing what you want in plain language and letting an AI write the code, focusing on the result over the syntax.

Vibe coding is a way of building software where you describe what you want in plain natural language and let an AI coding tool write the code, so you steer by the result rather than by reading and writing every line yourself. The term was coined by Andrej Karpathy in February 2025, who described it as "I just see stuff, say stuff, run stuff, and copy-paste stuff, and it mostly works", and it was named Collins Dictionary Word of the Year for 2025. In short, vibe coding means you give the vibe and the goal, the AI produces the implementation, and you check whether it does what you wanted.

## How vibe coding works

You prompt an AI tool in everyday language ("add a dark mode toggle", "fix this error"), it generates or edits the code, you run it, and you keep going by describing the next change. You lean on the output and the running app to judge progress instead of inspecting the code closely. This makes building fast and accessible, but it also means you are trusting code you may not fully understand.

- You describe the goal in plain language, not in code.
- The AI writes, edits and often runs the code for you.
- You judge success by the result, then prompt the next change.

## Where it shines, and where it bites

Vibe coding is great for prototypes, throwaway scripts, learning and getting a first version on screen quickly. The risk shows up when vibe-coded software goes to real users: code you never reviewed can hide security holes, break in edge cases, or become impossible to maintain. The honest practice is to vibe code freely while exploring, then slow down, read the code, add tests and harden it before anything ships.

## Vibe coding vs agentic engineering

Vibe coding and agentic engineering both use AI to write code, but they are not the same. Vibe coding optimises for speed and feel and accepts not understanding the result. Agentic engineering keeps you in charge: you still drive an AI agent, but with clear goals, tests, reviews and verification so the output is production-grade. Think of vibe coding as the fun on-ramp and agentic engineering as how you turn that into something you can trust in production.

## FAQ

### Who coined the term vibe coding?

Andrej Karpathy coined it in a February 2025 post, describing a style of coding where you mostly see, say, run and copy-paste with an AI and it mostly works. Collins Dictionary then named "vibe coding" its Word of the Year for 2025.

### Is vibe coding safe for production apps?

Not on its own. Vibe coding is excellent for prototypes and learning, but code you have not reviewed can carry security and reliability issues. Before you ship to real users, read the code, add tests and harden it, which is the shift from vibe coding to agentic engineering.

### Do I need to know how to code to vibe code?

No, that is much of the appeal. You can build working software by describing what you want. Some understanding still helps you spot when the AI goes wrong and decide what is safe to ship, so basic literacy pays off fast.

### What is the difference between vibe coding and using an AI coding assistant?

It is a matter of degree. An AI assistant suggests code you review and accept. Vibe coding leans further: you mostly trust the output by its behaviour rather than reading it line by line, prompting your way to the result.