The original wording says that the point of vibe coding is that you "forget that the code even exists". That is not slang for fast development: it is a specific claim about what you do not do. You do not read it through, you do not understand it line by line, and you cannot say what happens inside it.
It follows that the question is not how good the model is. The question is whether you can afford to forget that this particular code exists. For a weekend experiment, a one-off data conversion, an internal helper, the answer can comfortably be yes. One vendor reliability report lists nine live cases where the answer was not yes — of those, one is confirmed by an independent source as well.
The most common misconception is that vibe coding and AI-assisted development are the same thing. They are not: in AI-assisted development you read and review what you got. The difference between the two is not speed, it is responsibility — the code is yours even when you did not type it.
Where the line runs, and what happened in those cases, is the subject of Vibe Coding: What It Is Good For and Where It Stops, a separate article. Directly related terms: coding agent, AGENTS.md and slopsquatting.