Meet your AI teammate for Unreal Engine

Code Maestro now drives the Unreal Editor, reads any Blueprint, understands your entire C++ codebase as a graph, and writes the code to match — so you spend less time spelunking through a 2,000-file project and more time shipping.

Every Unreal project eventually becomes a maze

Blueprints call into C++, C++ fires delegates back into Blueprints, replication is scattered across a dozen files, and the one person who remembers how it all fits together is on vacation. Onboarding a new engineer takes weeks. Tracking down a desync bug takes a day.

Code Maestro is an AI teammate that lives inside that complexity for you. Ask it a question in plain English and it answers from a real understanding of your project — not a guess. Ask it to make a change and it drives the editor, writes the C++, and compiles it. Here's what that looks like today.

Drive your editor by just asking

Code Maestro connects straight into the Unreal Editor with 200+ live tools — plus its own 2D Studio for generating textures and VFX sprites on the spot. Anything you'd click through by hand, you can describe instead, and it runs the whole chain for you.

“Create a 10×10×4 room with lighting and a concrete texture”

It spawns the floor and four walls, places three point lights, generates and applies a concrete material, and adjusts every transform — one sentence, a finished room. Need an ability icon or an explosion sprite sheet? 2D Studio generates it, imports it, and wires it into a material or a Niagara emitter — no round trip to a designer.

Understand any Blueprint — and turn it into C++

Blueprints are great until they're 80 nodes deep and nobody wants to touch them. Code Maestro reads the graph, explains it in plain language, finds the broken pin behind a compile error, and — when you're ready — rewrites the whole thing as clean C++ with every UE decorator in place.

“Extract this Blueprint's logic into a C++ class with all decorators”

It reads the graph, generates the .h and .cpp with UCLASS, UPROPERTY and UFUNCTION macros, writes the files, and compiles through Live Coding. Blueprint to C++ in minutes.

Your whole project as a queryable graph

This is the part that changes how the work feels. Code Maestro parses your C++ into a knowledge graph — classes, delegates, replication, modules, cross-file links — and answers structural questions in milliseconds instead of burning through your codebase token by token.

• “Which classes depend on AHealthComponent?” — 12 direct, 38 transitive, grouped by module, with risk flags.
• “How would changing AWeaponBase.h affect the project?” — a full blast-radius map across four modules in 300ms.
• “Find dead code with no callers.” — real candidates, with engine callbacks filtered out.

Graph queries answer in milliseconds and use up to 99% fewer tokens than reading files one by one — so the assistant stays fast and accurate even on a 2,000-file project.

Ship multiplayer without the desync nightmares

Replication bugs are the worst kind — invisible until they aren't. Code Maestro audits your replication and RPC topology, flags the properties that will quietly desync, and writes the fix.

“Why isn't health replicating to the client? It's always 100%”

It audits the topology, finds that Health was declared but never added to GetLifetimeReplicatedProps, generates the DOREPLIFETIME_CONDITION line, writes it, and compiles. Bug fixed. The same depth applies to the Gameplay Ability System — ability lifecycles, GameplayTags, effects and costs all mapped out — and to everyday feature work: generate a replicated AWeapon, add a server function with an authority check, fix a build error, compile.

What's next

Today's foundation — live editor control, the C++ parser, the knowledge graph, Blueprint reading and code generation, 2D Studio — is already shipping. Next on the roadmap: a full Blueprint↔C++ pipeline, version-control integration, a build-error auto-fix loop, a 3D Asset Studio, and long-running agents that keep working while you don't.

See the full capability breakdown, with live examples for every layer →