Agent Atlas

The Builders

Antti Kananen

Writes Games Alchemy and builds games by directing agents through a pipeline he keeps in a handbook.

Pick the stack, write the smallest docs, prove the risky part, and do not let an agent expand the wrong spec.

Steal this

  • Agents are good at expanding the wrong specification. Prove the risky part before you scale.
  • A new engine, service or dependency has to be proposed, researched and approved.
  • Play, say what is wrong, let the agent patch, play again.

The lesson and the takeaways are our summary. Everything below is theirs, with where they said it.

The setup

Factual
Machines

Not named.

Software

Unreal Engine 5.8 with Claude or Codex leading. Earlier, Codex owned the project and Claude worked in a separate Blender lane.

Models

Claude Opus 5.5, Claude Sonnet 5.5 and Astra, for different jobs.

As of October 12, 2026. Setups change; follow the links.

How they work

Factual
  1. On 24 Aug 2026 his handbook picks the platform, then the smallest design docs, then a proof of the risky parts. (Antti Kananen)
  2. His role is a set of directors, product, creative, design, technical and art. A new dependency needs his approval. (Antti Kananen)
  3. Codex keeps the project. Claude works in a separate Blender lane and cannot overwrite the runtime model. Codex reviews before anything enters the game. (Antti Kananen)
  4. He says the tools do not give taste, spatial consistency or production-ready topology. (Antti Kananen)
  5. On 2 Sep 2026 a tank looks finished until the turret has to turn, and a character rigs until the hand has to hold a weapon. (Antti Kananen)
  6. On 1 Oct 2026 the loop is play, say what is wrong, let the agent patch, and play again. (Antti Kananen)
  7. On 12 Oct 2026 he directs agents inside Unreal Engine 5.8. Claude or Codex leads, whichever still has usage. (Antti Kananen)