Vibe Debugging

What does vibe debugging mean?

The app breaks. You paste the error message into the chat. The AI rewrites some code, you run it again, and a different error appears. So you paste that one back too.

Eventually the app works. You may not know exactly what fixed it.

Vibe debugging is the joking, slightly critical name for letting the AI chase the bug while you keep testing the result. It is closely tied to vibe coding, where generated code may be accepted without much review.

The term is still used in more than one way. Here, it refers to the trial-and-error version common in vibe coding; elsewhere it can mean AI-assisted debugging more broadly.

How people use it

Three hours, six pasted stack traces, no idea what actually broke. Pure vibe debugging.

Example written for this dictionary.

People often use the phrase about themselves. The joke is that the bug may be gone, but the explanation went with it.

Why it matters

For a small experiment or a throwaway project, that may be good enough. The approach gets riskier once the code needs to be maintained, trusted or explained to someone else.

The issue is not using AI to debug. It is fixing symptoms without knowing whether the underlying problem is actually gone. A passing test can tell you that one case works; it cannot tell you what else the rewrite changed.

Where it came from

Vibe debugging grew out of vibe coding, the phrase Andrej Karpathy popularized in 2025 for a loose, AI-led style of programming where the developer may spend more time prompting and testing than reading the generated code.

The debugging variation followed naturally, but a reliable first use has not surfaced. Its meaning remains less settled than vibe coding itself.