Reports

Unity AI and Unreal's AI Tools in 2026: What the Engines Are Actually Shipping

Both big engines now put an AI agent inside the editor, and both are racing to become the thing your own AI plugs into. We read the docs, pricing pages, release notes, survey data and developer reaction to separate what Unity AI and Unreal Engine's AI tools do today from what their keynotes promise.

By the CreateGame.ai editorial teamOctober 9, 202621 min read

What changed in 2026

A year ago the AI story at both engine vendors was a set of separate experiments. Unity had Muse and Sentis, Epic had a documentation chatbot for Fortnite creators. In 2026 the pieces converged around one idea: expose the editor to an agent. The terms differ, and so do the business models, but the architecture is the same. An assistant lives inside the editor and can read the scene, edit it and run it. A protocol (MCP, or Unity's command-line interface) lets outside agents do the same. And a growing share of the work is done by third-party frontier models, not by the engine company's own.

That shift is the main thing we want to explain. It matters for the price you pay, the data you share, the lock-in you accept and the legal risk you carry.

Unity AI

What it is, and what happened to Muse and Sentis

Unity AI is the umbrella name for what replaced Unity Muse. Unity rolled out the first Unity AI beta with Unity 6.2 in August 2025 (CG Channel), and on 5 May 2026 it opened a broader beta to developers on Unity 6.0 or later. Unity's own post says it plainly: "These tools are not Unity Muse," which it describes as a separate, deprecated tool built on Unity's first-party models, whereas the new suite runs inside the Editor on third-party frontier models accessed through Unity Cloud (Unity, 5 May 2026).

Sentis, the runtime library for running neural networks inside shipped games, survived under a new name. Unity's 6.2 documentation lists it as the Inference Engine package (com.unity.ai.inference, version 2.3.0 for 6000.2), and forum posts confirm the rename happened from version 2.2 (Unity docs). Unity is careful to keep the two apart: the AI tools are for the developer's authoring workflow, and Inference Engine is for the player's runtime experience (Unity, July 2026).

The four components

As of Unity's explainer page dated 28 July 2026, Unity AI consists of four parts (Unity):

1. The in-editor AI assistant. A panel that sees the live project: scene hierarchy, settings, packages, code, asset library, platform targets and serialized Inspector data. It has three modes. Ask answers questions, Plan breaks a task into a reviewable list, and Agent executes end to end, writing C# scripts, modifying components and creating prefabs. Unity says every change is reversible and generated assets carry metadata identifying them as AI-made (Unity).
2. AI generators. These make materials, sounds, cubemaps, sprites and 3D models from the Editor. Unity's framing is notable: the intended use is "dev-stage placeholders," with the metadata tag there so assets "can be audited and replaced before shipping" (Unity).
3. The AI Gateway. It lets verified third-party agents (Claude, Codex, Gemini) use Unity's project context. Crucially for cost, an agent connected this way "runs on the developer's existing subscription" and does not consume Unity AI Credits (Unity).
4. The MCP server. The outside-in control path for IDEs and CLI agents. Here Unity has already changed course. Its docs now say the MCP server inside the assistant package is deprecated and replaced by the Unity command-line interface, which includes its own MCP mode and direct commands that are, in Unity's words, faster and use fewer tokens (Unity docs).

Unity's page also contains a sentence that is worth quoting against the company's own CEO. The tools "aren't a way to prompt a finished game into existence. This is coding and authoring assistance" (Unity). In February 2026 Matthew Bromberg told investors that Unity would announce a beta of an upgraded Unity AI at GDC, and trade coverage reported he said it would let developers prompt "full-fledged casual games" into existence, aimed at non-programmers (Gigazine, citing Game Developer). The shipped product, by the vendor's own description five months later, is an authoring assistant. That is a reasonable product. It is not the one in the earnings call.

What it costs

Unity sells the AI tools through credits tied to your plan. The pricing page we reviewed on 9 October 2026 lists the allowances below (Unity pricing).

Personal gets a 14-day trial of the AI tools, then a paid subscription is required for the 1,000 monthly credits. Pro (listed at $210 a month, or from $2,310 a year) includes 2,000, and Enterprise and Industry include 3,000. Concurrent MCP connections are capped at 3 on Pro and 5 on Enterprise and Industry. Third-party sites report the Personal add-on at about $10 a month, but we could not find that figure on Unity's own pages and treat it as unconfirmed.

The terms are what developers should read. Unity's AI Credits Beta Terms (last updated 28 July 2026) define a credit as a unit that "reflects the computing resources consumed" to produce an output. Credits are not refundable except as required by law, and they are purchased in advance (Unity). Excerpts of the same terms surfaced in search add that unused credits expire at the end of the subscription period and that Unity can change credit pricing during the beta without refund; we did not see those lines in the portion we fetched, so check the live document before you buy. Unity does not publish a per-action credit price, so we cannot give you a cost per task.

Developer forums show the friction. Thread titles we saw in search results include "How quickly are credits consumed in Unity AI?" and "Unity AI is way out of reality on cost," and the open-beta thread has a tester complaining that Agent mode splits work into many small scripts each needing approval, which makes it slow unless Autorun is enabled (Unity Discussions; open-beta thread). We could not load those threads directly, so we are relying on titles and search snippets, and forum posters are not a representative sample. For a fuller picture of what token spend looks like outside the engine, see our cost breakdown for making a game with AI.

Our reading of the economics: the Gateway is the cheapest route if you already pay for a frontier model, because Unity's own page says that route does not burn credits. The metered assistant is for people who want the integrated experience and do not already subscribe to anything. That makes the credit meter a tax on convenience, which is a viable business, but it explains why the loudest complaints are about consumption rates.

The terms-of-service wobble

One more item for anyone building a pipeline around agents. After Unity's terms update of 30 June 2026, some developers read clauses as banning unapproved AI agents, command-line interfaces and MCP. A trade report said Unity's support account responded on Reddit that the restrictions do not apply to MCP or AI integrations that work only with the local Editor and project files, and that no formal statement had been issued at publication time (Roboin). We could not open that article's body, only the summary in search results. If your tooling touches Unity from outside, read the live terms and ask Unity in writing.

Unreal Engine

The pieces Epic has shipped

Epic's list is shorter on branding and longer on plumbing.

Epic Developer Assistant. It began as a web assistant for Fortnite creators using Unreal Editor for Fortnite. In September 2025 Epic extended it to Unreal Engine 5.6 documentation questions and C++ generation, and said Unreal Engine 5.7 would bring it into the editor itself (Epic Developer Community). Coverage of the 5.7 release (late 2025) lists an in-editor AI assistant alongside production-ready PCG and Nanite Foliage (Inven Global). We could not open the 5.7 release notes section describing it, so we cannot tell you its exact capabilities. One early forum reply to the announcement said the poster would rather "epic focus on other areas" (Epic forum).

An MCP server in Unreal Engine 5.8. Released on 17 June 2026, UE 5.8 adds an experimental MCP plugin that "enables agentic AI systems to connect to the Unreal Editor," so they can understand the engine and project and help build assets or systems, with a toolset for animation features appearing in the release notes (Epic release notes). In the keynote demo, Claude Code placed objects from an asset library into a living room and built a city that adjusted as parks were added (Engadget). Epic does not meter this. You bring a model and pay that model's vendor.

MetaHuman 5.8. MetaHuman is the nearest thing Epic has to a character-AI product, though most of it is machine-learning-assisted tooling rather than generative AI. The 5.8 release notes describe an experimental MetaHuman Crowd plugin that scales from tens to thousands of characters using Mass, a "Mesh to MetaHuman" workflow that converts a humanoid mesh of any topology into a rigged MetaHuman, and updated facial animation models for the MetaHuman Animator (MetaHuman 5.8 release notes). Nothing in those notes involves text-prompted character generation.

Unreal Engine 6

Epic teased Unreal Engine 6 in May 2026 and gave details at the State of Unreal keynote on 17 June: it merges Unreal Engine 5 and UEFN, with early access targeted for late 2027 and a full release 12 to 18 months later (Engadget). The AI position, in Epic development lead Marcus Wassmer's words as reproduced by Aftermath, is that "LLMs, generative AI models, and tools like Claude and Codex" will play "a central role" and that much of the effort goes into exposing engine capabilities "through the MCP protocol" so developers can mix and match models. Epic is also improving the Epic Developer Assistant as an optional, turnkey tool (Aftermath, quoting Epic's post). Epic says UE6 will let you "bring your own favorite models," battle-tested internally and in UEFN (Engadget).

