Vibe coding and vibe computing name the same shift in how a person addresses a computer, applied at two different scopes. Vibe coding is the practice of building software primarily by describing what is wanted to an AI assistant. Vibe computing is the broader pattern of doing any digital work that way.
What vibe coding actually means
Andrej Karpathy introduced vibe coding on X in February 2024 to describe a way of writing software in which the developer accepts and iterates on AI-generated code rather than authoring each line directly. He wrote it loosely, not as a category, more as a wink, but the term spread quickly because practitioners recognized themselves in it. The original post is short and worth reading in full.
The tools vibe coding describes are the agentic and autocomplete IDEs that became common over 2023 and 2024: Cursor, GitHub Copilot, Claude Code, OpenAI Codex, Devin, and a long tail of others. They share a shape: the developer describes intent, the model produces code, the developer keeps the loop tight.
What changes outside of code
The property of vibe coding that drew attention, that the user no longer translated their intent into the machine’s formal syntax, is not specific to code. It applies whenever a user can produce an outcome by describing it, regardless of whether the outcome is a function, an email, a slide deck, or a sequence of actions across applications. Vibe computing is the term proposed for that broader shift.
The systems involved differ from vibe coding’s in one important way: they must operate the user’s real computer. Vibe coding ships its output as text in a buffer that the developer then runs. Vibe computing ships its output as clicks, keystrokes, and application calls performed against live software the user is also looking at. That is a meaningfully harder problem and a meaningfully different product shape.
The relationship
Vibe coding is a specialized form of vibe computing whose surface happens to be a code editor. Anyone using an agentic coding tool to ship software is doing vibe computing within a single category of application. Anyone using a screen-reading assistant to operate Excel, Mail, or a browser is doing vibe computing whose surface happens to be everything else.
Why the distinction matters
Treating vibe coding as the whole story understates the change. The same interaction pattern is being applied to surfaces well beyond a code editor: native applications, browsers, email clients, spreadsheets, calendars, and the desktop itself. Naming the broader pattern separately makes that visible, and makes it easier to notice where it is going well and where it is not.