Vibe Coding vs Agentic Engineering: What Is Actually Different (and Why the Claude Code Creator Wants to Retire the Term)

The creator of Claude Code went on r/technology last week and asked, more or less politely, if anyone had a better name than "vibe coding." The post pulled 2,200 upvotes and 1,498 comments. A few days later Simon Willison published "vibe coding and agentic engineering are getting closer than I'd like" on his blog. The Hacker News thread on it hit 787 points and 885 comments.

Two senior people in the AI tooling world, in the same week, arguing the same thing: the term we all started using in early 2025 is no longer fit for purpose.

Then I pulled Google Trends. Worldwide average interest for "vibe coding" sits at 61. For "agentic engineering" it sits at 1.

I run a site called vibecoding.app. So when the people who built the tools tell me the name has outgrown the work, I have a stake in the answer. Here is what I actually think, after reading both pieces, the Reddit threads, and the Ask HN that ran in parallel about whether Anthropic itself is doing too much vibe coding.

TL;DR

• Insiders want a serious-sounding term because the workflow got more serious. Fair.
• The audience has not moved and probably will not move soon. Trends data is unambiguous.
• The two words describe overlapping practices but different audiences, different tools, and different failure modes.
• Use "vibe coding" for the front door (anyone with an idea). Use "agentic engineering" for the engine room (anyone responsible for what ships).

Table of contents

1. The thread that started this
2. Why "vibe coding" got popular in the first place
3. What "agentic engineering" actually means
4. The four real differences
5. Why the audience will not move
6. What we use at vibecoding.app and why
7. FAQ

The thread that started this

The Claude Code creator's r/technology post does not say "vibe coding is dead." It says, roughly, that the term carries cultural baggage that no longer matches what senior engineers do with these tools. Plan steps. Run evals. Read the diff. Roll back when it breaks. The argument is that calling all of that "vibing" undersells the discipline involved, and undersells the people doing it.

To his credit, he wrote it as a question. He asked the community what they would call the supervised, instrumented version of the workflow. The replies were a mix of (a) thoughtful alternatives, including "agentic engineering," (b) people defending the original term, and (c) the usual Reddit chaos.

The most upvoted defense, paraphrased: the name fits the actual audience. Founders and designers are not running eval loops. They are running prompts and accepting output. That is exactly what Karpathy meant when he coined it in February 2025. Renaming it does not change who is doing the thing.

Simon Willison's piece a few days later took the other side. His post on the convergence of vibe coding and agentic engineering is worth reading in full, but the core observation is this: the tools are pushing both workflows toward the same middle. Cursor's agent mode, Claude Code's planning loops, Codex's diff review, even Lovable's checkpoint system. They all add supervision on top of pure prompt-and-accept. So the line between "I vibed it" and "I engineered it agentically" is fuzzier than it was a year ago.

Both takes are correct. They just describe different parts of the elephant.

Why "vibe coding" got popular in the first place

Karpathy coined the term on X in February 2025. The post did 4.5 million views. Within six months Collins Dictionary made it Word of the Year. Within twelve months it became a category descriptor in venture pitches, job posts, and product copy.

Three reasons it landed:

1. It described a real new behavior. Accepting AI output without reading every line was new. People needed a word for it.
2. The "vibe" word did real work. It captured the part of the experience that was emotional, not just technical. You feel when the AI got it right.
3. It was the right word for the audience that was actually buying. Founders, indie hackers, designers, and people who had been locked out of "real" coding by syntax. None of them wanted to be called engineers. "Vibe coder" felt like permission.

That last point is the one the rebranders keep underweighting. Karpathy did not name a discipline. He named a permission slip.

What "agentic engineering" actually means

Strip the vocabulary and the practice is recognizable. From Simon Willison's framing and what platform teams are actually doing:

• Planning. The agent writes a step plan before touching code. You review and approve it. Then execution starts.
• Eval loops. Outputs run through automated checks: type checks, tests, lint, sometimes LLM-judge evals on specific behaviors. Failure routes back to the agent.
• Instrumentation. Logs, traces, token counts, retry counts, rollback triggers. The same stuff you wrap around any production system.
• Supervision. A human reviews diffs, not full files. The agent does the typing. You make the editing decisions.
• Memory and skills. The agent learns your repo conventions so the next session starts smarter than the last.

If you have ever used Claude Code with a plan-then-execute workflow, you have done agentic engineering. The name is more honest than "vibing" for what you were doing. But the work itself is not new.

The four real differences

Strip the philosophy and there are four practical splits between the two ends of the spectrum.

1. Tooling depth

• Vibe coding: prompt, accept, move on. Single window. Maybe a preview pane.
• Agentic engineering: plan tool, eval tool, file diff tool, terminal tool, rollback tool, sometimes a sub-agent tool. Multiple windows, sometimes multiple agents.

The simplest test: how many things does the agent have permission to do without asking you? Vibe coding is "one thing at a time." Agentic engineering is "the whole loop, here is the budget."

2. Output ownership