Two things are worth keeping separate. What exists today is an experimental plugin in 5.8. What is promised is a deeper integration in an engine that does not yet have a public build. We would plan around the first and watch the second.

Context: Godot and Roblox

Godot has taken the opposite stance. In a post on 30 June 2026 the Godot Foundation said AI-generated contributions had worsened a reviewer shortage and were "demoralizing," because feedback absorbed by a machine does not mentor a future maintainer (Godot Foundation). Trade coverage reports the resulting policy bans autonomous agent use and "vibe coding," bars AI from generating substantial code, allows menial help such as completion and regex, and requires human review of every PR (GamingOnLinux). That concerns how Godot is built, not how you build with it, and nothing stops you from pointing an external agent at a Godot project. Search coverage also quotes a lead maintainer saying the project has no plans to build AI features into the engine, which we saw only through secondary reports. Godot matters here because it is where some dissatisfied developers are heading: GDC found 11 percent of newer indie developers use it as a primary engine (GDC).

Roblox has the opposite incentive, because its creators are its supply chain. Its April 2026 post on an "agentic" Studio says 44 percent of the top 1,000 creators use Roblox Assistant or third-party AI tools through MCP to plan, build and test their games, adds an improved Planning Mode, and exposes features to outside tools through Studio's built-in MCP server (Roblox). The footnote defines the group as creators ranked by Robux spent who used Assistant or MCP between 6 March and 7 April 2026. It is a statistic about the best-resourced creators, not the platform's average, and Roblox has not published broader figures. The pattern, though, is the same as Unity's and Epic's: the platform becomes a surface for whichever model the creator prefers.

