How the meter actually works

Every eligible plan includes Grok Bot usage that resets weekly, in a bucket separate from Grok chat and Cursor editor usage. If you hold both a Cursor and a SuperGrok subscription, the FAQ says Grok Bot draws from whichever has more usage. Consumption is measured by agent steps and tokens, not messages: a Bot that spends twenty minutes scrolling a website costs far more than twenty short chat replies.

When the allowance runs out, work continues on on-demand billing derived from model and token cost, provided on-demand is enabled on the account. There is no Grok Bot-specific cap, and a forum thread reports no warning before the switch. The usage banner can be dismissed but returns, which one thread asks to fix.

Documentation: Billing and access FAQ ↗ Cursor Grok Bot docs ↗ Forum: no warning before weekly usage spills into on-demand ↗

What burns it fastest

Community reports point at the same culprits: many Bots running in parallel, long unattended browser sessions, routines that run whether or not there is new data, and Bots retrying a stuck page. One user described 42 percent of a weekly allowance gone on day one across six Bots; another put five percent on a hundred small completions plus a ten-minute script. A forum thread on the API path reports costs far above expectation.

There is no model picker, so you cannot route small jobs to a cheaper model. The levers you do have are fewer Bots, shorter tasks, and routines that stop early when nothing changed.

Documentation: CellCog problems tracker ↗ Forum: very high costs on the API ↗

The setting that protects you

Because the product has no cap of its own, the account-level on-demand control in Cursor is the only hard stop. Decide deliberately whether on-demand is enabled, and if it is, set the limit before the first routine runs unattended.

Documentation: Billing and access FAQ ↗ Cursor Grok Bot docs ↗

  1. Open your Cursor account billing settings and find on-demand usage.
  2. Either disable it, accepting that Bots stop when the allowance ends, or set a monthly limit you can afford.
  3. In the Grok Bot app, open usage and note today's level and the day it moves back up; that is your reset day.
  4. Run one Bot on one bounded task and reread usage to learn what a single run costs.
  5. Add routines last, with a no-change early exit, and check usage after their first unattended week.
  • On-demand is deliberately on with a limit, or deliberately off.
  • You know your reset day.
  • Every routine has a stop-if-nothing-changed instruction.
  • You are running the fewest Bots that get the job done.

Quick answers

Is there a Grok Bot spending cap?

No Grok Bot-specific cap exists as of September 17, 2026. When the weekly allowance is used up, usage continues on the account's shared on-demand spend if on-demand is enabled. The only protection is the account-level on-demand setting and limit in Cursor.

How big is the weekly allowance?

Unpublished. The docs describe it only relatively: Pro below Pro+ below Ultra, with SuperGrok tiers following the same pattern. Forum users report a full week consumed in one day by a six-Bot setup, and around five percent consumed by about a hundred short completions plus one ten-minute script.

When does the allowance reset?

Weekly. The usage screen in the app shows the current level; several users ask for a visible reset date and a warning threshold, neither of which exists yet. Note your own reset day the first time you see the meter move.

Sources & next steps

Capabilities are grounded in the documentation below. The workflow design and acceptance checks are editorial suggestions.

Build your own workflow brief ↗