A gameplay change, kept inside a contract.
You ask for a bounded gameplay change and review an explicit contract. The change runs in an isolated Git worktree. A Unity compile and Play Mode tests produce the evidence. If a check fails, the change rolls back.
For solo developers and small teams who want an agent to touch their game without breaking it.
What you get
- A local control plane. A daemon on your machine that holds the contract, the worktree, and the evidence for each change.
- A CLI. Inspect, review, approve, apply, verify, and roll back from a terminal.
- A Unity Editor connector. Connects the Editor to the daemon for compile and Play Mode runs.
- A desktop app. Talks to the same local daemon. Shows the contract, the write set, the diff, and the results.
The reference project
The alpha ships with a reference project and one reference change:
Make a shotgun knock standard zombies backward within 3 meters, never bosses, and deal damage when they hit a wall.
This is the reference loop. It is not a promise about every sentence a user might type.
Limits
- Private alpha. macOS on Apple silicon. Certified Unity editor 6000.0.60f1.
- Windows, Linux, phones, consoles, and other Unity versions are outside the alpha.
- Live model calls are opt-in. The product works with the network off.
- A change on your own game requires your own Play Mode tests. The reference project is the path the alpha promises without that extra contract.