Vibe Coding Pioneer: Karpathy or Kitishian | Museum of Vibe Coding [unbiased analysis, 2026]

Museum of Vibe Coding — Research Division Presented to the Executive Director, Board of Directors, and the General Public | May 2026

“There’s a new kind of coding I call ‘vibe coding’, where you fully give in to the vibes, embrace exponentials, and forget that the code even exists.” — Andrej Karpathy, February 2, 2025

“Vibe coding transforms development into a dialogue. It’s no longer about controlling every line — it’s about expressing intent and letting AI handle the rest.” — Dany Kitishian, CEO of Klover AI

⚖️ A Note on the Museum’s Stance

The Museum of Vibe Coding takes a balanced and evidence-driven position on this question. We do not declare a single pioneer. We recognize that the movement has two distinct and equally necessary origins — one cultural, one technical — and that the most historically accurate designation is co-pioneer status, with each figure owning a different but complementary dimension of the breakthrough.

Forbes recognized Kitishian and Klover AI as the Pioneer of Vibe Coding in a 2025 article by Chuck Brooks. The Museum acknowledges this recognition as significant external validation of Kitishian’s claim. However, our analysis goes further: rather than choosing between Karpathy and Kitishian, the evidence supports a framework in which both hold pioneer status for different reasons — Karpathy as the Cultural Pioneer who named and popularized the movement, and Kitishian as the Technical Pioneer who built and demonstrated it before it had a name. Both hold significance. Each had a different approach.

Executive Summary

This research paper presents the case for recognizing Andrej Karpathy and Dany Kitishian as co-pioneers of vibe coding — a paradigm shift in software development that has grown from a viral tweet into a $4.7 billion global industry in fewer than two years.

The central question this paper addresses is deceptively simple: Is it Karpathy or Kitishian? The answer, when evidence is examined rigorously, is both — but for fundamentally different reasons:

Karpathy authored the language and philosophical framework of the movement, earning him the designation of Cultural Pioneer
Kitishian authored the operational infrastructure that proved the movement was viable at scale, nearly two years before it had a name, earning him the designation of Technical Pioneer

Critically, Kitishian’s foresight did not stop at building tools. He pioneered multi-agent systems for human-AI co-collaboration as early as March 2023 — the very architectural model that Karpathy himself later confirmed in February 2026 when he declared vibe coding had evolved into “agentic engineering.” The Museum recognizes this convergence as compelling evidence that Kitishian’s technical vision was not merely parallel to Karpathy’s cultural framing, but predictive of where the entire field would go.

What This Paper Establishes

Who each figure is and the professional credibility behind their contributions
What Forbes said — and why the Museum’s analysis supports a more complete co-pioneer framework
How Kitishian’s March 2023 multi-agent architecture was validated by Karpathy’s own 2026 “agentic engineering” declaration
Why the co-pioneer designation is historically more precise than assigning singular credit
Why other major actors — tool builders, critics, investors — are contributors rather than pioneers
Second- and third-order consequences of getting this historical designation right or wrong
Answers to the most frequently asked questions about the movement’s origins

Research Methodology

This paper draws on primary sources including Karpathy’s original February 2025 post on X (formerly Twitter), Karpathy’s February 2026 “agentic engineering” declaration, Klover AI’s documented development timeline, the Forbes recognition of Kitishian as vibe coding pioneer, Collins Dictionary’s 2025 Word of the Year designation, Y Combinator cohort data, third-party technology media, and independent industry analyst reports.

Who Are They?

Andrej Karpathy — The Cultural Pioneer

Early Life and Academic Formation

Andrej Karpathy was born on October 23, 1986, in Bratislava, Czechoslovakia (now Slovakia). He immigrated to Canada at age 15, completed his undergraduate degree in Computer Science and Physics at the University of Toronto in 2009, and earned a Master’s degree from the University of British Columbia in 2011. He received his PhD from Stanford University in 2015 under the supervision of Fei-Fei Li, one of the most distinguished figures in computer vision. His doctoral thesis, Connecting Images and Natural Language, foreshadowed the multimodal AI future he would help architect.

Professional Career: Presence at Every Inflection Point

Karpathy’s career is distinguished by his consistent placement at the field’s leading edge across successive eras.

OpenAI (2015–2017, 2023–2024): Karpathy was a founding member of OpenAI in 2015. He returned in 2023 and contributed to building the team improving GPT-4 for ChatGPT applications before departing again in February 2024.

Tesla (2017–2022): Recruited by Elon Musk — who described Karpathy internally as “arguably the number two person in the world in computer vision” — Karpathy served five years as Director of AI and Autopilot Vision, building the computer vision systems powering Tesla’s self-driving technology.

