Lan asked why Neo wants to explore AI game development with Unity when the course runs on Godot. Astra itself raised Unity in September. This page answers both: what actually happened, what Unity now offers an AI agent, what the studio already owns, and a two-week experiment with a pass or fail line, so the question is settled by a result rather than an opinion.
Nothing was decided against Unity. The prototype went Godot because it was the fastest path to an installable build on a Mac with no Unity installed. That is a logistics fact, not an engine verdict.
| Piece | What it is | Why it matters here |
|---|---|---|
| Unity AI Assistant (Unity 6.3 LTS) | An agent inside the editor that reads the project and can build scenes, write scripts and generate placeholder assets. Included with Pro, Enterprise and Industry seats. Personal seats pay per use in credits. | The studio's Pro seats already carry it. No new bill to start. |
| Unity MCP server (official) | A standard bridge that lets outside agents such as Claude Code and Codex operate the editor: create scenes, manage assets, edit scripts, run tasks. | This is how the kit's Build desk reaches Unity the way it reaches Godot today. |
| Unity's Claude Code plugin (10 Sep 2026) | First-party, distributed through Claude's own plugin directory, bundling 29 Unity skills. | Unity is now maintaining the Claude Code side itself. Less for us to build. |
| Community bridges (mcp-unity, unity-mcp) | Open-source packages that connect Codex CLI, Cursor and others to the editor; actively maintained in 2026. | Codex, Astra's tool, gets the same door. |
| AI Gateway | Routes the assistant's work to third-party models such as Claude or GPT; those calls do not spend Unity credits. | Our seats do the thinking; Unity does the editing. |
| GPT-6 Astra in the wild (from 3 Sep 2026) | Public demos of Astra driving Blender, Godot and Unreal directly, moving menus and building scenes; one showed a full game in about 25 minutes; a round-up thread passed 890,000 views in three days. | This is what Neo pointed Lan to. The public is already doing with Blender and Unreal what we are proposing to do with Unity. |
One caution worth stating: Unity's assistant, its credits and its pricing have moved several times in the past two years. The experiment uses the pieces that are stable (the editor, the official server, the Claude Code plugin) and treats the in-editor assistant as a bonus, not a dependency.
What Lan is right to worry about. Unity has a history of licence surprises (the 2023 runtime fee, withdrawn in 2024), its AI credits are a metered cost for anyone outside Pro, it is Windows-first, and it is heavier for a beginner than Godot. All four are reasons to keep Unity out of cohort 1, and none of them is a reason for the studio not to test it.
| Days | Who | What |
|---|---|---|
| 1–2 | Claude Code + one Studios developer | One Windows PC: Unity 6.3 LTS on a Pro seat, the official Unity MCP server, Unity's Claude Code plugin, Codex through the community bridge. Kit's memory and logging hooks attached. Record every prompt, as for a student. |
| 3–6 | Codex (Astra) leads, Claude Code reviews | Port the RUSH chase loop to Unity: pasar level, police and robbers, two cameras, touch controls, bots. Astra writes; Claude Code tests and merges, exactly the two-lane rule from the course. |
| 7–8 | Claude Code | Port the headless "is it fun" audit (40 rounds, win rates, time fallen) so the Unity build is measured the same way the Godot build was. |
| 9–10 | Claude Code + the farm | Android and Windows builds through the build farm, upload to itch.io under the studio account, Play internal testing. Review gate report. Written result. |