Build a commercial Godot colony game by directing agents through Linear tickets

A former tech architect who had never used Godot or GDScript spent 18 months directing 5 to 15 Claude and Codex agents to build a cozy colony sim, now with a Steam demo.

Done withClaude CodeCodexCursorinLinear· Nov 13, 2026

What they did

The poster, Nick, a former web developer and tech architect, quit corporate work to make an indie game called Luminids without writing code himself. He runs Claude (mostly Opus 5.5 on high effort) and Codex through Cursor, often 5 to 15 agents at once. The agents are wired to Linear by API and CLI, and every piece of work goes through a ticket with milestones and acceptance criteria. A custom MCP bridge and Godot's headless CLI let agents build and test the game, Blender is driven over its MCP server, and an art tool is linked the same way. Agents take roles such as developer, game designer, QA, adversarial tester, blind reviewer and researcher, and some play the game in windowed mode to check visuals. He describes himself as the director, spending 60 to 70 hours a week planning and redirecting them.

How it went

After 18 months the game, a colony sim with creatures that keep memory, relationships and beliefs (no LLM runs in the game), has a playable Steam demo and is heading for early access. He says the agents produced over 60 creature animations in Blender in about two days, work a freelancer had quoted at thousands of pounds and three months. His heaviest months cost about £2,000 to £3,000. Video generation never worked for him despite over $500 spent, so cut scenes are stills with text, and 3D generators made models too heavy to use.

Worth knowing

He credits the ticket system, not markdown files, with keeping agents on track, and says left unsupervised they drift and add bugs and performance problems. Character designs came from a hired 3D artist and the music from a composer. Commenters pointed out that the Steam AI disclosure only mentions selected code, which they said does not match the claim of no hand-written code.

Try it

With Claude Code· 3 parts to fill in

You are the lead agent on my [engine, e.g. Godot] game in [project folder]. Work only from tickets in [Linear or my ticket tool]: before coding, read the ticket, its acceptance criteria and the design docs it links. Split the work into tasks for helper agents (developer, QA tester, reviewer) and coordinate them. Run the game headless to run the unit and smoke tests, and capture screenshots for any visual change. Do not add features or systems that are not in a ticket, and flag anything that could hurt performance. When the acceptance criteria pass, post a summary and the screenshots on the ticket and stop for my review before starting the next one.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related