Vibe coding is no longer a Silicon Valley buzzword that stays in startup Slack channels. On October 15, 2026, the term is dominating conversations inside the video game industry itself, after a wide-ranging interview with Xsolla’s Chief Strategy & Comms Officer Chris Hewish put a blunt question on the table: what happens to game development when AI tools let “just anybody with a vision or an idea” build and ship a product. The interview, published by ModernCTO, lands at the same moment Epic Games has publicly confirmed it used vibe coding to rebuild its own storefront software, giving the debate a concrete, shipped example instead of just speculation.
Taken together, the interview and the Epic Games launcher rebuild form the clearest signal yet that vibe coding in video games has moved from hobbyist experiment to boardroom strategy. Studios, platform holders, and investors are now treating AI-assisted development as a core competitive variable rather than a side curiosity, and that shift carries real implications for hiring, security, and how quickly new game software can reach players.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
Inside the Interview: Xsolla’s Chris Hewish on Gaming’s AI Future
Chris Hewish holds the Chief Strategy & Comms Officer role at Xsolla, the games commerce and payments company that works with thousands of developers and publishers worldwide. In the ModernCTO conversation, Hewish framed vibe coding as a structural change to who gets to make games, not just a productivity bump for existing studios. He predicted that the funding model around game development is already bending toward this shift, telling the interviewer: “Hey, before you know it, people are gonna get funded for having a Vibe studio, right?”
That line matters because it reframes vibe coding as an investment category, not just a workflow tweak. Hewish went further, arguing that AI-enabled tools could let “somebody, just anybody with a vision or an idea” turn that idea into a working product and put it in front of players, collapsing the traditional path that once required years of engineering training, a publisher relationship, or a funded studio. Podcast host Joel Beasley raised the term directly during the exchange, asking, “And then the whole, what is it? Vibe coding, right?” — a sign that even industry-adjacent media figures are still catching up with how fast the terminology has spread into gaming conversations.
Xsolla’s position gives the comments extra weight. As a commerce layer sitting underneath a large share of independent and mid-size game releases, the company has a front-row view of who is actually shipping titles and how. If Hewish’s read is accurate, the next wave of funded “vibe studios” would be competing directly with traditional indie teams for both player attention and investor capital, and existing comparisons like Claude Code vs Codex vs Copilot adoption data suggest the underlying AI coding tools are already seeing heavy day-to-day developer use well beyond gaming.
What Vibe Coding Actually Means for Game Studios
In practice, vibe coding describes a development style where a programmer or non-programmer describes the desired outcome in natural language and lets an AI model generate, iterate on, and often directly ship the resulting code, with far less manual line-by-line review than traditional software engineering. For game studios, that can touch anything from gameplay scripting and UI layout to the kind of storefront and launcher software that players interact with before a game even starts.
The appeal for smaller teams is obvious: fewer engineers can cover more ground, and ideas that once needed a six-person engineering team can get a working prototype from two or three people. The risk, which the rest of this article digs into, is that speed and review rigor tend to move in opposite directions. Vibe coding in video games is attractive precisely because it compresses timelines, but that same compression is what worries veteran engineers who have spent careers hardening code against edge cases, security holes, and platform certification requirements.
Epic Games Already Shipped a Vibe-Coded Product
While the Xsolla interview deals in predictions, Epic Games has already delivered a real-world case study. The company confirmed that it rebuilt the Epic Games Launcher, the storefront software used to buy and run games on its platform, using AI-assisted development it openly calls vibe coding. In its own preview announcement, Epic Games stated: “Programming is hard. So, instead of doing that, we vibe coded a new Epic Games Launcher that’s way faster and more responsive than the current one, and has a new look.”
Martin Keely, vice president and general manager of the Epic Games Store, gave more detail in an interview with IGN, acknowledging the controversy around AI-assisted coding directly: “It’s obviously an issue that’s of high visibility at the moment across the industry, but for us, it made us more efficient and allowed a small team to rewrite the code base and be able to launch it faster across platforms, support Windows and Mac, and we’re going to have a Linux version as well.” Keely’s framing is notable because it does not dodge the debate — it leans into the tradeoff, presenting a smaller team and a faster rewrite as worth the scrutiny that comes with the vibe coding label.
The performance claim behind the rebuild is specific. In a separate IGN interview, Keely said: “The library loads 30 times faster,” referring to how quickly a player’s game collection appears compared with the previous launcher. That is a concrete, user-facing number that gives the broader vibe coding debate something measurable to point to, rather than leaving the conversation purely theoretical.
By the Numbers: Vibe Coding’s Early Track Record in Gaming
Because this is such a fast-moving story, it is worth separating what has actually been confirmed by named sources from what remains speculation. The table below lays out the current state of verified claims around vibe coding video games as of October 15, 2026.
| Claim | Source | Status |
|---|---|---|
| Epic Games Launcher rebuilt using AI-assisted “vibe coding” | Epic Games official announcement | Confirmed |
| Rebuilt launcher’s game library loads 30 times faster | Martin Keely, VP/GM Epic Games Store, via IGN | Confirmed |
| Small team rewrote the launcher’s full code base | Martin Keely, via IGN | Confirmed |
| Linux version of the launcher is planned | Martin Keely, via IGN | Confirmed, no date given |
| Investors will fund dedicated “vibe studios” for game development | Chris Hewish, Xsolla, via ModernCTO | Prediction, not yet observed industry-wide |
| A named AAA publisher ships a full game built primarily via vibe coding | Not reported by any named outlet | Unconfirmed |
| Industry-wide revenue or headcount impact from vibe coding adoption | Not yet quantified by any named source | Unconfirmed |
The pattern here is consistent with how most emerging development trends play out: the infrastructure and tooling claims are concrete and attributable, while the business-model predictions remain directional. That gap is exactly why Hewish’s funding comment and Epic’s shipped launcher are being read together — one supplies the vision, the other supplies the proof that it works at least for non-gameplay software.
Market Impact: Capital Is Already Flowing Into AI Coding Tools
The capital markets angle around vibe coding predates this week’s interview, but it gives Hewish’s “funded Vibe studio” prediction real context. AI coding agent startups have been pulling in large valuations well outside the game industry specifically, a sign that investors already see AI-assisted software creation as a category worth betting on regardless of vertical. Elsewhere in the broader AI-coding market, startups building autonomous coding agents have seen valuations triple within months, and separate industry data has shown AI coding assistants adding meaningfully more code volume to production codebases, even as reviewers debate how much of that output constitutes finished, shippable software rather than just more code to maintain.
Coverage from WebProNews frames Epic’s launcher rebuild explicitly as a competitive bet, arguing that gaming platforms are now racing on development speed as much as on content exclusives or storefront fees. That reframing is significant for an industry that has spent the better part of a decade competing primarily on revenue-share percentages and exclusivity deals. If vibe coding genuinely lets platform holders and studios ship faster with smaller teams, the competitive axis shifts toward engineering velocity, which is a very different kind of arms race than the one gaming platforms have fought since the Epic Games Store first undercut Steam’s standard cut in 2018.
That velocity argument also connects to funding activity already visible elsewhere in gaming. Independent studios have continued raising capital this year even as the broader game industry faces cost pressure, and tools that let smaller teams credibly compete on production value make that funding math more attractive to investors watching headcount-to-output ratios.
How Platforms and Studios Are Responding, Compared
Not every company in gaming is reacting to AI-assisted development the same way. Some are embracing vibe coding publicly, as Epic Games has, while others are drawing hard lines around AI-generated content specifically to reassure players and artists. The comparison below pulls together how different parts of the industry are currently positioned.
| Company / Platform | Stance on AI-Assisted Development | Public Evidence |
|---|---|---|
| Epic Games | Openly embraces “vibe coding” for internal tooling | Rebuilt Epic Games Launcher, 30x faster library loads |
| Xsolla | Predicts AI will expand who can fund and run a studio | Chris Hewish interview with ModernCTO |
| Capcom | Publicly rejects AI-generated in-game assets | Vowed zero AI assets in RE Engine titles amid fan backlash |
| Google Play | Opened AI app-building tools to non-developers | Vibe coding feature launched for 18+ users without a developer account |
| Steam (Valve) | No public vibe coding policy; competes on platform scale | Hit 43.5 million concurrent users, a 2026 record |
The split illustrates that vibe coding is being adopted unevenly depending on what is being built. Back-end and storefront software, like Epic’s launcher, appears to be where studios feel most comfortable letting AI tools do heavy lifting, since errors there are inconvenient but rarely game-breaking for players. Front-facing creative content, by contrast, is where companies like Capcom are drawing firmer lines, reflecting both quality concerns and the reputational risk of visible AI-generated art or writing inside a flagship franchise.
Historical Context: From Visual Scripting to Vibe Coding
Game development has gone through several waves of trying to lower the barrier to building playable software. Visual scripting tools inside engines like Unreal’s Blueprint and Unity’s Bolt let designers build logic without writing traditional code, but they still required understanding the underlying system architecture. Asset marketplaces did something similar for art and audio, letting small teams buy production-quality content instead of building it from scratch. Each of these shifts expanded who could meaningfully contribute to a game without fundamentally changing who could ship one.
Vibe coding is being discussed differently because the claim attached to it is bigger: not just lowering the skill floor for one part of development, but potentially removing the engineering bottleneck almost entirely for some categories of software. A piece published by Inven Global gathering multiple perspectives on the current state of the game industry captures this tension well, with people across the business weighing efficiency gains against concerns about where creative and technical judgment still needs to sit with a human. That framing echoes long-running debates in software more broadly, including the shift documented in reporting on AI coding agents adding 30% more code without necessarily producing 30% more finished software, a distinction the game industry is now running into as well.
The Skeptics: Why Developers Are Wary of “Vibe Studios”
Martin Keely’s own comments acknowledge the skepticism head-on rather than brushing past it. His description of vibe coding as “an issue that’s of high visibility at the moment across the industry” is itself an admission that Epic anticipated pushback before the launcher even shipped. That pushback tends to center on a few recurring arguments among working engineers and designers: AI-generated code can pass casual testing while still hiding edge-case bugs, automated output can quietly duplicate licensed or copyrighted patterns without anyone noticing, and teams that lean too heavily on AI generation risk losing the institutional knowledge needed to debug complex systems when something eventually breaks in production.
There is also a labor dimension to the skepticism that goes beyond code quality. If Hewish’s prediction about funded vibe studios plays out, it implies a future where fewer engineers are needed per shipped title, which is a direct concern for a games workforce that has already weathered multiple rounds of layoffs across the industry in recent years. Keely’s framing of “a small team” rewriting Epic’s launcher is presented as an efficiency win by the company, but the same fact can read very differently to engineers worried about headcount trends across the industry.
What People Building This Are Actually Saying
Beyond the Xsolla interview, the clearest first-hand testimony about vibe coding video games comes directly from the people who shipped Epic’s rebuilt launcher. Epic Games put its position in writing in its own launcher preview announcement, cited above: “Programming is hard. So, instead of doing that, we vibe coded a new Epic Games Launcher that’s way faster and more responsive than the current one, and has a new look.”
Martin Keely, the executive overseeing the Epic Games Store, backed that framing with implementation detail in his IGN interview cited earlier: “It’s obviously an issue that’s of high visibility at the moment across the industry, but for us, it made us more efficient and allowed a small team to rewrite the code base and be able to launch it faster across platforms, support Windows and Mac, and we’re going to have a Linux version as well.” On the specific performance gain players will notice first, Keely was direct in his separate IGN conversation: “The library loads 30 times faster.”
Xsolla’s Chris Hewish, speaking to where this trend goes next rather than what has already shipped, told ModernCTO that the funding world is already adjusting to this category, predicting people will get backed “for having a Vibe studio.” Taken together, the testimony from Epic’s side describes present-day results, while Hewish’s comments describe where the capital is likely to move next — two halves of the same emerging story.
Risks: Code Quality, Security, and Accountability Gaps
Launcher and storefront software sits in a sensitive position because it handles payment flows, account credentials, and automatic updates — exactly the kind of surface area where quietly introduced bugs can become security incidents rather than mere annoyances. Epic has not reported any security issues tied to the rebuilt launcher, and Keely’s comments focus entirely on speed and efficiency gains rather than defects. Still, the broader vibe coding conversation across software development has repeatedly raised questions about whether AI-generated code receives the same level of security review as hand-written code, particularly when a “small team,” in Keely’s own words, is responsible for a rewrite of this scope.
Accountability is the other open question. When a traditional engineering team ships a bug, there is a clear chain of code review, pull requests, and named reviewers to trace the mistake back through. Vibe-coded software, by design, compresses that chain, which raises a practical question studios will need to answer as the practice spreads: who signs off on AI-generated code before it reaches millions of players, and what does a meaningful review process look like when the code was generated from a natural-language prompt rather than written line by line.
Five Predictions for Vibe Coding in Game Development
Based on where the Xsolla interview and Epic’s launcher rebuild leave the conversation, a handful of near-term outcomes look most likely heading into 2027.
- More platform holders will apply vibe coding to back-end and storefront software first, following Epic’s pattern, before extending it to gameplay-facing code where errors are more visible to players.
- Investors will start explicitly asking studios about their AI-assisted development workflows during funding pitches, turning Chris Hewish’s “funded Vibe studio” comment into a literal due-diligence question.
- At least one major publisher will face public criticism after an AI-assisted feature ships with a visible bug, similar to the backlash patterns already seen around AI-generated art in franchises like Capcom’s Resident Evil line.
- Game industry labor groups and unions will push harder for transparency requirements around how much of a shipped title’s code was AI-generated, echoing broader software-industry debates about AI coding agent output quality.
- Smaller and mid-size studios will adopt vibe coding tools faster than large publishers, since the efficiency gains matter most to teams without the engineering headcount AAA studios already have.
None of these are locked in, and the industry has a track record of overcorrecting on hype cycles before settling into a more boring equilibrium. But the combination of a named executive predicting a new funding category and a major platform holder already shipping a concrete example gives this particular wave of vibe coding more substance than most AI trend stories get on day one.
What Comes Next for Vibe Coding in Gaming
The next concrete marker to watch is whether Epic actually ships the Linux version of the launcher that Keely referenced, since a successful cross-platform rollout would strengthen the case that vibe-coded rewrites hold up under real-world, multi-platform demands rather than just a single successful launch. Equally important will be whether any other major platform holder goes on record the way Epic has, rather than quietly using similar AI tools without the same public framing. Xsolla’s own commerce data, given its position underneath a large slice of the independent game market, would be one of the more credible sources to confirm or walk back Hewish’s prediction about dedicated vibe studios attracting funding rounds over the coming year.
For now, the story sits at an unusually clear inflection point: one executive describing where the money is likely to go, and one platform holder already showing what the product looks like when it gets there first.
Frequently Asked Questions
What is vibe coding in video game development?
Vibe coding video games describes using AI models to generate working software from natural-language descriptions rather than traditional line-by-line programming. In gaming, it has been applied most visibly to back-end and storefront software, such as Epic Games’ rebuilt launcher.
Did Epic Games really use vibe coding to build its launcher?
Yes. Epic Games confirmed this directly in its own launcher preview announcement, and Martin Keely, VP and general manager of the Epic Games Store, discussed the approach in on-record interviews with IGN.
Who is Chris Hewish and why does his interview matter?
Chris Hewish is the Chief Strategy & Comms Officer at Xsolla, a games commerce company. In an interview with ModernCTO, he predicted that investors will begin funding dedicated “vibe studios” built around AI-assisted game development.
How much faster is the vibe-coded Epic Games Launcher?
According to Martin Keely, the rebuilt launcher’s game library loads 30 times faster than the previous version, based on his interview with IGN.
Is vibe coding being used for actual gameplay code, not just launchers?
There is no confirmed, named report of a major studio shipping a full game title built primarily through vibe coding as of October 2026. Current public examples center on supporting software like storefronts and launchers.
Are game studios worried about AI-generated code quality?
Yes. Martin Keely himself described vibe coding as “an issue that’s of high visibility at the moment across the industry,” acknowledging the scrutiny even while defending Epic’s results. Broader concerns from developers center on security review gaps and reduced accountability for AI-generated output.
Will vibe coding reduce jobs in game development?
That remains unconfirmed and contested. Efficiency gains like Epic’s “small team” launcher rewrite are read by companies as productivity wins, but the same facts raise headcount concerns among engineers, especially following recent industry-wide layoffs.
What should smaller studios take away from this trend?
Smaller teams are likely to adopt AI-assisted development fastest, since the efficiency gains matter most where engineering headcount is limited. Studios experimenting with it should prioritize support software and tooling first, following Epic’s own rollout pattern, before extending AI generation into player-facing gameplay systems.
