Is vibe coding dead? What Reddit actually says

Somebody posts an obituary for vibe coding roughly once a week, so people keep asking Reddit whether it's actually dead.

Quick answer: No. The word is dying, the practice is not. Reddit's consensus is that unconstrained "prompt and pray" generation failed in production and got replaced by constrained, reviewed, agent-driven workflows. Andrej Karpathy, who coined the term in February 2025, now calls the casual version obsolete and works under the name "agentic engineering." What died is generating code with no written constraints. What survived is everything else.

Google's AI Overview on this query goes further than Reddit does, calling vibe coding "effectively dead as a viable way to build real software." The threads below are more precise about which part died. Here is what they actually say.

What do the Reddit threads say?

The SERP for "is vibe coding dead reddit" is wall-to-wall Reddit, and the biggest threads all land on the same split verdict.

• "RIP Vibe Coding 2024-2026" (r/vibecoding, 600+ comments): the flagship obituary thread, posted in the subreddit named after the practice. The most quoted reply rejects the premise: "Vibe coding is not dead, it is just not what you think it is. The remaining code is mostly done by the engineer."
• "is vibe coding dead?" (r/ClaudeCode, 30+ comments): the thread that ranks first on Google. The principle the discussion converges on: "AI is useful only to the extent you understand the problem yourself."
• "Have we, professional developers, already lost the battle?" (r/cscareerquestions, 660+ comments): the definitional answer: "Vibe coding is explicitly not checking the output of AI. Vibe coding can never 'win'." By that strict definition, the thread concedes the battle is over in the other direction: people ship unchecked AI code anyway.
• "Why is everyone saying vibe coding is dead?" (r/vibecoding): the direct rebuttal thread: "Vibe coding is far from dead. It's quite valuable." The argument is that it delivers what no-code and low-code tools promised for a decade.
• "The Death of 'Vibe Coding'" (r/LLMDevs, 40+ comments): the engineering post-mortem, arguing unmonitored generation is "creating brittle, unmaintainable systems" and compounding technical debt. This is the thread Google's AI Overview cites as its main evidence.
• "Vibe coding has not yet killed software engineering" (r/vibecoding, 40+ comments): the labor-market read: "It technically hasn't 'killed' coding. But it's reduced the number of jobs per project."
• "How Vibe Coding Is Killing Open Source" (r/programming, 160+ comments): the inverse question, where vibe coding is the killer rather than the victim: "Vibe-coding is killing everything, even proprietary software, where you don't see it, but you definitely notice the effects."
• "Is vibe going to end?" (r/theprimeagen, 100+ comments): the cyclical take: "vibe-coding as a concept will die again", framing it as a hype phase that recurs every time the tools jump.
• "Vibe coding is about to kill 95% of you and it's not why you think" (r/SaaS, 250+ comments): the founder angle: "The thing that kills SaaS founders is NOT a coding problem." When everyone can generate an app, generation stops being the moat.
• "Is vibe coding actually the future of development?" (r/VibeCodersNest, 30+ comments): the redefinition in real time: "Definitely the future. But by vibe coding I mean AI assisted development. You still want a human in the loop who knows what they're doing."

Read them together and the pattern is consistent: nobody defends the February 2025 version of vibe coding, and almost nobody has stopped using AI to write code.

Why did "vibe coding is dead" become the narrative?

1. The person who named it moved on

Karpathy's original framing was throwaway: prompt the model, accept what comes back, don't read the diff. In early 2026 he declared that framing passé and started using "agentic engineering" for the structured version: agents that plan, edit across files, run tests, and iterate, while the human owns the architecture. Forbes ran the obituary under the headline "Is Vibe Coding Already Dead? Even Karpathy Is Moving On." When the coiner renames the category, every content farm gets a "vibe coding is dead" post out of it.

2. The usage data wobbled

Gary Marcus asked "Is vibe coding dying?" after investor Chamath Palihapitiya posted a chart showing vibe coding usage "declining for months" from its initial spike. Whether that chart measured the practice or just the buzzword is exactly what the comment sections argue about.

3. Production caught up with the demos

The Stack Overflow blog called vibe coding without code knowledge "a new worst coder" entering the chat. Level Up Coding reports companies that moved fast on vibe coding are now "quietly hiring people to clean up the aftermath." The security numbers behind that cleanup wave are covered in our is vibe coding bad roundup: 10.5% secure agent solutions in a 2026 CMU benchmark, 45% vulnerability rates in Veracode's LLM testing.

4. Declaring things dead performs well