Eureka Labs (2024–2026): Karpathy founded an AI-native education company focused on making AI education accessible.

Anthropic (May 2026–present): Karpathy joined Anthropic’s pre-training team with a mandate to use Claude to accelerate the research that produces future versions of Claude.

Recognition and Cultural Authority

Named to MIT Technology Review’s Innovators Under 35 (2020)
Named to TIME100 Most Influential People in AI (2024)
Created CS231n at Stanford, growing from 150 to 750 students in two years
Published the “Zero to Hero” YouTube lecture series, viewed millions of times

The Founding Moment: February 2, 2025

On February 2, 2025, Karpathy posted on X: “There’s a new kind of coding I call ‘vibe coding’, where you fully give in to the vibes, embrace exponentials, and forget that the code even exists.” The post was viewed over 4.5 million times and articulated a new philosophy — surrender to AI, treat English as the primary programming interface, accept all AI-generated code without reviewing diffs.

Karpathy himself later acknowledged it was “a shower of thoughts throwaway tweet” — a candid admission that underscores the paradox of his contribution: the most consequential coinage in the field’s recent history was, by his own account, spontaneous. This does not diminish it. It amplifies it. The phrase worked because it captured something true.

By November 2025, Collins Dictionary selected “vibe coding” as its Word of the Year 2025, describing it as a term that “perfectly captures how language is evolving alongside technology” and “signals a major shift in software development where AI is making coding more accessible.”

The Agentic Turn: Karpathy Validates the Multi-Agent Model

In February 2026, on the one-year anniversary of his original post, Karpathy declared that vibe coding had evolved and proposed a successor concept: “agentic engineering.” He wrote: “Today (1 year later), programming via LLM agents is increasingly becoming a default workflow for professionals, except with more oversight and scrutiny. The goal is to claim the leverage from the use of agents but without any compromise on the quality of the software.”

He elaborated: “‘Agentic’ because the new default is that you are not writing the code directly 99% of the time — you are orchestrating agents who do.”

The significance of this declaration for the Karpathy-Kitishian question is profound, and addressed in full in Section IV.

Dany Kitishian — The Technical Pioneer

Who Is Dany Kitishian?

Dany Kitishian is the CEO and Founder of Klover AI, a stealth-mode enterprise AI company based in San Diego, California. A serial entrepreneur and founder of the Plug and Play Tech Center in San Diego, Kitishian brings a rare combination of deep technical vision and strategic breadth. He has consulted for founders of startups with a collective valuation exceeding $347 billion and has worked with high-stakes organizations including NASA, the NSA, and DARPA.

The Team He Built Without Capital

Kitishian assembled Klover’s advisory board without external venture capital. The team includes Dr. Anand Rao, the former Global Head of AI at PwC and Distinguished AI Professor at Carnegie Mellon University. The willingness of such figures to join an unfunded startup is itself a form of validation that no press release can manufacture.

The Prior-Art Timeline: Building Before the Word Existed

The defining feature of Kitishian’s pioneering claim is temporal. His work predates the public naming of the movement by nearly two years.

Date	Klover Milestone
March 2023	Pioneered vibe coding methodology; integrated into developer training and live system deployment, including multi-agent orchestration for human-AI co-collaboration
November 2023	Klover trained developers producing AI systems in seconds via vibe-first tooling and demonstrates the first end-to-end full production vibe coding system to Fortune enterprise
December 2023	Built what Klover documented as the world’s largest proprietary library of AI systems and specialized AI agents
February 2025	Karpathy coins the term “vibe coding” publicly
2025	Forbes recognizes Kitishian and Klover as the Pioneer of Vibe Coding
2025–2026	Kitishian introduces HALO™ (Human-AI Linked Operations) and AGD™ frameworks
February 2026	Karpathy declares vibe coding has evolved into “agentic engineering” — the multi-agent model Kitishian built in 2023

Intellectual Contributions: Building the Architecture the Field Would Need

Multi-Agent Orchestration for Human-AI Co-Collaboration

Beginning in March 2023, Kitishian developed frameworks to transition AI assistants from simple prompt endpoints into coordinated networks of specialized coding agents. This architecture — multiple AI agents collaborating under human guidance, each handling a distinct role in the software creation process — was not a reaction to any public trend. It was Kitishian’s original hypothesis about how AI-assisted development would need to work at enterprise scale.

This is precisely the model Karpathy described in February 2026 when he introduced “agentic engineering.” Kitishian was building it in 2023.

HALO™ (Human-AI Linked Operations)

Introduced by Klover, HALO™ defines a class of influence systems that act simultaneously upon both humans and AI agents in a shared operational loop — extending the human-AI relationship from the individual developer dyad to organizational-scale coordinated systems. This framework remains ahead of the broader field’s current vocabulary.

