[ how we build ]
A father, a son, and overcli.
We design the games together. overcli — the agent desktop app we also make — runs the long build sessions, and Unity’s own tests say whether they worked. Then we pick up a phone and play.
[ the loop ]
Spec, build, test, play.
The agent does the long, careful work. The parts only people can judge — how it feels in your hands — stay ours.
Every game starts as one document: its pillars, rules, tuning numbers and milestones. It’s the source of truth for us and for the agent.
An agent in overcli works through the milestones on its own, compiling in Unity’s batch mode and reading the log for errors as it goes.
A Build All menu runs every test. Bots fly every course and putt every hole; the screenshots are checked.
Tilt, touch, two phones on the Wi-Fi, how it feels — the parts no test can judge. That’s our job.
Each game copies what it needs from the last one — terrain, share codes, the Lab pattern — and never edits its siblings.
Every session ends with a build log: what was built, what passed, and what nobody has tried yet.
Built with overcli.
overcli puts Claude Code, Codex and the other agent CLIs in one window, then lets them work in long sessions, review each other and run in loops. It’s how these games get built — and it’s free and open source.