Grok Bot has no spend cap. Build one.
There's no Bot-level spending limit in Grok Bot. Here's the ceiling we install on every account: allowance tracking, a 60/85% alert routine, on-demand rules, and a kill procedure.
The situation
Eligible plans include a weekly Grok Bot allowance (size unpublished). Beyond it, usage bills on-demand by model and token. There is no per-Bot or per-product ceiling; account-level on-demand settings are the only brake. An early HN user reported using more tokens in one month of always-on Bots than in the previous five years combined. That's not a bug in his setup. That's what always-on means.
The ceiling we install
1. On-demand rule. In the Cursor dashboard, set on-demand usage to a fixed monthly amount you can afford to lose, or off entirely for the first two weeks. The app can disagree with the dashboard about usage; the dashboard bills, so it wins.
2. A watcher routine. One Bot, one routine, runs daily: open the usage page, record the allowance percentage and on-demand spend in a log file, and message you (Slack or email) when either crosses 60% and again at 85%. It's a Bot watching the meter. Cost of the watcher itself: negligible.
3. Frequency discipline. The most common cause of runaway spend is a routine scheduled hourly that should run daily, or a Bot told to "keep checking". Every routine gets an explicit cadence and a stop condition. See runaway routine.
4. Kill procedure. Written down, one page: how to pause every routine, how to pause each Bot, how to revoke the Bot accounts' tokens. Practised once so it takes under a minute.
What a normal month looks like
A five-Bot small-team setup with daily routines and no "always be checking" instructions typically stays inside the weekly allowance on the mid-tier plans. The spend problems we see are almost always one routine, not the whole fleet.
Runaway routine · Usage meter mismatch · Grok Bot pricing explained
Verified 28 Aug 2026 · Facts about Grok Bot change during beta. See changelog.