Grok Bot engineer runs 200+ coding agents with five bots
A Grok Bot team member shared his setup: five domain-specific bots plus a manager bot that writes no code, with scheduled checks on PRs, CI, and P0 tasks.
A Grok Bot engineer just shared his personal Grok Bot setup. It runs 200+ coding agents at once Lingxi Li builds Grok Bot with Grok Bot. Here is how it works. The team: 5 bots, one per part of the product. iOS, desktop and CI, infra, Android, and the Grok Bot harness. A bot works best in its own domain, where its specs are sharp. The work: each bot turns a task into a Cursor cloud agent with a detailed prompt and the proof it expects back, like before and after screenshots. Then it watches the run and unblocks the agent when it gets stuck. The manager: Jenny writes no code. Every day at 5:00 it holds a 1:1 with each bot. After any mistake it runs a postmortem and updates the playbook for everyone. The clock: > every 30 min: every PR checked for Bugbot findings, failing CI, conflicts > 3:00: audits for dead code, load time, bundle size > every 5 min: P0 tasks only The merge rule: high confidence and low blast radius merges itself. Everything else goes to a human. The clock is where most setups go wrong. The article below covers it.
This post quotes another post: x.com/gippp69/status/2109235458383216811