Loading…
Blog
Unreal Engine AI agent: what it does in the editor
What an Unreal Engine AI agent is, how it reads, plans, acts and checks inside Unreal Editor, and how Dola's specialist agents keep you in control.
Last updated 4 November 2026
Published 4 November 2026
An agent acts, a chatbot answers
Ask a chatbot how to open a door when the player walks up and you get steps to follow. Ask an Unreal Engine AI agent and it does the steps: it adds the trigger, builds the Blueprint graph, compiles it and tells you what changed.
That needs two things a chat window does not have: a way into the running editor, and tools it can call there. In Dola, the Unreal Editor plugin opens a local bridge to the desktop app, and the agents work through that bridge in your open project.
What an agent loop looks like in Unreal
- Read. Look at the level, the Blueprints and the C++ that the request touches, so the change fits what is already there.
- Plan. Break the request into steps, for example a trigger volume, a timeline and a rotation.
- Act. Call editor tools: add nodes and wire them, set properties, place actors, write a C++ class.
- Check. Compile the Blueprint, read the errors, fix them, and verify the result before saying it is done.
The check step is what separates a useful agent from one that leaves you broken graphs. See how it works on a real graph in Blueprint AI.
One agent or many?
Unreal covers very different kinds of work. Dola splits it across specialist agents for Blueprints, C++, levels, materials, animation, VFX, UI, audio, cinematics, gameplay AI and modeling, each with the tools for its area. The full list is in the agent roster.
Staying in control
- Risky actions ask first in the chat, and you can decline them.
- Changes land in your project like your own edits, so source control shows exactly what moved.
- Chats and project indexes stay on your machine.
- You can use your own model API key, or Dola-hosted models on a paid plan.
FAQ
A model that does not only answer questions but takes actions in your project: it reads Blueprints and code, calls editor tools, checks the result, and keeps going until the task is done or it needs you.
No. NPC AI (Behavior Trees, State Trees, EQS) runs inside your game for players. A developer AI agent runs in the editor for you, and builds things such as those Behavior Trees.
Dola asks first in the chat for risky actions: plugin and config changes, new C++ classes, packaging, force deletes and replacing assets. Blueprint edits are compiled and saved so you can review them like your own.
Start with the getting started guide or read what the Unreal Engine AI assistant covers.