Alex Finn has one Grok Bot tell another to loop a task every five minutes
On 16 Aug 2026 Alex Finn (@AlexFinn) wrote that Grok Bot is built for loops: the main agent instructs another to loop a task every five minutes and monitor it. He said an orchestrator watched an engineer Bot for 24 hours and reflected every 30 minutes on one way to improve.
Based on a public example shared by @AlexFinn on X.
He contrasts this with a single Bot /loop watching itself. The extra Bot is a different context making the judgment. We summarize the public post — we did not re-run his 24-hour loop.
Why it's useful
If you want a job to keep going without you babysitting /loop, this is the two-Bot version.
Who should try it
Builders
Engineers
Researchers running long jobs
From the original post
“All you do is tell your main agent to tell another agent to loop on a task every 5 minutes, and monitor it while it goes”
Nate Herk published “A Week of Grok Bot Lessons in 10 Mins” on X: nine hacks for turning a default Bot into a team. Elon quote-tweeted it the same morning and asked people what Bots they run.
Blake accepted a public challenge, skipped OpenClaw, and in two nights: linked email, had a Bot build a 12-page household budget PowerPoint, stood up a team for his wife’s business, and started daily Tesla news recaps.
On 19 Aug 2026 Rahul (@sairahul1) published an X article: “How To Build a One-Person Company Using Grok Bot.” The open is the solo-founder load — find the leads, write the outreach, make the images, answer the replies, count the week — and a Bot system that takes those lanes.