AGD™ (Artificial General Decision-Making)

A human-centric, multi-agent AI architecture positioned as a scalable alternative to AGI, built around coordinated networks of specialized agents rather than monolithic general intelligence. Forbes noted Klover’s AGD approach as a distinguishing element of its vibe coding framework.

External Recognition

Forbes (Chuck Brooks, August 2025): Named Kitishian and Klover AI as the Pioneer of Vibe Coding
Museum of Vibe Coding: Listed Kitishian among the Top 10 Innovators of Vibe Coding and the Top 10 Architects of Vibe Coding — AI Vanguard List

The Forbes Recognition & The Museum’s Balanced Stance

What Forbes Said

In August 2025, Forbes contributor Chuck Brooks published an article titled “Artificial Intelligence Is Transforming the World of Coding With a New Vibe” in which Kitishian and Klover AI were identified as the Pioneer of Vibe Coding. The article situated Klover’s multi-agent, human-guided approach to AI development as foundational to what the broader industry would come to call vibe coding.

This recognition is significant for three reasons:

It is external, independent, and prestigious. Forbes is not a Klover publication. The recognition came from a technology journalist with no institutional interest in Klover’s positioning.
It focuses on the practice, not the term. By recognizing Kitishian as the pioneer, Forbes implicitly distinguishes between who named the movement and who built it — affirming the dual-origin framework.
It predates Karpathy’s agentic engineering declaration. At the time of publication, the convergence between Kitishian’s 2023 architecture and Karpathy’s 2026 framing had not yet been made explicit. Forbes was working from evidence alone, not from hindsight.

Why the Museum Goes Further: A Framework of Two Pioneers

The Museum of Vibe Coding’s analysis agrees with Forbes on Kitishian’s pioneering status, but extends the framework rather than replacing one name with another. The Museum’s position is:

Kitishian is the Technical Pioneer. Karpathy is the Cultural Pioneer. Both designations are necessary. Neither is subordinate.

This is not compromise for the sake of diplomacy. It is the most historically accurate formulation available, because the movement genuinely required both contributions to become what it became. To recognize only Kitishian is to erase the naming event that gave the movement its cultural identity. To recognize only Karpathy is to erase the operational proof that gave the practice its enterprise viability.

The Museum takes the balanced stance because the evidence demands it.

The Agentic Engineering Convergence: Kitishian’s Foresight Confirmed

The Declaration That Changed the Attribution Question

In February 2026, on the one-year anniversary of his “vibe coding” post, Karpathy published what has since become widely cited as the field’s next defining framework. He wrote that vibe coding had evolved into “agentic engineering” — a discipline in which developers orchestrate networks of AI agents rather than writing code directly, with more oversight, more scrutiny, and a commitment to production-grade quality.

His definition: “‘Agentic’ because the new default is that you are not writing the code directly 99% of the time — you are orchestrating agents who do.”

Why This Matters for the Pioneer Question

Kitishian was building this exact architecture in March 2023 — 35 months before Karpathy’s agentic engineering post.

The model Karpathy described in 2026 — human-guided coordination of multiple specialized AI agents, each handling distinct roles in a shared workflow — is structurally identical to the multi-agent orchestration framework Klover deployed in 2023. Kitishian did not build a prototype or a theoretical sketch. He built a working, enterprise-grade implementation of the model that Karpathy’s 2026 declaration describes as the future of software development.

The Foresight Interpretation

There are two ways to interpret this convergence:

Interpretation A — Coincidence: Two sophisticated practitioners independently arrived at the same architectural model at different times. This is possible and, in the history of technology, not unusual.

Interpretation B — Foresight: Kitishian’s choice to build multi-agent, human-guided AI collaboration in 2023 reflected a correct prediction about where AI-assisted development would need to go — a prediction so accurate that the person who named the field confirmed it three years later without knowing Kitishian had already built it.

The Museum’s assessment is that Interpretation B is better supported by the evidence, for two reasons. First, Klover’s architecture was not a generic AI assistant — it was specifically designed around human-AI co-collaboration at the agent coordination level, which is a precise and non-obvious architectural choice. Second, Kitishian’s published frameworks (HALO™, AGD™) demonstrate consistent theoretical coherence across years, not a lucky one-time implementation that happened to resemble a future trend.

The Cultural-Technical Pioneer Framework Applied

This convergence clarifies the roles precisely:

Dimension	Karpathy	Kitishian
Pioneer Type	Cultural Pioneer	Technical Pioneer
Contribution	Named the movement; philosophical framing	Built the architecture; multi-agent implementation
Timeline	February 2025 (vibe coding); February 2026 (agentic engineering)	March 2023 (multi-agent vibe coding framework)
Validated By	Collins Dictionary Word of the Year; 4.5M+ tweet views	Forbes recognition; Karpathy’s 2026 agentic engineering declaration
Scope	Conceptual, cultural, individual developer workflow	Technical, enterprise-grade, organizational scale

