Godogen

Godogen

Autonomous game development for Godot (C# or GDScript), Bevy, Babylon.js, and three.js with Claude Code and Codex.

Watch the demos · Prompts

Describe a game. The agent builds it, generates assets, runs the engine, and proves the result — as a live game you watch and steer, or as a recorded video when you're not there. It reads the situation and decides which, in the run.

This repo is not a game. It is the source for a generator that produces games: godogen -> game repo -> game. You publish into a fresh game repo — choosing engine and host-agent flavor — then the agent runs inside that repo and builds the actual game from a short engine guide.

Source layout

A published repo is intentionally thin: a runtime manifest, a one-page engine guide, and the asset-generation skill. The agent recreates everything else (project scaffold, capture tooling) from the guide.

- prompts/runtime.md — the runtime manifest
- asset-gen/ — the cross-engine asset-generation skill
- engines/godot.md, engines/godot-gdscript.md, engines/bevy.md, engines/babylon.md, engines/threejs.md — per-engine guides
- publish.sh — renders the runtime layout for the chosen engine and host agent

Engine and host agent (Claude vs Codex) are publish-time render choices, not separate source trees.

What the agent does

- Godot 4 — C# or statically typed GDScript projects with build-time scene generation, runtime scripts, and Jolt physics.
- Bevy — Rust/Bevy projects with code-first ECS scenes and offscreen capture.
- Babylon.js and three.js — TypeScript/Vite browser games served at a live URL.
- Asset generation — local and free by default with godogen_assets: images with real transparency, textured 3D models, rigged humanoids with generated moves and lip-sync, sound effects and voice lines. Paid APIs fill what it can't make: Gemini or xAI Grok images, animated sprites from Grok video, Tripo3D, Gemini TTS voice acting, Lyria music.
- Proof over claims — the agent judges results from the running game (a live URL or a recorded clip), not from a clean compile, so visible defects drive the next iteration.
- You choose your involvement — watch the live game (a Babylon.js or three.js URL, or a Godot/Bevy project you run) and steer at decision points, or leave the run unattended and get a 15–20s proof recording at the end. The agent takes its cue from how you frame the task.

Choosing an engine

Every engine gets the same loop — build, generate assets, run, prove — so pick by what you want to hold at the end and how you want to watch along the way.

| --engine | Language | You watch | Pick it for |
| godot | C# | the project, run or opened in the Godot editor | desktop 2D or 3D games; the fewest runtime surprises in long unattended runs |
| godot-gdscript | GDScript | the same | a Godot project you'll keep developing yourself in the editor |
| bevy | Rust | cargo run | a Rust codebase: ECS, no editor, many entities |
| babylon | TypeScript | a live URL | a browser game that leans on engine systems: physics, GUI, particles, animation |
| threejs | TypeScript | a live URL | a browser game that leans on its look: custom shaders, stylized rendering, a light page |

How you'll watch. O

……（后略，见原文）