What developers actually think

The numbers

The most reliable data we have is the GDC 2026 State of the Game Industry survey: more than 2,300 professionals, fielded 4 November to 5 December 2025, with questions customised by role, which means GDC cautions against strict year-on-year comparisons (GamesBeat; GDC).

The headline is that 52 percent say generative AI is having a negative impact on the industry, against 30 percent a year earlier and 18 percent the year before, while 7 percent call it positive (13 percent in 2025). Negative views are strongest among visual and technical artists (64 percent), game designers and narrative staff (63 percent) and programmers (59 percent). Executives and business-operations staff were the most positive, at 19 percent each.

Use is a different story from sentiment. Thirty-six percent of respondents use generative AI tools as part of their job. But the split by employer is stark: 30 percent at game studios, against 58 percent at publishing, support and marketing firms, and 58 percent among business professionals. The most used tools are chat assistants (ChatGPT 74 percent, Gemini 37 percent, Copilot 22 percent).

Among those who use it, the dominant use is research and brainstorming (81 percent), followed by daily tasks and code assistance (47 percent each) and prototyping (35 percent). That profile is revealing for the engine story. The in-editor assistants are aimed at the 47 percent code-assistance and 35 percent prototyping slices, which are real but smaller than the headline suggests, and the creative-production uses the survey's most skeptical respondents fear (art, narrative) are exactly what Unity labels "placeholders."

GDC's engine data also matters for who is spending on this race. Unreal is the primary engine for 42 percent of respondents against Unity at 30 percent, with Unreal stronger at AA (59 percent) and AAA (47 percent) studios and Unity still the majority choice (54 percent) at older indie studios (GDC). Both companies are adding AI to a user base that is, on balance, wary of it.

The reaction to Epic's announcement

The clearest case study is the UE6 reveal. Aftermath's coverage, which is opinionated and should be read that way, reported that the developers of Vampire Survivors, Poncle, said they were "reviewing" a forthcoming Fortnite collaboration in light of Epic's AI plans, and quoted video game lawyer Haley MacLean on Bluesky arguing that "AI cannot assign copyright" and that output generated in an engine would not be ownable in the way publisher agreements assume (Aftermath). Creative Bloq reported worry about Blueprints, and 80.lv summarised a split between excitement and concerns about authorship and traditional art pipelines, while also noting that the 5.8 feature list pleased many developers (80.lv). We could only read the introduction of the 80.lv piece. We have not seen confirmation that the Poncle collaboration was cancelled and do not claim it was.