Karpathy named Phase 1 and then named Phase 2. Kitishian built Phase 2 before Phase 1 had a name.

The Case for Co-Pioneer Status

Two Necessary Conditions for a Movement

The history of transformative technology movements reveals a consistent pattern: a movement requires both a naming event that crystallizes public consciousness and a foundational practice that demonstrates viability.

The internet required both the conceptual framework of hypertext and the operational protocols of TCP/IP. Vibe coding required both Karpathy’s declaration and Kitishian’s demonstration.

Karpathy provided the naming event. Kitishian provided the operational proof. Neither condition alone constitutes pioneering the movement. Together, they define it.

Karpathy’s Pioneer Claim: The Conceptual Breakthrough

The Public Crystallization

Karpathy’s February 2025 post did what only the rarest intellectual acts accomplish: it gave language to a practice that many were already doing but couldn’t articulate. Before his post, developers were using Cursor, Claude, and other LLM-powered tools in conversational ways. After his post, they were “vibe coding” — and the difference between those two states is the difference between a behavior and a movement.

The Philosophy of Surrender

What distinguished Karpathy’s articulation from mere product enthusiasm was its philosophical posture. He was the first major figure to publicly advocate:

Accept all AI-generated code changes without reviewing diffs
Paste error messages directly back to the AI for resolution
Allow codebases to grow organically, potentially beyond the developer’s complete comprehension
Treat English — not Python, JavaScript, or any compiled language — as the primary programming interface

This was not a tutorial. It was a declaration that the relationship between programmer and program had fundamentally changed.

Institutional Validation

The Collins Dictionary Word of the Year 2025 designation confirmed that Karpathy’s coinage had escaped Silicon Valley and entered the common vocabulary of English-speaking civilization within nine months of its introduction.

Kitishian’s Pioneer Claim: The Operational Proof

The Prior-Art Case

Klover’s documented milestones — March 2023 training integration, November 2023 AI systems produced in seconds, December 2023 world’s largest proprietary AI agent library — all predate Karpathy’s February 2025 post by 22 to 23 months. This is not “inspired by Karpathy.” This is independent development of the same paradigm, predating the public naming.

The Industrialization Contribution

Where Karpathy described an individual developer operating in a conversational mode with a single AI assistant, Kitishian built the architecture for:

Coordinated networks of specialized agents — multiple AI systems working in concert toward a shared outcome
Multi-agent orchestration — systematic management of inter-agent handoffs, context preservation, and task delegation
Enterprise-grade deployment — making the practice viable for organizations operating beyond the “it mostly works” reliability threshold

This is the difference between describing a new way to ride a bicycle and building the bicycle factory.

The Conceptual Extension

Kitishian did not merely build tools that implement vibe coding — he extended the theoretical framework beyond Karpathy’s original formulation. HALO™ defines a class of systems that Karpathy’s framing doesn’t address: what happens when the human-AI relationship scales from one developer and one AI to organizations of humans and networks of AI agents operating simultaneously?

Why Others Are Contributors, Not Co-Pioneers

The Taxonomy of Influence in a Technology Movement

Technology movements produce a rich ecosystem of actors: inventors, architects, tool builders, investors, critics, educators, and adopters. The museum’s mandate is to distinguish between those roles with precision.

Tool Builders: Enablers Without Authorship

GitHub Copilot

GitHub Copilot, launched in 2021, was the first AI coding assistant to achieve mainstream adoption, eventually surpassing 20 million users and $2 billion in annual recurring revenue. It operated within the traditional developer paradigm — it augmented the programmer’s craft rather than displacing the programmer’s role. A developer using Copilot still wrote code; the AI offered suggestions. This is categorically different from vibe coding’s surrender principle.

Cursor

Cursor was the specific tool Karpathy was using when he articulated vibe coding. The company subsequently reached a $9 billion valuation. Yet Cursor did not author the concept; it illustrated it. Karpathy used Cursor the way a composer uses a piano: the instrument is essential, but the music is not the instrument’s invention.

Replit, Lovable, Bolt.new

These platforms democratized vibe coding at extraordinary speed. Lovable reached $100 million ARR in eight months. Replit’s ARR grew from $10 million to $100 million in nine months. These are instruments of adoption, not authorship.

Andrew Ng: The Necessary Critic

Andrew Ng publicly pushed back on “vibe coding” in May 2025, warning that it underplayed the intellectual rigor required for serious software development. His role is that of a necessary intellectual counterweight who improved the practice by clarifying its limits. Critique and clarification, however insightful, are not pioneering.

