Is there a free trial?

Yes. Start a free 3-day trial from your account at codefizz.dev/account, no credit card required. The trial unlocks the full Pro plugin for UE 5.6, 5.7 and 5.8 on one machine. When it ends, upgrade to a paid plan and the same key keeps working with five machine seats. There is also a separate free, open-source community edition (Unreal MCP).

Which Unreal Engine versions are supported?

UE 5.6, 5.7 and 5.8 on Win64. Each release ships as a separate binary plugin matched to the engine ABI, and the cfa CLI downloads the build that matches the engine you point it at. Future engine versions are added as they release.

Which platforms are supported?

Right now, Windows 64-bit only. The plugin is built and tested on Windows for this first release. Linux and Mac support are on the roadmap and will be added when there is clear demand from paying customers. I would rather wait until I can properly test those builds end to end than ship binaries I have not run myself. If you are on Mac or Linux and would buy the plugin today, drop a note in Discord or send me an email. That is how the priority for adding those platforms gets set.

Do I need a license key, and how do I enter it?

Activate from the CLI with your CodeFizz website account. Install or update the free cfa CLI, run cfa login, and sign in in the browser. That machine is activated and the editor plugin reads the same sign in, with nothing to paste inside Unreal. Offline grace still applies. A license key remains under License and billing for recovery and older cfa builds (cfa login --key), but new setups should use browser login only.

What MCP clients work with the plugin?

Any MCP-compatible client. The plugin exposes a TCP bridge and the Go CLI ships separately, so Claude Code, Cursor, VS Code, Gemini, and other MCP hosts all work out of the box.

Can I cancel anytime?

Yes. Open your account at codefizz.dev/account and click Manage billing to open the Polar billing portal, then cancel in one click. You keep access through the end of your billing period and stop being charged afterward.

What happens to my installed plugin if I cancel?

A subscription earns you ownership, not just access. Once you have paid for twelve months, the version you have at that point is permanently yours: cancel any time after that and it keeps running on your machines with nothing more to pay, you simply stop receiving new releases. Annual plans reach that point with their first payment, since they cover a year up front. Before twelve months your access runs alongside the subscription, so it pauses if you cancel and picks straight back up when you resubscribe, with the months you already paid still counting toward the permanent license. Lifetime Pro skips the wait entirely and is the only plan that never stops receiving updates. Anyone who subscribed before 5 August 2026 keeps their original terms.

Do you offer refunds?

No refunds on subscriptions, since the plugin is downloadable software you get immediately. You can cancel any time and keep access through the end of the period you have already paid for. Lifetime Pro is a one-time purchase with nothing to cancel: it is fully refundable within fourteen days if you have not downloaded the plugin yet, and a refund ends the licence. If you ran into a real bug or a feature you reasonably expected to be there, email me and we will figure it out. Full policy on the Refund Policy page in the footer.

Why is Patron more expensive when I get the same plugin?

Patron is for people who want to influence the direction of CodeFizz Editor Agent, with voting, a private roadmap, priority answers, and direct input on new APIs. If you just need the plugin and updates, stay on Pro.

Is there a free version?

Yes. There is a free, open-source community edition (Unreal MCP) that gives you the core bridge and a basic command set, which is great for trying the workflow. The paid Pro edition is the fully maintained build with the complete toolset (Niagara, PCG, StateTree, Insights, and more), regular updates, and support. The open-source edition is linked in the footer.

Studio / team licensing?

For studios needing multiple seats, an enterprise tier is available off-platform. Contact directly for pricing.

Is there a lifetime or one-time payment option?

Yes. Lifetime Pro is a one-time payment of $399 USD (list price $499) that gives you the full CodeFizz Editor Agent plugin and every future update permanently, with no subscription and nothing to renew or cancel. It covers UE 5.6, 5.7 and 5.8 plus engine versions added later, five machine seats, and Pro Discord access. Prices are localized, so you are charged in your own currency at checkout.

