RESEARCH · 2026-09-21

IS HE THE FIRST?

Solo founder + multi-AI agent pit crew shipping a game and reality-show ops with a forever URL. Straight answer below — then case studies to steal polish from, and whether to pay testers.

No — José is not the first person to ship an indie game with AI coding agents as a “studio.” Solo + Claude/Cursor/Codex workflows, multi-agent game templates, and building-in-public AI ops all existed by 2024–2026.

What is rare is the combo: named agent lanes with inbox/🔥 claims, a forever public URL, War Room “reality show” ops, and a Godot mosh arcade under one founder. Closest analogues cover pieces of that stack — steal their process, not their product identity.

Case studies & videos

1. Agentic Game Development — Stellar Throne (Mr. Phil Games)

Solo · AI as junior collaborator · CLAUDE.md OS

Steal: Write the agent operating manual first (we already have AGENTS.md / GAME_BIBLE). Treat agents as desk neighbors with file ownership — not chat interns.

mrphilgames.com/newsletter/agentic-game-development

2. Epic Survivors — 14 months, up to 8 parallel agents

MonoGame survivors-like · Cursor + Claude Code + Codex · headless test flags

Steal: Data-driven content (YAML/JSON boards) so agents edit cards not engine guts; headless scenario flags for overnight cert — mirrors our wave_board + audit_crew_integrity.

web3dev1337.github.io/epic-survivors-architecture

3. Ashen Crown — almost-all-AI Godot experiment (Quah Jit)

Single giant GDScript · Claude conversation · code-drawn art

Steal: Founder drives taste; AI drafts. Their polish gap (meh audio/art) is the warning — pay humans for juice/readability when agents plateau.

quahjit.com/ashencrownproject

4. Solo GameMaker + Claude Code (makz)

Dev log · train the AI via spec notes after breaks

Steal: Every agent failure → one durable rule in the bible/inbox (same as our ALCOA+ / CF training reflex).

note.com/mono_games — Solo Game Dev Log Vol. 10

5. Tiny Studio / Game MCP — multi-agent “studio in a repo”

Templates · Lead/Engineer/Designer/Artist/QA roles

Steal: Explicit roles + bible-first — we already outgrew templates; use them as a mirror to prune redundant tools (#redundant? on /tools).

github.com/unveil-gg/tiny-studio · github.com/xthenyo/game-mcp

6. Multi-agent Claude Code tutorial (video)

Kieran Klaassen · ~40 min · parallel agents + CI

Steal: Founder spends attention on what’s next while agents run — our overnight HOT claimables pattern.

youtube.com/watch?v=Z_iWe6dyGzs

7. Juice it or lose it (video) — polish craft

Jonasson & Purho · classic juice talk

Steal: Maximum output for minimum input — hit-stop, shake, particles, sound layered on existing combat. Pair with POLISH_PLAYBOOK.md.

youtube.com/watch?v=Fy0aCDmgnxg

8. Creative control with AI (Atomic Object)

Prototype-driven vs spec-dump · keep founder taste

Steal: Play the build between prompts. Our Charter already says this — enforce it when polish feels “agent-shaped.”

spin.atomicobject.com/creative-control-game-developer

Should we pay testers?

YES — with tiers

Pay when you need strangers and structured evidence (first 60s confusion, telegraph fairness, mobile thumbs). Don’t pay friends to praise you. Don’t pay before you have one specific question.

Practical next step after Arcade Complete feel cert: Tier 1 round of 8–12 phone + desktop players on the forever URL, one survey (“When did you die / did you see the red flash?”), then one PlaytestCloud sample if patterns disagree.

Refs: PlaytestCloud Indie · Solo playtest guide · Closed alpha playbook

Also open