Cut Grok Bot weekly usage when the meter climbs fast

After this page you can open the weekly meter, pause the work that drains it, and set a monthly on-demand cap. There is still no estimate before a task starts, and no view that splits usage by Bot.

On legacy Cursor plans and SuperGrok or X Premium+ links, paid Grok Bot access includes Weekly usage. That included grant resets weekly. When it runs out, extra Grok Bot usage can continue as On-demand usage if on-demand is enabled. Grok Bot usage is metered on your Cursor account, not on Grok or X. The same meter is shared by macOS and iOS. On The X Subscription, Grok Bot is included on Premium, Super, and Ultra (not Plus or Free). It draws from one weekly pool shared with Grok and Cursor. When the pool runs out, extra usage is paid from prepaid credit (top-ups), with a monthly additional-usage limit at grok.com/dashboard/billing. Check usage under Usage at grok.com/dashboard. Official pages: Plans and billing, Routines, and Models. More Grok Bot jobs live on the Grok Bot hub under Usage, plans and billing. For which X Subscription tiers include the Bot, see Is Grok Bot included in each X Subscription tier?.

Check the meter first

Usage is measured by agent steps and tokens rather than the number of messages you send. Larger or longer agent jobs use more. Cursor help says to start small, scope tasks tightly, and check your usage on the plan screen before running large or long agent jobs.

1. Open Grok Bot.
2. Open Settings > Usage & Billing.
3. Read the included weekly usage and when it resets.
4. Note whether on-demand is enabled and what monthly limit you set.

Grok Bot usage is seen in Grok Bot under Settings > Usage & Billing, not in the Grok app. When you use up your plan's included usage, Grok Bot shows the usage limit notice instead of Bot failed to respond, and that same Settings page shows your included usage and when it resets. On The X Subscription, check Usage at grok.com/dashboard.

Cursor staff (Colin) said on the forum (Oct 5, 2026) that today the Usage section in Grok Bot's Settings shows your weekly usage for the whole account, not split by Bot. A per-Bot breakdown is something the team is working on. There is no per-chat, per-routine, or per-model usage view in Grok Bot either. The Cursor dashboard export at cursor.com/dashboard → Usage → Export CSV can include Cloud Agent ID and Automation ID columns for Cursor Cloud Agents. That export is not a per-Bot Grok Bot breakdown.

Cut the work that spends the week

Each routine run spends usage. An hourly schedule, a short interval, or a Slack trigger on a busy channel can use a week of usage in a day.

1. Pause routines you do not need. A routine that never runs does not spend usage. Test does.
2. Ask the Bot to widen schedules and narrow Slack triggers before you raise a plan or an on-demand limit.
3. Scope the next chat tightly. Prefer one finish line over an open-ended “keep watching” job.
4. Avoid long, unattended monitoring sessions. Official help does not publish a per-minute rate for computer use, so treat those jobs as large until you check the meter again.

A Cursor plan and a SuperGrok or X Premium+ link don't add together; Grok Bot uses whichever grants more weekly usage. On The X Subscription there's nothing to link.

There is no preflight cost

No official page describes a usage estimate or a confirm step before a task. A Bot cannot show you what the next job will cost, and there is no approval card for spend. The documented controls are the ones above: read Usage & Billing, start small, pause unused routines, and set the On-demand monthly limit (legacy plans; on The X Subscription it's the monthly additional-usage limit under Additional usage credits) on the plans page if you want a cap after the week runs out.

When the week is already gone, see Control Grok Bot On-Demand after weekly usage hits 100%. For Ultra and Heavy pacing, see Pace Grok Bot weekly allowance on Ultra (and Heavy). If specialist Bots keep reviewing each other, see Stop multi-Bot review loops from burning your weekly Grok Bot usage.

Pitfalls

• Looking for Grok Bot usage in the Grok app. It is not there.
• Expecting the Settings meter to name which Bot, chat, routine, or model spent the week. It does not, as of Oct 5, 2026.
• Leaving Test on a routine you already paused. A test run still spends usage.
• Treating SuperGrok plus a Cursor plan as two weekly grants. They do not stack. On The X Subscription there's nothing to link.
• Treating the On-demand monthly limit as the extra-usage cap on The X Subscription. On that plan it's the monthly additional-usage limit under Additional usage credits.