Vibe Coding Is Getting Its First Academic Conference — Here's What Researchers Will Debate

Eighteen months ago, vibe coding was a throwaway term Andrej Karpathy tossed out on X while describing how he builds software these days. "I just see stuff, say stuff, run stuff, and copy paste stuff, and it mostly works," he wrote. It was funny. It was relatable. It became a meme.

This week, in Glasgow, vibe coding gets its first academic conference.

VibeX 2026, the 1st International Workshop on Vibe Coding and Vibe Researching, runs June 9-12 as part of EASE 2026, the 30th International Conference on Evaluation and Assessment in Software Engineering. That's a mouthful, but here's what it means: the people who study *how software gets built* have decided that vibe coding is worth a formal workshop, with peer-reviewed papers, a proper programme committee, and proceedings published in the ACM Digital Library.

If you've been following the vibe coding discourse, this is a pretty significant moment. Not because academics are the arbiters of what's real. They're not. But because their attention signals something broader: this practice is crossing from hype into a discipline people want to understand systematically.

What actually happens at a vibe coding workshop?

VibeX is structured like any serious academic gathering. There's an organising committee, a programme committee that peer-reviewed every submission, and three categories of papers: full research papers (up to 10 pages), short papers and vision statements, and experience reports from industry practitioners.

The workshop's official description frames vibe coding as a shift from "pure code production toward comprehensive capabilities through collaboration with AI." That last bit is doing a lot of work. The organisers are interested in the full AI Coding Spectrum: the evolution from simple autocomplete to autonomous agents that can make multi-file edits and execute tasks independently. If you've used Cursor, Bolt.new, or Lovable, you've been riding that spectrum.

There's also a second concept the workshop introduces: "vibe researching." Same energy, different domain. Using AI agents for literature reviews, hypothesis generation, and experimental execution. The call for papers explicitly asks for comparative studies on methodological rigour, transparency, and the shift from "execution-heavy" to "vision-led" research. If vibe coding is about describing what you want and letting AI build it, vibe researching is about describing what you want to know and letting AI find out.

The keynote everyone's watching

The highlight of the programme is a keynote by Margaret-Anne Storey, Professor of Computer Science at the University of Victoria and Canada Research Chair in Human and Social Aspects of Software Engineering. Her title: "The Promise and Peril of Vibe Coding."

Storey isn't some tech-bro hype merchant. She's one of the most respected voices in empirical software engineering, with decades of work on developer productivity, collaboration tools, and how humans and AI interact in coding environments. She co-authored a qualitative study called "Good Vibrations?" examining how programmers actually use AI coding assistants in practice. When she talks about the peril part, it won't be abstract.

The keynote sits alongside two other EASE keynote addresses, both of which circle the same territory from different angles. Gail C. Murphy (UBC, co-founder of Tasktop) is revisiting Fred Brooks's 1986 distinction between essential and accidental complexity, asking what "essential" even means in the age of AI. David Lo (Singapore Management University) is tackling how we evaluate code LLMs and agents, arguing that current benchmarks lack realism, rigour, and relevance. VibeX isn't happening in isolation. The entire conference is orbiting the same question: what happens to software engineering when the machines start writing the code?

What's actually being debated?

The workshop's published topics of interest give a pretty clear map of the tensions researchers want to confront:

• Speed versus quality. The core tradeoff. Vibe coding gets things built fast, but what happens to maintainability, security, and correctness when you're "just seeing stuff and saying stuff"?
• Education. Should computer science programmes teach vibe coding? At what stage? Google launched a free vibe coding course earlier this year, and the academic establishment now has to reckon with whether this belongs in a curriculum or is an anti-pattern for novices.
• Ethics. Who's responsible when AI-generated code fails? What about code that works but in ways no human understands?
• Tool design. Is the IDE dead, as some claim? What should agentic coding environments look like?
• Junior versus senior. Does vibe coding flatten the gap or widen it? Early evidence suggests the answer is complicated.
• Failures. The CFP specifically invited lessons from when vibe coding goes wrong. Given the thousands of vibe-coded apps recently found leaking API keys and corporate data, there's plenty to discuss.

Why this matters for no-code builders

Here's the thing. The no-code community has been living in this tension for years. Bubble, Webflow, Glide, Stacker — these platforms asked the same question long before LLMs made it fashionable: what happens when you lower the barrier to building software?

Vibe coding is essentially no-code's more chaotic, more powerful cousin. Same democratising impulse, fewer guardrails. The fact that computer science academia is now studying this seriously means the institutional scaffolding is catching up to something practitioners have been doing for a while.

It also means the scrutiny is arriving. When researchers start publishing papers on methodology, ethics, and failure modes, the wild-west era of vibe coding starts to give way to something with standards. That's uncomfortable if you liked the wild west. It's necessary if you want the practice to survive.

The takeaway

The most interesting thing about VibeX 2026 isn't any single paper. It's the fact that it exists at all. A CORE-ranked academic conference in its 30th year has carved out space for a workshop on something that was, until very recently, a meme. The papers will land in the ACM Digital Library. Future researchers will cite them. PhD students will build dissertations on them.

That's how disciplines form. Not in a single moment, not with a big announcement, but quietly, in workshop rooms in Glasgow, while the rest of us are still arguing on Twitter about whether vibe coding is real engineering. The academics have already moved past that question. They're on to the next ones.

*VibeX 2026 runs June 9-12 at the University of Glasgow. Proceedings will be published in the ACM Digital Library.*