Epic's counter-argument, via Wassmer's post, is that studios wary of AI can ignore the features. Tim Sweeney's wider position is that AI "will be involved in nearly all future production," which is the reasoning behind his criticism of Steam's AI labels (below).

The rules that shape what ships

Steam disclosure

Valve's content survey asks developers to declare AI use in two categories: pre-generated content that ships with the game and live-generated content created while the game runs, with an extra requirement to explain guardrails for the latter (Steamworks documentation). Valve has also narrowed the scope. Reporting on its January 2026 rewrite says disclosure is no longer needed for efficiency tools such as code assistants, while content players see, including store and marketing assets, still must be declared (Slashdot; sources differ on whether the date was 16 or 19 January).

The best dataset on what has followed comes from Pax Dei co-founder Sulka Haro, who ran a census of 53,597 Steam releases from mid-2023 to mid-2026. The share carrying an AI disclosure was 10.9 percent in 2024, 19.9 percent in 2025 and 30.8 percent of 2026 releases through July (PC Gamer; Haro).

Haro's other findings are more interesting than the headline. Monthly AI-flagged launches went from about 13 before the field existed to about 530, while non-AI launches rose only from roughly 1,030 to 1,320, so 60 to 90 percent of the growth in monthly Steam releases is AI-flagged games. Yet 87 percent of AI-flagged games are commercial non-performers, and a flagged game reaches a modest success threshold (about 100 reviews) at roughly 55 percent of the non-AI rate, a ratio that has not improved in two years. He extrapolates to half of releases by 2027 to 2028 and labels that a scenario rather than a forecast. Two caveats from the same source. The field measures what developers choose to tick, not verified use, and the disclosure only became possible in January 2024, so the 2023 figure is structurally near zero.

Sweeney thinks the labels are a mistake. In a June 2026 PC Gamer interview he called them "really irresponsible" of Valve (Video Games Chronicle), and in November 2025 he argued a "made with AI" tag suits art exhibits and licensing marketplaces but "makes no sense for game stores" (Engadget). The irony is that Epic's Fab marketplace, a licensing marketplace of exactly the kind he describes, requires sellers to tag generative-AI assets as "Created With AI" while keeping them on sale, with a user filter that is off by default (80.lv). We found no equivalent rule on the Epic Games Store, but that comes from a single secondary source.

Labor and SAG-AFTRA

The strongest legal constraint on game AI so far is a contract. SAG-AFTRA's members ratified the Interactive Media Agreement in July 2025 with 95.04 percent in favor, ending a 320-day strike that, as The Wrap noted, was spurred solely by artificial intelligence (The Wrap). Companies must tell performers about all the ways AI will be used on their voice, likeness and movements and obtain written consent; reporting on the deal adds minimum rates for digital replicas and a right for performers to withdraw consent for new AI material during a strike, with traditional tools such as noise reduction and pitch correction carved out (TheWrap on deal details). A law-firm summary lists Epic's subsidiary Llama Productions among the covered companies (Frankfurt Kurnit), and about seven weeks before the vote, in May 2025, that subsidiary had been the target of an unfair labor practice charge over an AI-generated Darth Vader voice in Fortnite (Proskauer). We did not find the outcome of that charge.

The practical consequence for studios using engine AI: text and code assistants are largely outside the agreement, while synthetic voice work built on a performer's voice is not. Engine vendors provide no cover here. Unity's generators are described as placeholder tools, and its docs say a tagged asset should be replaced before shipping.

Who owns the output

A different legal constraint applies to everyone. The US Copyright Office's January 2025 report concluded that, with current generally available technology, prompts alone do not give a user enough control to count as the author of the output, though human selection, arrangement and modification of AI output can be protected (summary by Foley). On 2 March 2026 the US Supreme Court declined to hear Thaler v. Perlmutter, leaving in place the appeals court's holding that a work produced autonomously by a machine is not eligible for copyright (Mayer Brown). A denial of review is not a ruling on the merits, and the Office's report is guidance, not law.