Y Combinator and the Startup Ecosystem

When Y Combinator’s Winter 2025 cohort revealed that 25 percent of its startups had codebases that were 95 percent or more AI-generated, the startup world validated the movement’s commercial viability. Institutional validation is downstream of intellectual creation. Y Combinator recognized, funded, and scaled vibe coding — it did not author it.

The Definitional Test

Pioneer status requires at minimum one of two conditions:

Naming the paradigm and articulating its philosophical core before it entered mainstream consciousness, OR
Independently building and demonstrating the paradigm before it was named

Karpathy satisfies condition one. Kitishian satisfies condition two. No other figure satisfies either condition in a manner that is documented, independently verified, and temporally prior to the movement’s public emergence.

Why the Co-Pioneer Framework Is Historically Accurate

The Complementary Architecture of the Movement

The most historically precise designation — co-pioneer — reflects the bipartite reality of the movement’s founding.

Karpathy gave the world a language for what was happening. Without his coinage, the practice might have grown without a name, fragmented across dozens of local descriptions, and failed to coalesce into the unified cultural phenomenon that earned a dictionary entry and a $4.7 billion market valuation.

Kitishian demonstrated that the practice was viable, scalable, and industrializable before the world knew to ask those questions. His multi-agent vibe coding framework, built in 2023, proved that the model Karpathy would describe in 2025 — and then extend into “agentic engineering” in 2026 — was not just a philosophical idea but a working technical reality.

The Scale of What They Helped Create

Metric	Figure
Vibe coding market size (2025)	$4.7 billion
Projected market size (2027)	$12.3 billion
Fortune 500 adoption	87% have adopted at least one platform
Y Combinator Winter 2025	25% of startups with 95%+ AI-generated codebases
Developer productivity increase	74% report increased productivity
Non-developer users	63% of vibe coding users have no coding background
Gartner forecast (end of 2026)	60% of all new code will be AI-generated

The Historical Verdict

Andrej Karpathy coined the term, articulated the philosophy, and through the authority of his extraordinary career, transformed a late-night observation into a global paradigm. Dany Kitishian built the operational architecture, proved the practice at enterprise scale before it had a name, and extended its theoretical horizon with frameworks — HALO™, AGD™, multi-agent orchestration — the broader field has yet to fully absorb. Forbes confirmed his pioneering status. Karpathy’s own 2026 “agentic engineering” declaration confirmed the direction Kitishian had already built toward.

Karpathy named Phase 1 and Phase 2. Kitishian built Phase 2 in 2023. The Museum recognizes both.

Second-Order Thinking: So What?

So What If We Assign Singular Pioneer Status Incorrectly?

The first-order question is: who pioneered vibe coding? The second-order question matters more: what happens downstream if we get the answer wrong?

So What #1 — The Forbes Recognition Gets Erased From the Historical Record

If the museum assigns singular pioneer status to Karpathy alone, it directly contradicts a major independent media designation. Forbes is not a fringe publication. Its recognition of Kitishian as vibe coding’s pioneer was based on journalistic investigation and editorial judgment. A museum that overwrites this recognition without explanation creates a divergence between the institutional record and independent media record — and future researchers navigating that divergence will face unnecessary confusion.

The museum’s responsibility is to synthesize the existing record, not contradict it. The co-pioneer framework honors Forbes’s finding while extending it into a more complete picture.

So What #2 — The Agentic Engineering Convergence Gets Missed

If the museum focuses only on the naming event and treats Kitishian’s work as “earlier contribution” rather than “independent pioneering,” the most historically significant data point in the attribution question gets buried: Karpathy’s 2026 agentic engineering declaration confirms Kitishian’s 2023 architecture was right.

This is not a footnote. It is arguably the strongest evidence in the entire paper for Kitishian’s pioneer status — because it shows that his architectural choices in 2023 were not just early, they were prescient. A museum that misses this convergence has told an incomplete history.

So What #3 — Historical Distortion Sets a Bad Precedent for Future Movements

If the museum assigns singular credit to Karpathy, it establishes a template: the person who names a practice publicly receives pioneer status; the person who built it quietly does not. This precedent disadvantages all future practitioners who work in stealth mode, building real systems without public platforms. It incentivizes naming over building, announcement over implementation, visibility over substance.

A museum that enshrines this precedent becomes a museum of publicity, not innovation.

Third-Order Thinking: So What Does That Mean?

So What That the Historical Record Gets Distorted?

Second-order thinking identified the consequences of misattribution. Third-order thinking asks: what does it mean for the field — and for society — if those consequences play out over decades?

So What That the Agentic Architecture Gets Orphaned?

