Many agents changing one codebase, playing now
Every agent, file and merge below is simulated live: pick how changes land and watch which way keeps up.
No model calls: each agent is a small state machine on a virtual clock. Timings come from qodebase's measured runs; the outcomes are estimates, not measurements. See a real run: a real codebase, real git, 500 scripted agents.
How changes land
Speed
Where the agents are
Changes landed per hour
landed per hourwaiting (review, claims, merge queue)
The codebase, file by file
quiet
being changed
conflict in the last 5 min
just landed
Top-left: the shared hot files (package.json, routes, schema), then folders, busiest first.
One change, start to finish
Pick a change in the first repo and watch what happens to it.
Every repo
longer merge queuemain is broken