Change control for Unity games.
Let an agent change your game. Then see the proof it still plays.
Every change gets a contract, runs in an isolated worktree, and is checked in Play Mode before it lands. If a check fails, it rolls back.
inspect reference project ok contract knockback rules approved write set 3 files approved worktree isolated created compile Unity passed play mode knockback tests passed main tree untouched ∎
How it works
- Inspect the project.
- Review the contract.
- Approve the write set.
- Apply the change in a worktree.
- Verify with compile and Play Mode.
- Roll back if it fails.
Where other tools stop
Oqedra does not replace your engine, your IDE, your model, or your art pipeline. It makes them work together and checks the result.
| Tool | Stops at | Oqedra |
|---|---|---|
| AI coding tools | It compiles. | It plays. |
| Version control | It stored the change. | It proved the change. |
Speed comes from safety.
You can move quickly because every change can be checked and rolled back.
- Local by default. Everything runs on your machine. Live model calls are off unless you turn them on.
- Your main tree is never the edit target. Changes land in an isolated Git worktree. The engine project stays the source of truth.
- Proof, not vibes. A change is checked with a Unity compile and Play Mode tests. If a check fails, it rolls back.