Grok Bot rebuilds a shop backend from one app.js with 100 subagents
The author says Grok Bot split 100 small agents into readers, writers, testers and checkers to rebuild a shop backend from a single app.js, passing 360 tests while every edit waits for user approval.
Wait... Grok Bot rebuilt a shop's backend from a single app.js, passed 360 tests, and still asks for your yes before anything changes??? It didn't use one giant bot. It used 100 small ones in 4 narrow roles The work split like this: 1/ 20 readers list every request the app sends or expects back 2/ 50 writers build the API backwards from those requests 3/ 20 testers run the app against the new API 4/ 10 checkers don't count anything as done until it matches the app On top sits one lead Grok that hands out the work and asks checker-07 to confirm every match The trick isn't more agents. It's that what it can't read gets switched off instead of guessed and every edit waits for you You can run the same setup on Grok Bot with one small app. Start with the readers, the full setup prompt is in the replies ↓
This post quotes another post: x.com/kv1nsiii/status/2113703026120884264