What does Lifetime Pro include?

Lifetime Pro is the complete Pro plugin for every supported Unreal Engine version, yours permanently. That means all 900+ commands across Blueprints, Materials, Niagara, PCG, StateTree, Control Rig, Mutable, audio and Insights profiling, every future update and every new command at no extra cost, five activated machines, and Pro Discord channel access. There is no renewal date, no expiry, and no second invoice. You pay once and it keeps working, including on Unreal Engine versions that do not exist yet.

Back to all posts

Workflow6 August 2026 · 7 min read

Using an AI assistant inside Unreal Engine 5: one real run, every command

A real run: what I asked for, every command the assistant actually ran, the bit it got wrong, and how it fixed itself. Plus what it is genuinely good at, and what it is not.

You point an AI assistant at a running Unreal Editor, ask for something in plain English, and it calls real editor commands to build it. Not code you paste in afterwards. The asset appears in your content browser while you watch.

I build the plugin that does this, so take the enthusiasm with the appropriate pinch of salt. What I can do is show you an actual run, including the bit where it got something wrong and fixed itself, because that part is more convincing than any feature list.

Unreal Engine viewport showing a rigged character with control gizmos on the hands, elbows, hips, knees and feet, alongside the Anim Outliner listing the full control hierarchy. — One of these runs, finished. A Control Rig with the whole control hierarchy built, gizmos measured from the mesh rather than eyeballed, and IK on all four limbs. Nothing here was placed by hand.

Getting it talking to the editor

Three commands and your project is reachable. The plugin runs a small bridge inside the editor and the CLI talks to it. Your AI assistant then drives the CLI.

Install the free CLI:

bash

irm https://codefizz.dev/install.ps1 | iex

bash

cfa login

Install the plugin into your engine:

bash

cfa install-plugin "E:/Unreal/UE_5.8"

Then the step people skip, and then regret skipping:

Teach the assistant what the commands actually do:

bash

cfa skill install

Without that, the model guesses at parameter names. With it, it looks things up before calling anything. The difference in how often the first attempt works is not subtle.

Check the editor is reachable:

bash

cfa health_check

What I asked for

With the editor open, I asked Claude for a spark effect. Nothing clever, phrased the way you would ask a colleague:

"Make me a Niagara system called NS_Sparks with an emitter that throws sparks upward. Give it a decent spawn rate and let me tint the colour from Blueprint."

What it actually ran

It did not write me a tutorial. It called commands, in this order:

Created the system:

bash

cfa create_niagara_system --asset-path "/Game/VFX/NS_Sparks"

Added an emitter from a template:

bash

cfa add_niagara_emitter --system-path "/Game/VFX/NS_Sparks" --template "Fountain" --emitter-name "Sparks"

Looked up a module rather than guessing the path:

bash

cfa list_niagara_modules --search velocity

Added it to the right stage of the stack:

bash

cfa add_niagara_module --system-path "/Game/VFX/NS_Sparks" --emitter-name "Sparks" --module-path "/Niagara/Modules/Update/Velocity/VortexVelocity.VortexVelocity" --script-usage ParticleUpdate

Set the spawn rate:

bash

cfa set_niagara_module_input --system-path "/Game/VFX/NS_Sparks" --emitter-name "Sparks" --module-name "SpawnRate" --input-name "SpawnRate" --value 500 --script-usage EmitterUpdate

Exposed the colour so gameplay can drive it:

bash

cfa add_niagara_user_parameter --system-path "/Game/VFX/NS_Sparks" --parameter-name "SparkColor" --parameter-type "LinearColor"

Compiled it:

bash

cfa compile_niagara_system --system-path "/Game/VFX/NS_Sparks"

The bit that went wrong

The velocity module landed in the wrong stage first time. It compiled fine and the particles did nothing, which is the most annoying category of Niagara bug because there is no error to read. A module in EmitterUpdate that belongs in ParticleUpdate is simply ignored.

What made it recoverable is that the assistant could look:

