Grok Bot teams can loop all night; a 43-line script caps it
The author warns Grok Bot writer-reviewer chains can ping-pong until morning with no output, and shares a 43-line script with handoff caps and stall detection plus a multi-bot speedup estimate.
This is f*cking scary: Grok Bot teams can argue with each other until morning, and nothing in the docs I read stops them Picture it. One report requested, then sleep. The writer sends a draft. The reviewer wants a change. The writer fixes a comma. The reviewer wants another. Two hundred messages by morning. Zero reports. No cap on handoffs. No cap on turns. Nobody awake. The popular setup builds this loop by design: chief of staff, researcher, writer, reviewer. Every arrow is a wait. Six bots in a chain run exactly as fast as one. What I built against it: the math: 6 bots with 70% independent work give 2.4x, not 6x a reviewer that sees the artifact and the source, never the thread, so it can’t inherit the writer’s blind spots a script that kills runaway chains: handoff cap, stalled rounds, ping-pong. On my test log it flagged 3 of 6 tasks, and a task that finished still took 7 handoffs The script takes 43 lines. The 3 a.m. loop takes none.
This post quotes another post: x.com/rvaniaaaa/status/2112997845854797838