BALANCEb425rel/engines-tools3 min read

Unreal Engine 5.9 Preview Tests AI Agents Building the Engine

Epic's early Unreal Engine 5.9 preview tests AI-agent engine development, restores WebAssembly exports, broadens MCP and Python tools, and remains rough ahead of the AI Megajam.

Unreal Engine 5.9 Preview
Unreal Engine 5.9 PreviewPexels / pixabay

Patch notes

  • Unreal Engine 5.9 is predominantly AI-written and tests AI agents developing the engine itself.

  • The early preview mainly supports the upcoming Epic AI Megajam.

  • WebAssembly returns as an export target after being abandoned in Unreal Engine 4.x.

  • Unreal MCP launches automatically and expands across nine tool areas.

  • Expanded Python APIs cover nine areas while Unreal Canvas adds shared human-and-agent workflows.

By Elena Vasquez

Epic Games’ Unreal Engine 5.9 preview puts AI agents to work on the engine itself, with the build predominantly written by AI. The release frames most headline features as tools for AI-assisted production.

This is not a polished feature release. The preview is less finished than previous preview releases and mainly supports the upcoming Epic AI Megajam. Its narrower purpose, the preview says, is “testing and refining AI agent driven development of Unreal Engine itself.” That makes 5.9 a test bed for development methods as much as a set of studio tools.

Agent tools enter the editor

Unreal Canvas gives people and AI agents one shared place to create and refine content. Epic calls it a “shared workspace for people and AI agents for creating and refining content.” It also includes hooks into several generative AI services for images, video, and 3D models.

For studios, Canvas defines a common production surface for human and agent work. That can reduce handoffs when a team mixes manual work with generated images, video, or 3D models. The preview does not name the connected services or publish output benchmarks, so teams must test those integrations within their own pipelines.

By placing people and agents in one content workspace, while expanding the editor operations available through MCP, Epic is testing a broader form of assisted production than isolated prompt tools.

Unreal MCP updates make editor control through connected tools more practical. It now launches automatically with the editor and offers more reliable connections. Its toolsets now cover rendering, source control, profiling, debugging, gameplay testing, geometry, audio, UI, and level creation.

That expansion gives MCP-connected workflows access to both creative and technical editor operations. Automatic startup also removes a manual editor-launch step for teams adopting MCP. Connection reliability still matters because these tools touch core production systems rather than isolated documents.

WebAssembly returns as an export target

WebAssembly is back as an export target in Unreal Engine 5.9. Epic abandoned the target during the Unreal Engine 4.x era. The 5.9 implementation ports the old code base back into the engine and treats AI agents as an experimental part of the feature.

For teams planning browser delivery, the restoration revives an export option, although its experimental status makes this preview evidence for feasibility rather than a production guarantee.

The preview labels the work experimental and gives no browser, performance, or compatibility matrix. Studios should treat WebAssembly as an evaluation target, not a production commitment.

Python scripting expands

Expanded Python scripting adds APIs for audio, MetaSounds, modeling, physics, Niagara, materials, PCG, networking, and UI. The list turns those editor systems into scriptable building blocks for procedural tools, validation, and repetitive production work.

By putting those systems behind one scripting interface, Epic gives tools programmers a broader common layer for internal automation, procedural workflows, and editor extensions across projects.

This change matters most to technical artists and tools programmers, who can cover more editor work through one scripting layer. The preview does not describe API stability, which teams need before embedding these calls in shipped tools.

What does this change for Unreal Engine teams?

Unreal Engine 5.9 shifts the AI discussion from content generation toward the engine’s development stack. It combines a shared human-and-agent workspace, broader MCP access, wider Python control, and a returning WebAssembly target.

For studios, the useful response is a controlled evaluation of browser exports, MCP-assisted workflows, Canvas integrations and Python automation, with production adoption deferred until Epic resolves preview readiness and API stability.

The limitations are equally concrete. This is an early, less-polished build, and several features listed in the Unreal Development Roadmap may not be ready for 5.9. The preview package points developers to a 5.9 MegaJam preview, release notes, and a video demonstrating SimplyStream, identified as a web export solution.

The package provides no final feature list or release date. The next useful signal is how much of the roadmap survives the polish period between the AI Megajam build and the final 5.9 release.

via unrealengine.com (Original)

Share this article:

More from Elena Vasquez

Elena Vasquez

Show full bio

Staff writer covering regulation, policy and their impact on video game industry at Game Dev Wire.

248 articles