Epic built Unreal Engine 5.9 preview with AI agent fleets in a week

Epic Games assembled the Unreal Engine 5.9 preview in roughly one week, using fleets of AI agents directed by a small team of engineers. It is the company's first engine release built mainly through agentic workflows, and it arrives ahead of the 2026 Epic AI MegaJam, which runs from 12 to 15 November.

The release is also AI-heavy in its feature set. Epic's announcement invites developers to "invite your agents," highlighting the ability to work with AI coding agents directly inside the Editor. The update centres on Unreal MCP, Unreal Assistant and a new AI-driven content creation tool called Unreal Canvas.

What does Unreal Canvas change for artists and technical designers?

Epic describes Unreal Canvas as a shared workspace where people and agents create and refine content using Unreal Engine and connected tools. Canvases include text, image, video and mesh generators, all controlled with prompts and a chosen generation service.

Two companion plugins extend the workflow:

• Unreal Canvas Bridge exposes Movie Render Graph rendering to Canvas as MCP tools.
• Unreal Canvas Spatial Annotations places annotations in the 3D scene and captures the scene for use in Canvas.

Beyond AI tooling, version 5.9 brings improvements to animation, rendering and world-building, including Lumen World Cache and improved Nanite culling. Projects can again run in the browser through WebAssembly and WebGPU.

How did agents build the engine itself?

Eric's engineering account of the build is concrete. "A handful of people directed fleets of agents to port the AI tooling from our UE6 development branch and implement Web as a target platform," Epic states. "Agents wrote the web platform code, starting from UE4's retired HTML5 platform, with engineers directing, reviewing, and testing the work."

Epic frames the experiment as a learning exercise in building the engine with multiple people directing swarms of agents working in parallel. The company adds: "we're already seeing benefits from this approach, and it allows us to deliver more UE5 releases with faster bug fixes and development on targeted features, all without pulling focus from UE6."

The MegaJam's November dates appear deliberate: the jam can serve as a testing ground for the preview before wider adoption.

Why are developers divided?

Epic has acknowledged that some of the agent-written code and parts of the web renderer remain prototypes requiring clean-up before the full release. Developers sceptical of AI agents are citing stability concerns and plan to stay on 5.8.

One commenter on X argues the release crosses a line: "I think we'll just be staying on 5.8. LLMs are a great help, but literally everything about this preview sounds like something that crosses a boundary. Focus on optimising your code, what possessed you to add 3D model generation?"

Others see merit in the integration strategy. "I'm not a fan of the asset gen stuff. But I do love more integration for agents! Including not trying to force us to use an agent IN the editor," another developer counters.

What does this change for studios? Teams on 5.8 can wait for the clean-up pass, while agent-first pipelines gain direct MCP hooks into rendering and scene annotation. Whether agent-built engine code holds up under production load will become visible during the MegaJam in November.