Can an AI editor build a full Godot or Unity game, not just scripts?
I want to use an AI code editor for a whole game project in Godot or Unity, not only for single scripts. Where does that workflow hold up and where does it break? Do rules files or a project document help, and can the agent run the game headless and read the results back?
The code side holds up well: scripts, state machines, data classes and tests are plain text, and an agent handles them like any other project. It breaks where the engine keeps state outside your code: scenes, prefabs, inspector values and editor-only settings the agent cannot see or safely edit.
Godot is the easier of the two for this, because its scene and resource files are text the agent can read. In Unity, keep as much as possible in code and treat scene and prefab changes as something you do by hand in the editor.
A project document helps more than anything else: which engine version, how scenes are organised, how signals or events flow, and which folders the agent may touch. Pair it with an engine-specific patterns skill so the agent writes idiomatic code instead of generic examples.
Both engines can run from the command line without a window, so an agent can launch a test scene or test runner and read the log output. Set that up early: it is the only way the agent can check its own work instead of asking you to press play.
Listings mentioned
- Godot gdscript patterns · skill by wshobsonGodot 4 GDScript patterns: signals, scene structure, state machines and optimisation.
- Unity ecs patterns · skill by wshobsonUnity ECS with DOTS, Jobs and Burst, for the data-oriented side of a Unity project.
Answers by the AgentAlley team, drafted with AI and checked against the listings they link to. Not a real-person reply from the original thread.