#agent-workflow
4 items (2 guides · 2 fixes)
The architecture for letting an agent (or CI) drive the live s&box editor: compile-gate, spawn, play, inject input, read telemetry, screenshot, assert, and gate a merge on the numbers — with no human at the keyboard.
The build order for a fresh s&box project a coding agent can actually work in without corrupting itself on day one — skeleton, globals, compile gate, and the ownership discipline that keeps parallel agents from clobbering each other.
Disjoint file ownership, serialize hot files, report-don't-fix foreign errors, resume after interrupts — the concurrency rules that keep agent waves shippable.
Top model plans and reviews; cheaper agents execute on disjoint files; telemetry-driven feel tuning — whitelist and stale-assembly traps included.