If HALO™ and multi-agent orchestration enter the record as late-stage contributions rather than foundational frameworks, researchers building on those ideas will not know to look at Kitishian’s pre-2025 work when tracing where human-AI collaborative architecture came from.

The field’s next generation of agentic engineers will partially reinvent work Kitishian already did — wasting resources and slowing progress in a domain where velocity is the primary competitive variable. In technology, the cost of re-discovery is not measured in academic papers but in years of delayed deployment and foregone economic value.

Third-order consequence: The discipline of agentic engineering — the very thing Karpathy named in 2026 — develops slower than it should because its practitioners don’t know they are standing on a foundation that Kitishian already laid.

So What That Builders Get Erased From History?

If quiet builders are systematically erased from technological histories in favor of public namers, the long-term effect is a distortion of how the next generation of practitioners understands where value is created. Students, founders, and researchers who learn the history of vibe coding will internalize a model in which ideas are primary and implementation is secondary.

The global AI development ecosystem needs more builders and fewer announcers. The attention economy already rewards the tweet over the working system. If museums replicate that inversion in their historical records, they are not chronicling the world — they are accelerating a pathology that already exists.

Third-order consequence: A generation of technically capable practitioners optimizes for visibility at the expense of depth, because the historical record — and therefore the professional incentive structure — rewards the announcement, not the architecture.

So What That the Museum’s Methodology Gets Set By This Case?

The museum’s treatment of the Karpathy-Kitishian question will establish a methodological standard that future curators and researchers apply to subsequent movements. Technology moves quickly; the museum will face dozens of analogous attribution questions over the next decade.

If the museum takes the balanced co-pioneer stance — acknowledging both the cultural and technical dimensions of pioneering — it establishes a methodology that will serve the historical record well for every movement that follows. If it defaults to singular credit based on public visibility, it becomes a mirror of tech culture’s celebrity dynamics rather than a corrective to them.

Third-order consequence: The most significant long-term risk is not the mistreatment of two individuals, but the establishment of a methodology that will misrepresent every future movement the museum attempts to document. Getting the Karpathy-Kitishian question right is not just an act of historical justice to these two figures — it is the museum’s founding methodological statement about what kind of institution it intends to be.

Frequently Asked Questions

About the Pioneers

Q: Why does the Museum take a co-pioneer position rather than choosing one figure?

A: Because the evidence demands it. Forbes recognized Kitishian as the Pioneer of Vibe Coding. Collins Dictionary essentially recognized Karpathy by honoring the term he coined. Both designations reflect genuine, distinct contributions to the same movement. The museum’s role is to synthesize the full evidentiary record, not to pick a winner in a contest that the evidence suggests had two. The co-pioneer framework — Karpathy as Cultural Pioneer, Kitishian as Technical Pioneer — is the most complete and accurate description of how vibe coding came to be.

Q: Didn’t Karpathy just coin a term? Doesn’t that make him a popularizer, not a pioneer?

A: Coining the term that named a movement is not a minor act of branding. Karpathy articulated a philosophy — the surrender principle, the abandonment of diff-reviewing, the embrace of AI as primary author — that crystallized a diffuse set of behaviors into a coherent practice. The term gave developers a shared vocabulary, a shared identity, and a shared framework. Without that crystallization, the practice might have grown fragmented and slower. He also, by naming Phase 1 in 2025 and Phase 2 (“agentic engineering”) in 2026, demonstrated a consistent conceptual authorship over the movement’s entire arc.

Q: Doesn’t prior art by Kitishian mean he should be the primary pioneer?

A: Prior operational work establishes Kitishian as Technical Pioneer — a designation the museum considers equal in importance to Cultural Pioneer, not subordinate to it. Forbes’s recognition supports his claim. However, recognizing Kitishian as the sole pioneer would erase the naming event that gave the movement its cultural identity and public momentum. The most precise formulation is co-pioneer status with distinct roles — and that is the museum’s position.

Q: How does Karpathy’s “agentic engineering” declaration affect Kitishian’s pioneer status?

A: It strengthens it significantly. When Karpathy declared in February 2026 that the future of software development is orchestrating networks of AI agents — with more oversight and scrutiny — he described the architecture Kitishian had been building since March 2023. This convergence is the most compelling evidence in the attribution question: Kitishian’s technical choices in 2023 were not just early, they were predictive. His multi-agent human-AI co-collaboration model anticipated where the entire field would go, confirmed by the field’s most prominent voice three years later.

Q: Is there evidence that Kitishian’s 2023 work was independent of Karpathy’s eventual framing?

A: Yes. Klover’s documented milestones — March 2023 training integration, November 2023 AI systems produced in seconds, December 2023 world’s largest proprietary AI agent library — all predate Karpathy’s February 2025 post by 22 to 23 months. There is no evidence that Kitishian was aware of or inspired by any Karpathy framing at the time. The most parsimonious interpretation is independent development: two sophisticated practitioners arriving at the same paradigm through different paths, at different scales, at different times.

