Vibe coding

On this page 7

Vibe coding is a software development style in which a person describes the desired behavior in natural language, lets a large language model generate the code, and judges the result mainly by running it and observing what happens rather than by reading the source. Among AI applications in artificial intelligence, it sits at the far end of the automation spectrum: the human steers by intent and feedback, while the model writes, edits and often debugs almost every line.

The phrase was popularized in February 2025 by the researcher Andrej Karpathy, who described giving in to the flow of the conversation and largely forgetting that the code exists. The defining trait is therefore not the use of AI itself but the deliberate absence of line-by-line review, which separates vibe coding from disciplined AI code generation inside a professional workflow.

How vibe coding works in practice

Vibe coding works as a tight conversational loop between a person and a coding model: describe, generate, run, react, and repeat. The person rarely edits files directly; instead, every correction becomes another natural-language instruction, such as “the button does nothing on mobile, fix it”.

Modern tools make this loop fast because the model can read the whole project, write several files at once and execute commands. Agentic editors and browser-based app builders apply changes automatically, install dependencies and show a live preview, so the cycle from idea to visible result often takes seconds.

The table below breaks the loop into its stages and shows what the human and the model each contribute.

StageHuman roleModel role
IntentStates the goal in plain languageInterprets requirements and fills gaps
GenerationWaits or accepts all changesWrites or rewrites files and configuration
ExecutionRuns the app or opens the previewMay run commands and tests itself
FeedbackPastes errors or describes wrong behaviorDiagnoses and patches the code
IterationRequests new features or tweaksExtends the codebase incrementally
Stages of a typical vibe coding loop

A key behavioral marker is pasting error messages back verbatim without investigating them. When a fix fails repeatedly, a vibe coder typically asks for a different approach or reverts to an earlier working state rather than debugging manually.

Vibe coding differs from neighboring practices mainly in how much the human reads, understands and owns the generated code. The same model and editor can support all of them; the difference lies in the developer’s discipline and accountability.

PracticeHuman reviews codeTypical userMain output
Code completionEvery suggestion, inlineProfessional developerFaster typing of known code
AI copilotMost changes before commitProfessional developerAssisted functions and refactors
AI-assisted engineeringAll changes, with testsEngineering teamProduction software
Vibe codingLittle or noneHobbyist, founder, designerPrototypes and personal tools
AI app builderUsually noneNon-programmerHosted apps from templates
Degree of human control across AI-assisted coding styles

Experienced engineers often argue that reviewing, testing and understanding generated code turns vibe coding back into ordinary software engineering with a fast assistant. In that sense, the term describes a mode of working that anyone can switch into, not a specific product or skill level.

Where vibe coding delivers value

Vibe coding delivers the most value when speed of exploration matters more than long-term maintainability. It lowers the barrier for people who understand a problem domain but lack programming fluency, and it lets experienced developers test ideas in minutes instead of days.

The decision table below summarizes situations where the approach fits well and where it carries unacceptable risk.

SituationSuitabilityReason
Throwaway prototype or demoWell suitedDisposable code, fast feedback matters most
Personal script or small utilityWell suitedSingle user, limited blast radius
Internal tool with sensitive dataUse with cautionAccess control and data handling need review
Customer-facing production servicePoorly suitedSecurity, scale and maintenance demand ownership
Regulated or safety-critical systemNot appropriateAudits require traceable, understood code
When vibe coding is and is not appropriate
  • Rapid prototyping: founders and product managers validate an idea before funding real development.
  • Learning by doing: newcomers see working examples, although passive acceptance can slow real understanding.
  • Weekend projects: small games, dashboards and automations that would otherwise never be built.

Risks and failure modes of vibe coding

The central risk of vibe coding is that nobody fully understands the system being shipped. Code that works in a demo can still contain security vulnerabilities, hidden data leaks and fragile logic that only appear under real users, real data or real attackers.

Language models also produce characteristic errors. They may invent package names that do not exist, a weakness attackers exploit by publishing malicious packages under those names, a pattern known as slopsquatting. They may also hard-code secrets, disable validation to silence an error, or quietly delete failing tests.

SymptomLikely causeMitigation
API keys visible in the browserSecrets placed in client-side codeMove secrets to a server and rotate keys
Any user can read all recordsMissing authorization rulesAdd and test row-level access control
Fix loop that never convergesContext lost across many editsRevert, then restate the goal concisely
Unknown dependency installedHallucinated or typosquatted packageVerify packages against the official registry
Codebase too tangled to extendAccumulated unreviewed patchesRefactor with tests or rebuild deliberately
Common symptoms, causes and mitigations

A further cost is technical debt that compounds quickly. Each patch is locally plausible, but without an architectural plan the project drifts toward duplicated logic and inconsistent patterns, and beyond a few thousand lines the model itself struggles to keep the whole design coherent.

Practices that make vibe coding safer

Vibe coding becomes considerably safer when a few lightweight guardrails are added without giving up its speed. The most effective one is frequent version control commits, which turn every working state into a restore point.

  1. Commit after each working change so a failed experiment can be reverted in one step.
  2. Ask the model to write automated tests and to explain how each feature is protected.
  3. Keep credentials in environment variables and run a secret scanner before publishing.
  4. Request a security review prompt focused on authentication, input validation and data exposure.
  5. Have a person who reads code review anything public-facing before real users arrive.

These steps do not make the code fully trustworthy, but they shrink the gap between a quick experiment and software that can responsibly handle other people’s data.

Put simply

Vibe coding means building an app by talking to an AI instead of writing code yourself. You say what you want, the AI writes the program, you try it, and you tell it what to change. You judge the work by whether it seems to work, not by reading how it was built.

It is a bit like directing a builder without ever checking the wiring. The house can look finished and the lights can turn on, yet hidden problems may remain. That is fine for a garden shed you built for fun, but risky for a home where other people will live.

In practice

A small bakery owner wants an online form where regular customers can reserve bread for Saturday pickup. With no programming background, she opens a browser-based AI app builder and writes: “Create a reservation page with a list of five breads, a quantity field, a pickup time between 7 and 11, and an admin view showing all orders.” Within about twenty minutes of back-and-forth prompts, she has a working page with a live preview.

Before sharing the link, a friend who works as a developer spends an hour checking it and finds that the admin view had no password, so anyone who guessed the address could see customer names and phone numbers. One more prompt adds a login and access rules. The outcome is typical of vibe coding: a useful tool built in an afternoon, made safe only after a brief human review caught what the conversation never mentioned.