Skip to content
kumo

Your engine, connected

kumo finds the engine a project uses and gives it only that engine's tools. Unreal is built in; Godot, Unity and your own engine plug in the same way.

The kumo plugin docks the whole app inside the Unreal editor, beside the viewport, and gives the assistant the editor itself. If Unreal can author an asset type, the assistant can create, edit and inspect it: Blueprints, animation, materials, Niagara, audio and MetaSounds, UI, the Gameplay Ability System, world building, cinematics and the rest, across the engine and its plugins. Every request becomes operations Unreal checks before they run, and new graph nodes land in a tidy layout.

100% of authorable asset types

Every asset type Unreal can author, measured by a coverage ledger the build checks. The report →

Up to 12× fewer tokens

A skill and a command line instead of an MCP server: the assistant loads only what each task needs. The measurement →

With the editor closed

The same operations from a terminal or CI, with Unreal running headless. Headless mode →

UE 5.7 and 5.8

The plugin targets Unreal Engine 5.7 and 5.8, on Windows, macOS and Linux.

kumo recognises a Godot project by its project.godot and a Unity project by its ProjectSettings and Assets folders, and runs each engine’s own tools.

EngineWhat kumo runsIn builds and automations
GodotGodot, headlessimport, check a script, run a script or a scene, test, export
UnityThe editor in batch modecompile, test, run a method, build

Review and sound work leave the board in each engine’s own form: sound graphs for Godot and Unity, cutscene video Godot plays as it is, and game events and remote config from each engine to the studio’s server.

An engine is a connector: a folder that says how to find the engine, what its command line does and which steps it offers to builds. A studio adds its own beside the shipped ones, or overrides one, without code.