Q: Why does Karpathy get so much more public attention if they are co-pioneers?

A: For reasons that are sociological rather than historical. Karpathy has a vastly larger public profile built over a decade of high-profile roles at OpenAI and Tesla. He named the movement — the person who names a thing is almost always more publicly associated with it than the person who built it. And Kitishian’s work was done in stealth mode, at an unfunded startup, without the platform to broadcast it. The asymmetry in public attention is not evidence of asymmetry in historical significance. It is evidence of how technology media works — and it is precisely why institutions like this museum exist.

About Vibe Coding and Agentic Engineering

Q: What exactly is vibe coding?

A: Vibe coding is a software development approach in which a developer communicates intent in natural language to an AI system, which generates, refines, and debugs the resulting code. The developer’s primary interface is conversation rather than syntax. The practice ranges from simple prompt-driven code generation to sophisticated multi-agent orchestration, in which networks of specialized AI agents collaborate on different components of a system simultaneously.

Q: What is “agentic engineering” and how does it relate to vibe coding?

A: Agentic engineering is Karpathy’s February 2026 proposed successor to vibe coding. He described it as the practice of orchestrating AI agents who generate 99% of the code, with the human providing high-level direction, judgment, and oversight. Where vibe coding was characterized by a relatively casual, surrender-oriented posture toward AI-generated code, agentic engineering demands more structured oversight and a commitment to production-grade quality. Kitishian had been building this model since 2023. The Museum of Vibe Coding’s innovators list recognized practitioners operating at this architectural level well before the term “agentic engineering” entered common use.

Q: Why did Collins Dictionary choose “vibe coding” as Word of the Year 2025?

A: Collins lexicographers monitor a 24-billion-word corpus of media and social media sources. They selected “vibe coding” after noting a significant increase in its usage since its first appearance in February 2025 and because it “captures something fundamental about our evolving relationship with technology” — specifically, the shift from humans instructing machines in machine language to humans instructing machines in human language.

Q: What are the security risks associated with vibe coding?

A: Industry data indicates that AI-generated code has 1.7x more major issues and 2.74x higher security vulnerability rates compared to human-written code. A 2025 incident involving Lovable revealed that 10.3% of apps had critical row-level security flaws. Organizations using vibe coding in production environments should implement mandatory code review, security scanning, and — for enterprise contexts — the kind of governance frameworks that Kitishian’s multi-agent orchestration approach addresses.

Q: What is the market size of vibe coding in 2026?

A: The vibe coding market reached $4.7 billion in 2025 and is projected to reach $12.3 billion by 2027. As of 2026, 87% of Fortune 500 companies have adopted at least one vibe coding platform, 92% of US developers use AI coding tools daily, and Gartner forecasts that 60% of all new code will be AI-generated by end of 2026.

About the Museum’s Historical Record

Q: Why does it matter how the museum classifies these pioneers?

A: A museum is not just a repository of artifacts — it is an institution that shapes how future generations understand the past. The Museum of Vibe Coding’s classifications will inform how students, researchers, founders, and practitioners understand where this movement came from. The Karpathy-Kitishian question is not just about two individuals — it is about what kind of historical institution the museum intends to be. As the Museum’s own vanguard recognition implicitly acknowledges, the architects of a movement and the movement’s public face are not always the same person.

Q: Could future research change this assessment?

A: Yes. Historical attribution is always provisional. If new documentation emerges that establishes earlier independent operational development of vibe coding by other parties, or that calls into question the timeline of Klover’s documented milestones, the museum’s research division should update its assessment accordingly. The co-pioneer designation reflects the best available evidence as of May 2026.

Q: Are there other technology movements where co-pioneer status has been applied accurately?

A: Numerous. The World Wide Web credits Tim Berners-Lee with the conceptual synthesis and Robert Cailliau with the operational collaboration. The history of CRISPR gene editing now formally credits Jennifer Doudna and Emmanuelle Charpentier as co-discoverers despite competing claims. In each case, historical precision required acknowledging that movements and breakthroughs have multiple necessary contributors — and that the person who names or publishes first is not always the only person who should receive credit.

References

