What an agent can do
An agent works through tools, each one a single job with its own checks. The tools refuse what the engine would not load, so an agent’s mistake is caught when it makes it, not when the game runs. The sample games Sky Hopper, PaperKid, Snowline and Lamplight were built this way.
The project and its assets
Section titled “The project and its assets”- Create and open projects, and read and change the project settings.
- Import files, with the import dialog’s options, and cook.
- Create assets (anything the editor’s Create menu makes), and read and edit a data asset’s content: an input map’s actions and bindings, a material, a sound cue.
- Find what uses an asset before deleting it, and check the whole project for broken references.
Scenes
Section titled “Scenes”An agent writes a scene, or a prefab, as XML and has the engine check it before saving: it loads it exactly as the game would and refuses it, with the reasons, if anything is wrong. The servers give it the format, generated from the engine itself, with an example to copy.
In the editor, an agent can also build in an open scene page an edit at a time: create entities, add components, set their properties, spawn prefabs and add script behaviors. Each change is one step you can undo, and nothing is saved until you (or it) save the page.
It can also select entities, move the editor camera, frame what it built and take a screenshot of the viewport, to see the result.
Scripts
Section titled “Scripts”An agent reads the script API as the engine binds it, for Luau or AngelScript, rather than from memory. It creates a script, writes it, compiles it to check it, and cooks it.
Shaders
Section titled “Shaders”An agent creates a custom shader, writes it, and checks it before cooking it: every version of it is compiled, and each error comes back with its line. Then it puts materials on it.
Playing and testing
Section titled “Playing and testing”In the editor, an agent can play the game in the Game tab and test it:
- Start the game, and take screenshots of it.
- Play it with input: keys, the mouse and gamepads, on a timeline, through the project’s input map as a player’s would.
- Watch values while it plays (an entity’s position, a behavior’s field, the game script’s score) and stop early on a condition, such as the player falling off the level.
That is how a playtest turns into numbers an agent can check, and screenshots you can look at.
Exporting
Section titled “Exporting”An agent lists and sets up export presets and exports the game, as Project > Export… does.
Diagnosing
Section titled “Diagnosing”An agent reads the engine’s log, from a marker it writes before trying something, and the engine’s list of known issues, so it can tell a known problem from a new one.
In the editor, an agent can profile the next few seconds: it gets the frame times, the scopes and GPU passes that took longest and the device’s counts, and the capture files to hand you (see The profiler).
The full list of tools, and how to use each, is in the guide every server carries:
docs://McpGuide.md.