Grok Bot routines: how 5-minute schedules burn your weekly quota
The post calculates that seven bots on a 5-minute routine run 14,112 times a week and drain the weekly pool, so it recommends scheduling jobs instead of clocks, with per-use frequencies and a guard prompt.
elon told 39 million people Grok Bot is a chief of staff. most of them will run it like a smoke alarm 7 bots on a 5-minute routine = 7 × 288 × 7 = 14,112 runs a week. if 30 find something real, the other 14,082 just woke up to look around the math on one routine: → every 5 min = 288 runs a day → hourly = 24 → once a day = 1 → every run burns your weekly usage pool. even the test button 5-min vs hourly is 12x the usage for the exact same job. one busy routine can eat a week's pool in a day the fix: schedule the job, not the clock → morning brief: once, 07:00 → call prep: once at 07:00, preps every call on today's calendar → invoices: once, on the 1st → renewals: once, every friday → inbox: hourly, work hours only. the only bot that earns it → ~100 runs a week instead of 14,112 where it breaks: → a meeting moves after 07:00 and the prep is stale. add one rerun at 13:00, not 288 → 40 emails land at once. batch them into the hourly run, never one run per email the rule to put in every bot's description: ------ Before any work, check what changed since your last run. If nothing changed, say nothing and stop. Never send, pay or sign without my approval. One job only. ------ save this before you give your next bot a schedule ↓
This post quotes another post: x.com/fluixoo/status/2114049849620332666