The counter-evidence is on the same SERP. Red Hat's developer piece concludes vibe coding "isn't going away. It's too useful, too accessible, too aligned with how humans naturally think." Designer Michal Malewicz, who published his own obituary post, still admits "Vibe-coding isn't going anywhere. The tools will get better." And the top comment on Hacker News' "Is Vibe Coding Dying?" thread: "Vibe coding is not dying, unless you reductively try to define it in very limited ways."

What actually died, and what survived?

The threads agree once you separate the practice into its parts.

❌ Dead or dying

• Shipping generated code nobody read, to real users, with real data
• "Make it look modern" as the entire design specification
• The one-prompt-one-app demo as a claim about production software
• Treating prompting as a replacement for engineering rather than a layer inside it
• The word itself, at least among people doing it professionally

✅ Alive and growing

• Agent workflows with plans, tests, and review gates (the thing Karpathy renamed)
• Vibe coding as prototyping: r/cursor's "Is Vibe coding (currently) dead against complex projects?" lands on fine for scaffolding, weak for complex systems
• Small, specific, reviewable prompts instead of abstract ones
• Written constraints the model cannot wander away from: specs, test suites, and design contracts

That last item is the part most postmortems skip. Code has always had guardrails available (types, tests, CI). The visual layer usually has none, which is why vibe-coded apps drift toward the same generic look even when the code holds up. We covered that failure mode in why AI-generated apps look the same and the design drift threads.

The workflow that replaced it

Whatever you call the surviving practice, it runs on constraints the model reads before generating. For the UI, that constraint is a design contract: a DESIGN.md file with a real product's color tokens, type scale, spacing system, and written do's and don'ts.

The duply library has 250+ real products extracted into that format. Grab Linear for dev-tool minimalism, Stripe for polished fintech, or Notion for warm content-first UI, drop the file in your repo, and the agent builds against fixed values instead of re-deciding the design every generation. Setup for Claude Code, Cursor, v0, Lovable, and Bolt is in how to give your AI agent a real design system.

FAQ

Is vibe coding dead? No. The unconstrained version (accept whatever the model outputs, don't read it, ship it) is widely considered dead for production software, by Reddit and by the people who coined the term. AI-driven development itself keeps growing; it just picked up plans, reviews, and written constraints along the way.

Why is vibe coding dying? Three reasons dominate the threads: unreviewed output is brittle and insecure at production scale, anyone can now generate a basic app so generated apps stopped being differentiating, and the term became an insult that professionals do not want attached to their workflow.

Is vibe coding still a thing in 2026? Yes, at enormous scale, mostly under new names. r/vibecoding remains one of the most active AI subreddits, and its own users define vibe coding as AI-assisted development with a human in the loop, which is a quiet redefinition of what the word meant in 2025.

What replaced vibe coding? Karpathy's term is agentic engineering: agents that plan, write, test, and debug across a codebase while the human owns architecture and review. The practical difference is written constraints at every layer: specs for behavior, tests for correctness, and design contracts like DESIGN.md for the UI.

Did Karpathy abandon vibe coding? He retired the framing, not the tools. Per Forbes, he now considers casual vibe coding obsolete and describes his own workflow as agentic engineering, with technical mastery mattering more, not less.

Is the vibe coding hype over? The hype cycle peaked and corrected, which is what the Chamath chart in Gary Marcus's piece shows. Search demand for the surrounding questions keeps growing though; "is vibe coding bad" roughly doubled from mid-2025 to mid-2026, which is attention, not abandonment.

Is vibe coding the future? The honest Reddit answer is that it already was the future for prototyping, and it was never the future for unreviewed production code. The r/VibeCodersNest framing holds up: the future is AI-assisted development with a human who knows what they are doing in the loop.

Summary

• "Is vibe coding dead" gets asked because the term's coiner moved on, usage charts dipped, and cleanup stories multiplied
• Reddit's actual verdict: the practice got redefined, not buried; the flagship RIP thread's top reply is "not dead, just not what you think it is"
• What died: unconstrained, unreviewed generation shipped to production
• What survived: agent workflows with specs, tests, review, and written constraints (Karpathy's "agentic engineering")
• The UI is the layer that usually still has no constraints, which is why design drift remains the most visible vibe-coding failure
• Fix the design layer the same way the code layer got fixed: a written contract the agent reads first, like a DESIGN.md from the duply library

Browse the library, pick a DESIGN.md that matches the product you want, and let the obituary writers argue about the name.

Related reading

• Is vibe coding bad? What Reddit actually says
• I hate vibe coding: what the Reddit threads actually say
• How to give your AI agent a real design system