For a small studio this is concrete. Code you edit and art you substantially rework are the safer ground. Raw generated meshes and sprites dropped in unchanged may be unprotectable and therefore copyable by anyone. We found no Unity commitment to indemnify developers for infringement claims over generated assets; Unity's documents describe metadata tagging and partner-model safeguards, and the indemnity language we saw runs from the user to Unity. Ask Unity's sales or legal team before shipping generated assets in a commercial title. For which image tools are strongest in practice, see our ranking for game art.

Our assessment

Three claims, argued from the evidence above. They are our opinions.

The engine is becoming the harness. Unity's Gateway and CLI, Epic's MCP plugin and Roblox's MCP server all do the same job: let the creator's preferred model drive the tool. This is probably good for developers in the short run, because the best models change every few months and an engine that hardcodes one would age badly. It also changes what engines compete on. Unity's moat is its project-aware context and its credits meter. Epic's is that UE6 ships the same hooks free. If our reading is right, the metered in-editor assistant is the weakest part of Unity's offer, because the Gateway undercuts it, and Unity's own pricing page quietly encourages that by making the Gateway free of credits. For how the models behind these agents compare on game code, see our look at the best AI for coding games.

The adoption gap is a trust gap, not a capability gap. The GDC numbers show heavy use among managers and marketers and light use at studios, with the sharpest opposition from the artists, designers and programmers who would operate the tools. Engine vendors are shipping into that. Epic's UE6 reaction and Godot's contributor policy suggest the backlash is as much about authorship and control as about quality. The vendors that make AI features optional and visible (Epic says studios can ignore them, Unity tags every generated asset) are making the right call, whatever the keynote language.

The market signal from Steam is mixed, and should temper both camps. Roughly a third of new releases now disclose AI use, and almost all of the growth in release volume is AI-flagged. Yet those games convert to modest success at about half the rate of others, per Haro, and the sample is dominated by games that never find an audience. That is consistent with the idea that AI lowers the cost of shipping without lowering the cost of being good. It is not evidence either that AI games cannot succeed or that they will, and the newest models are not yet reflected in games still in development, as Haro himself notes.

What would change our minds: Unity leaving beta with published per-action pricing and a stable agent mode; a UE6 early-access build whose AI features are demonstrably better than a bring-your-own model through MCP; independent evidence of production time saved in shipped games; or a clarified Unity position on agents in its terms. If you want the longer-run picture of AI that generates whole worlds, rather than assisting inside engines, we covered it in our piece on world models and the future of game development, and we compare tools that skip the engine entirely in AI game makers compared.

How we reviewed this

We reviewed published material: Unity's pricing page, its AI tools explainer, blog, credits terms and CLI documentation; Epic's UE 5.8 and MetaHuman 5.8 release notes, forum announcement and keynote coverage; Roblox's newsroom post; the Godot Foundation's contribution-policy post; Steamworks documentation; the GDC 2026 State of the Game Industry write-ups; Sulka Haro's Steam census as reported by PC Gamer and in his own post; and press coverage of SAG-AFTRA's agreement, the Copyright Office report and the Thaler decision. We did not use Unity AI or Epic's tools hands-on, and we ran no benchmarks. Nothing here is a test result.

What we could not verify. We did not read the GDC full report, only GDC's summary and press coverage of it; secondary sites quote a 52 percent figure for "company use of generative AI" that we could not find in GDC's own summary, and we do not use it. We read the SAG-AFTRA deal terms only through press and law-firm summaries. We could not open Unity's forum threads, Roboin's article body, the Unreal 5.7 release notes on the in-editor assistant, the 80.lv UE6 article beyond its summary, or Valve's January 2026 announcement. The $10 monthly Personal add-on price is third-party and unconfirmed, and the Godot "no AI features" statement comes from secondary reporting. Steam figures count self-reported disclosure. The status of the SAG-AFTRA charge against Llama Productions is unknown to us.