• Vibe coding: "the AI wrote it." You ship it. If it breaks, you re-prompt.
• Agentic engineering: "I supervised the AI writing it." You sign the diff. If it breaks, you read the trace and fix the prompt, the eval, or the retry policy.

This is the one the Claude Code creator was getting at. Senior engineers do not want their work described as "vibing" because the responsibility model is different.

3. Failure handling

• Vibe coding: retry with a different prompt. Maybe a different model.
• Agentic engineering: automated retry with structured feedback, alerts on threshold breaches, rollback on failed evals, and an incident review at the end.

If the workflow does not include any of "logs, alerts, rollback," it is vibe coding regardless of which model you used. That is not a value judgment. It is a category line.

4. Audience

• Vibe coding: founders, designers, students, hobbyists, indie hackers. People with an idea and a deadline.
• Agentic engineering: senior engineers, platform teams, ML and infra people, anyone responsible for an SLA.

Same tools, different responsibility levels, different vocabularies. This is fine. Most disciplines have a casual term and a serious term. "Cooking" and "culinary arts" coexist without anyone losing sleep.

Why the audience will not move

Back to the Trends data. 61 vs 1. Not a margin you close with one Reddit post and one HN piece. Three reasons:

1. Search volume favors the incumbent. Tools, courses, communities, and job posts have eighteen months of inventory built around "vibe coding." Replacing the vocabulary means rewriting your SEO, your landing pages, and your category page on Product Hunt. Nobody is doing that.
2. The word is in the dictionary. Collins made it official in 2025. Merriam-Webster called it trending. Linus Torvalds publicly admitted he tried it. Dictionary inclusion is a one-way ratchet.
3. The audience the rebranders want is small. Senior engineers are a fraction of the people buying AI coding tools. Renaming the category to please them shrinks the addressable market.

The likely outcome is the one Willison hinted at: convergence in practice, divergence in vocabulary. The workflows blur. The labels split. Founders keep saying "vibe coding." Platform teams adopt "agentic engineering." Both refer to overlapping subsets of the same tool stack.

What we use at vibecoding.app and why

Disclosure first: we are called vibecoding.app. We are not neutral. We picked the name because it was the term the audience was using and it still is. Skip to the FAQ if that disqualifies us in your reading.

Here is how we use the two terms internally and on the site:

• Front door: vibe coding. The definitional explainer, the tool directory, the landing page, the ads. This is where founders, designers, and students find us. The word does the marketing work.
• Engine room: agentic engineering. When we write about eval loops, multi-agent orchestration, supervised diff review, or vibe debugging workflows, we use the more precise vocabulary because the readers care about the precision.
• Bridge: agencies that supervise AI-generated code. The literal job description for what the Claude Code creator was describing. Someone has to do the supervision when the founder cannot.

We do not think the two terms are at war. They are at different doors of the same building.

A note on Karpathy

His original post was descriptive, not prescriptive. He named a behavior he saw, the behavior is real, and the naming was a gift to the category. The fact that the category later wanted a more serious name does not retroactively make the original term wrong. It just means the category grew up. Worth reading the Ask HN on whether Anthropic itself is doing too much vibe coding for the inside-baseball version of the same tension.

Bottom line

Use "vibe coding" when you are talking to the people buying. Use "agentic engineering" when you are talking to the people shipping. Both are real. Neither is going to win.

We are betting our domain on it.

FAQ

Is vibe coding dead? No. Google Trends still shows it at 61x the volume of "agentic engineering." The audience has not moved, and the term is in the dictionary. What is happening is a vocabulary split for a small senior-engineer audience, not the death of the category.

What is agentic engineering, in one sentence? Building software with AI agents under explicit supervision: planning, evals, instrumentation, retries, and rollback. The grown-up version of what most people call vibe coding.

Did Karpathy rebrand to agentic engineering? Not publicly. He coined "vibe coding" in February 2025 and has not retracted it. His recent work on tool use and evals matches what Simon Willison calls agentic engineering, but the rebrand is a community move, not a Karpathy move.

Why did the Claude Code creator want to retire the term? He argued the cultural baggage of "vibe" undersells the discipline senior engineers put into supervised agent workflows. The community pushed back. Most replies said the name still fits the audience that actually uses it.

Should I put "agentic engineering" on my resume? If you are applying to platform teams, MLOps roles, or production AI systems work, yes. If you are applying for product, frontend, or indie roles, "Cursor/Claude Code fluency" reads better. Recruiter search still indexes on "vibe coding" as a category.

Should I rewrite my landing page? Probably not. If your buyers are founders or non-technical builders, "vibe coding" still converts. If your buyers are enterprise engineering leaders, swap it for "agentic engineering" or "AI-supervised development." Match the door to the audience.

Where do I go to actually learn this? Start with our what is vibe coding explainer. Then read Simon Willison's piece for the agentic engineering framing. Then look at the Reddit thread for the community pushback. Then pick a tool from the directory and run a real loop.

---

Have a take on the vocabulary war? We are still calling the site vibecoding.app, but we are honest about why. If you think we should pivot to agenticengineering.dev, the comments are open.