Epic Games has reportedly told its developers working on a delayed Disney shooter—featuring Marvel and Star Wars characters—to stop writing code by hand. The new directive, as reported by The Verge and corroborated by Ars Technica and a Bloomberg-sourced Hacker News roundup, calls for an "AI first" or "AI-accelerated" development model. Art will be generated through "full AI workflows," and staff have been pointed at tools like Anthropic's Claude for both code and asset generation.
This isn't a quiet tooling update. It's a structural pivot on a high-profile IP collaboration, delivered to a team that was, per internal reporting, already stunted by a 1,000-employee layoff wave tied to a Fortnite engagement downturn.
What's actually being reported
The Verge's account (Oct 13, 2026) is the most specific. Game director Stevie Bonifield reportedly told staff: "No more hand-written code." All game art is to be produced via full AI workflows rather than being exclusively human-made. An Epic spokesperson, Jake Jones, confirmed externally that the company is "embracing AI-accelerated development."
Ars Technica reports the same core shift: the Marvel/Star Wars shooter is moving away from hand-written code and "AI-free art" toward an AI-first model, still within the Disney collaboration framework.
The Hacker News / AV Club item adds the internal texture. Employees were "stunned" by the mandate, some initially hoping it was a "sick joke." Internal reports, as relayed in that piece, suggest Epic had simply underestimated how many people the project required. The AI mandate followed that gap.
The context that makes this harder to read as a pure tech story
A few facts frame the decision:
- The game was originally targeting a March release window. It is now delayed. No new date has been confirmed by any source.
- Disney put $1.5 billion into Epic in 2024. That's a capital relationship, not a licensing footnote. Disney did not provide a comment when approached about the pivot.
- Epic has used AI before in production. The Verge notes a prior AI-generated Darth Vader character in Fortnite. So this isn't the company's first brush with AI output in a shipped product.
- The layoff wave hit earlier this year. Over 1,000 employees were cut following what was described as a Fortnite engagement downturn. The timeline links the two events, but the reported narrative is that Epic underestimated staffing for the Disney project specifically, and the AI mandate is the remedial move. The causal chain is reported, not independently established.
Tim Sweeney tweeted, per The Verge's reporting, that the pivot is meant to let developers build "MORE and BETTER stuff" rather than just reduce headcount. That's how the story is told from the top. It's also how the story reads most charitably.
What's unresolved (and what you should watch)
No source, as of this writing, confirms:
- A new release date.
- Whether the AI-first mandate is scoped to this Disney project or applies across Epic's development org.
- Which specific models, prompt pipelines, and review controls sit between a developer's prompt and a shipped asset. Claude is named by The Verge; other tools may be in the stack.
- How AI-generated code will be reviewed, tested, secured, and maintained over the product's lifetime. "No more hand-written code" is a production instruction, not a software engineering policy.
- Disney's formal position. No comment was provided. You can't infer approval from silence.
The practical question for anyone building software teams that are experimenting with AI-generated code isn't "can the model output compile?" It's "who owns the diff, who signs off on the security review, and what happens in month fourteen when a generated module has a subtle state bug that three different LLMs disagree on?" Those are the questions the current reporting doesn't answer, because Epic hasn't publicly defined them.
Why this lands differently than 'AI in your editor,'
Most AI-assisted development today is a suggestion layer. You write the function; the tool autocompletes or refactors. What's being reported here is a different category: the model is the production pipeline for code and art on a specific title, with human oversight (presumably) but no hand-written baseline.
If that model works—and ships, on a Disney IP slate, within a reasonable timeframe—it changes the staffing math for mid-to-large character-driven games. If it doesn't, it changes the post-mortem math for a company that just wrote a $1.5 billion check to its partner and is publicly confirming the shift to its own employees.
Either way, the next 12–18 months of Epic's internal tooling decisions will be the most interesting case study in AI-assisted software production to watch. Keep an eye on job postings, postmortems, and any Unreal Engine plugin releases that hint at the actual pipeline architecture. The tweet said "MORE and BETTER stuff." The build log will tell you if it did.