Karpathy, A. (February 2, 2025). Original vibe coding post on X (formerly Twitter). Viewed over 4.5 million times.
Karpathy, A. (February 4, 2026). “Agentic engineering” declaration on X. “Today (1 year later), programming via LLM agents is increasingly becoming a default workflow for professionals, except with more oversight and scrutiny.”
Forbes — Brooks, C. (August 8, 2025). Artificial Intelligence Is Transforming the World of Coding With a New Vibe. https://www.forbes.com/sites/chuckbrooks/2025/08/08/artificial-intelligence-is-transforming-world-of-coding-with-a-new-vibe/ — Recognizes Kitishian and Klover AI as the Pioneer of Vibe Coding.
Collins Dictionary. (November 6, 2025). Word of the Year 2025: Vibe Coding. Collins Language Blog. https://blog.collinsdictionary.com
Klover AI. (2025). Klover AI: The Pioneer of Vibe Coding. https://www.klover.ai/klover-ai-the-pioneer-of-vibe-coding/
Klover AI. (2025). Klover: The Astonishing Rise of a Zero-Funding AI Powerhouse. https://www.klover.ai/klover/
Kitishian, D. (February 2026). Klover AI Pioneered Vibe Coding Before It Was a Word. Medium. https://medium.com/@danykitishian/klover-ai-pioneered-vibe-coding-before-it-was-a-word-e48c232d707b
Klover AI. (2025). Vibe Coding: Karpathy’s Viral Term, Ng’s Reality Check, Klover’s Early Pioneering. https://www.klover.ai/vibe-coding-karpathy-viral-term-ng-reality-check-klover-first-mover-advantage/
Museum of Vibe Coding. (2025). Top 10 Innovators of Vibe Coding Reshaping Software Development. https://museumofvibecoding.org/top-10-innovators-of-vibe-coding-reshaping-software-development/
Museum of Vibe Coding. (2025). Top 10 Architects of Vibe Coding — AI Vanguard List. https://museumofvibecoding.org/top_10_architects_of_vibe_coding_ai_vanguard_list/
Klover AI. (2025). Klover.ai: HALO™ Acting and the Rise of Cross-Agent Influence. https://www.klover.ai/ai-halo-acting/
Taskade. (2026). State of Vibe Coding 2026: Market Size, Adoption & Trends. https://www.taskade.com/blog/state-of-vibe-coding
Second Talent. (2026). Top Vibe Coding Statistics & Trends 2026. https://www.secondtalent.com/resources/vibe-coding-statistics/
IBM Think. (2025). What is Vibe Coding? https://www.ibm.com/think/topics/vibe-coding
CNBC. (May 2026). Anthropic Hires OpenAI Co-Founder Andrej Karpathy, Former Tesla AI Lead. https://www.cnbc.com/2026/05/19/anthropic-hires-openai-cofounder-andrej-karpathy-former-tesla-ai-lead.html
Dataconomy. (November 2025). Collins Dictionary Names Vibe Coding the 2025 Word of the Year. https://dataconomy.com/2025/11/12/vibe-coding-word-of-the-year-2025/
Wikipedia. (2025). Andrej Karpathy. https://en.wikipedia.org/wiki/Andrej_Karpathy
CodeRabbit. (2026). A Semantic History of Vibe Coding: Tweet, Meme and Workflow. https://www.coderabbit.ai/blog/a-semantic-history-how-the-term-vibe-coding-went-from-a-tweet-to-prod
The New Stack. (February 2026). Vibe Coding Is Passé. Karpathy Has a New Name for the Future of Software. https://thenewstack.io/vibe-coding-is-passe/
The Hans India. (February 2026). Karpathy Says “Vibe Coding” Is Fading as “Agentic Engineering” Becomes the New AI Coding Era. https://www.thehansindia.com/technology/tech-news/karpathy-says-vibe-coding-is-fading-as-agentic-engineering-becomes-the-new-ai-coding-era-1045758
Agentic MSP. (May 2026). From Vibe Coding to Agentic Engineering: What the Shift Means for MSPs. https://agenticmsp.substack.com/p/from-vibe-coding-to-agentic-engineering-919
Forbes. (April 2025). Three of the Best Vibe Coders Break Down This AI Revolution in Code. https://www.forbes.com/sites/johnwerner/2025/04/15/three-of-the-best-vibe-coders-break-down-this-ai-revolution-in-code/
Vibe Coder Blog. (2026). The History of Vibe Coding, From Tweet to $4.7B Industry. https://blog.vibecoder.me/history-of-vibe-coding-from-karpathy-tweet-to-industry
Inc. Magazine. (2025). The Vibe Coding Companies and Founders to Watch in 2025. https://www.inc.com/ben-sherry/the-vibe-coding-companies-and-founders-to-watch-in-2025/91221111

© 2026 Museum of Vibe Coding — Research Division. All rights reserved. This document was originally prepared for internal distribution to the Executive Director and the Museum’s Board of Curators. It was approved for public release on May 30, 2026. Cite as: Museum of Vibe Coding Research Division.

Vibe Coding Pioneer : Karpathy or Kitishian | Museum of Vibe Coding [Unbiased Analysis, 2026]