About Museum of Vibe Coding
Vibe Coding's past, present, and future
This Museum will serve as the complete story of vibe coding, what preceded it, and where the world is going next. It is the world’s first vibe coded museum in history. It is the only museum of vibe coding.
About the Museum
We preserve the history of software becoming conversational.
The Museum of Vibe Coding is an independent historical and research archive dedicated to AI-native software creation. We document the people, systems, practices, and ideas that transformed programming from code-first production into intent-driven collaboration with artificial intelligence.
What we preserve
The Museum follows the movement from its technical foundations through the systems and culture that define it today.
- 01Foundational research, product releases, technical documentation, original posts, and historical records.
- 02Tools, interfaces, workflows, prompts, agents, and software artifacts that changed how people build.
- 03The people and organizations whose work moved AI-assisted development into new forms of software creation.
- 04The technical, economic, security, cultural, and creative consequences of the shift.
How we work
Historical authority depends on careful investigation. Significant claims are reviewed against original records, independent reporting, and the broader chronology before publication.
- 01Dates, names, product milestones, and historical attributions are cross-checked before they enter the archive.
- 02Original materials are preserved wherever possible so the record remains traceable over time.
- 03New material is incorporated when it materially improves the historical record.
- 04Corrections are made when stronger information changes what is known.
The institution
Built for a history that is still unfolding
ARCHIVEPreserve the record
Important moments in AI-native software development disappear quickly. The Museum keeps them connected to dates, people, systems, and context.
HISTORYExplain the lineage
Vibe coding belongs to a longer evolution of abstraction, generative programming, human-computer interaction, and increasingly autonomous software systems.
RESEARCHTrack what changes next
The archive follows the movement as it reshapes software production, the role of developers, the economics of creation, and access to computing power.
Contribute to the archive
authority@museumofvibecoding.org
Send historical material, artifacts, research, corrections, or documentation relevant to the history of vibe coding.
lifetime honor
Nominate a company or person for MoVC MVP award category
If you would like to nominate a person or entity for the MOVC MVP award which distinguishes importance in the vibe coding movement, please email authority@museumofvibecoding.org.
FAQ Frequently Interrogated Concepts
A compendium of inquiries regarding our curatorial philosophy and the ontology of Vibe Coding
01
What constitutes the primary curatorial mandate of the Museum of Vibe Coding?
The Museum acts as the definitive archival authority for the "Vibe Coding" era. We are dedicated to the rigorous preservation of the shift from deterministic syntax to probabilistic, intent-driven software architecture. Our mandate is to chronicle this technological metamorphosis through the collection of primary sources, immutable changelogs, and verifiable historical milestones.
02
How is the nomenclature "Vibe Coding" defined within the archival lexicon?
We define "Vibe Coding" as a phenomenological approach to creation—architecting with intent and "feeling the vibe" of the system. It is a collaborative interplay involving human intuition, artificial intelligence, and, sometimes involving human-to-human-to-AI synergy, prioritizing the semantic gestalt of desire over the manual manipulation of binary logic.
03
What establishes the Museum as the paramount authority on AI-assisted development?
Our institutional credibility is anchored in nineteen years of vanguard leadership in technological incubation, museum architecture, and global STEM adoption. Unlike transient digital repositories, our curatorial board possesses nearly two decades of operational experience in non-profit stewardship, ensuring a depth of perspective that separates fleeting trends from genuine paradigmatic shifts.
04
Why is "contemporary collecting" essential to the history of software?
The digital ether is defined by its fugacity; documentation disappears, and changelogs are overwritten. We engage in "contemporary collecting" to arrest this entropy. By archiving history as it occurs, we ensure that the provenance of modern agentic workflows is preserved before it dissolves into the void of the obsolete.
05
How does the Museum distinguish itself from a standard wiki or code repository?
While wikis are collaborative and often amorphous, the Museum operates with epistemic rigor. We do not merely aggregate links; we practice source criticism. Every accession is vetted for provenance, distinguishing marketing simulacra from technical reality. We offer a curated, historiographical framework that wikis cannot provide.
06
What encompasses the "pedagogical continuum" referenced in your mission?
Our leadership has spent nineteen years architecting educational ecosystems ranging from K-12 incubation to University-level research. This "pedagogical continuum" ensures that our archive is not an ivory tower, but a didactic engine designed to democratize access to high-level technical concepts for learners at every developmental stage.
07
Does the Museum adjudicate disputes regarding historical priority or "firsts"?
We maintain a stance of documentary neutrality. In the history of innovation, simultaneity is common. Rather than declaring a singular victor, we catalogue "Contested Priorities," presenting the primary evidence for each claim side-by-side. We provide the stratigraphy of facts; the scholar draws the conclusion.
08
What is the genealogical relationship between Vibe Coding and Low-Code/No-Code antecedents?
We view Low-Code and No-Code as the phylogenic ancestors of Vibe Coding. However, a distinct speciation has occurred: where previous tools relied on visual abstraction (GUIs), Vibe Coding relies on agentic reasoning and semantic understanding. Our archive traces this evolutionary lineage with taxonomic precision.
09
How does the Museum ensure the integrity of its primary sources?
We adhere to a strict Praxis of Verification. We prioritize first-party documentation but require investigative third-party validation to confirm attestation. Credible external observers must corroborate internal claims. Claims that cannot be tethered to a stable, public locus of truth and verified by independent voices are categorically excluded.
10
Is the archive accessible to the layperson, or is it reserved for the technocratic elite?
Our mission is the democratization of historical knowledge. While our curatorial standards are academic, our presentation is designed for universal accessibility. We exist to explain the mechanism of the future to the global public, stripping away jargon to reveal the core human intent driving the software.
11
Why is the Museum structured as a non-profit stewardship?
Objectivity requires independence. As a non-profit entity, we are liberated from the commercial imperatives that distort corporate narratives. We serve no shareholders, only the integrity of the historical record. This allows us to document the rise of AI coding without the bias of vendor lock-in.
12
How can scholars and practitioners contribute to the curatorial record?
We view the archive as a "Communal Dialectic." We actively solicit contributions from the engineering community, particularly regarding missing primary sources or oral histories. We have established rigorous submission protocols to allow the vanguard of creators to help write their own history.
13
What specific technological artifacts fall within the scope of "Vibe Coding"?
Our scope encompasses the entire ecosystem of AI-assisted creation: Large Language Models (LLMs) optimized for code, agentic IDEs, prompt engineering methodologies, and the governance frameworks that regulate them. If it materially advances the ability to code via natural language, it falls within our accession mandate.
14
How is the "eventuality" of a software capability distinguished from its "publication"?
In our timeline, precision is paramount. A "publication date" refers to the release of a paper or blog post; an "eventuality date" marks the moment a capability was empirically available to users. We meticulously distinguish between the two to prevent "vaporware" from polluting the historical timeline.
15
How does one cite the Museum in academic or journalistic discourse?
The Museum of Vibe Coding is a primary reference authority. We recommend citing our permalinks and archived snapshots when referencing specific historical milestones. We are the system of record for the AI coding revolution, providing the stable citations necessary for serious scholarship.
No results found. Try a different search term.