Read the stack back:

bash

cfa get_niagara_modules --system-path "/Game/VFX/NS_Sparks" --emitter-name "Sparks"

It saw the module sitting in the wrong stage, removed it, added it again with the right --script-usage, and recompiled. I did not tell it to do that. I said "the sparks are not moving".

This is the whole point

An assistant that can only write is guessing. One that can compile, read the result back, and correct itself is doing the job. Every capability list in this space is really a proxy for whether that loop closes.

How much of the editor it can actually reach

Niagara is one category out of 28. The reason I keep pushing on coverage is that a tool which reaches half the editor sends you back to clicking for the other half, and a workflow with a hole in it is not really a workflow.

What is reachable today, all of it editor side and all of it callable from a prompt:

Blueprints, graphs, components, structs, interfaces
Materials, functions, instances, layers, Custom HLSL
Niagara down to scratch pad HLSL
Control Rig hierarchies and RigVM solve graphs
PCG graphs and runtime generation
Procedural Vegetation, grow a tree and export it
Mutable, modular characters and swappable outfits
Sequencer, including Movie Render Queue
MetaSounds, Sound Cues, submixes
Behavior Trees, Blackboards, EQS
UMG widget trees and MVVM viewmodels
Insights profiling, read a trace and get a verdict

That is 900+ commands across 28 categories, and the number is generated from the CLI source rather than estimated, because I got tired of it being wrong in five places at once.

The profiling one is the one that changes how people work. The assistant can run a trace, read which node cost the frame, change the thing, and re-run to check it actually helped. That is a loop you would otherwise do by hand a dozen times an afternoon.

What it is not good at

Taste. It will build the effect you described, not the effect you imagined, and the gap between those is your job. I have not once had it produce something I would ship without touching.

Where it earns its place is the tedious, well-defined, repetitive half: the Blueprint graph you have wired forty times, the material you can describe faster than you can build, renaming a hundred assets and fixing the redirectors afterwards.

One thing that surprises people about engine versions

Epic ships its own MCP server now, and it is worth trying before you pay anyone anything. The catch is that it exists in Unreal Engine 5.8 only. On 5.6 and 5.7 there is no plugin to enable and no flag to flip, because engine features ship with engine versions and are not backported.

You can check your own install in about ten seconds. Look for these folders:

<EngineRoot>/Engine/Plugins/Experimental/ModelContextProtocol/
<EngineRoot>/Engine/Plugins/Experimental/ToolsetRegistry/
<EngineRoot>/Engine/Plugins/Experimental/Toolsets/

Present on 5.8, absent on 5.7 and 5.6. That matters more than it sounds, because studios mid production do not upgrade engine versions to try an experimental feature. A project on 5.7 has a build pipeline, a plugin set and a QA baseline pinned to it.

So if you are on 5.6 or 5.7, third-party is the only route there is. Mine is built and tested separately against all three versions, because the engine ABI differs between them and a single universal binary is not a thing that can exist.

And if you are on 5.8, try Epic's first. It is free and it is first party. The question to ask after an hour with it is simply how much of the list above you still need, because that is the only thing the decision actually turns on.

Trying it yourself

The full Niagara walkthrough, with every failure mode spelled out, is in the docs. If you would rather see the whole command surface first, it is searchable on the tools page.

Try it on your own project

CodeFizz Editor Agent

Everything in this post was one assistant, one editor, and the commands above. 900+ commands across 28 categories, on UE 5.6, 5.7 and 5.8. Drive it from Claude Code, Cursor, VS Code, or any MCP client.

Three day free trial. No card, nothing locked off, and it runs on your real project.

Start the free trial Read the quick start Ask in Discord

Want a corner of the editor reachable that is not covered yet? Say so in Discord. Most of what exists came from exactly that.

Loading…

Stop bouncing between AI and Unreal.

Drop the plugin into your project, point your MCP client at it, and let your AI actually build inside the editor.

Get the plugin Read the docs