Guide

Grok Bot usage limits and cost: Weekly usage explained

By Atlas AI Resources · Published October 8, 2026 · How we make these guides

How much does Grok Bot cost? There’s no separate Grok Bot subscription. Access is included with every paid individual Cursor plan and with Cursor Teams, or comes from linking an individual SuperGrok, SuperGrok Plus, SuperGrok Heavy, or X Premium+ subscription (or from a seat on a self-serve Grok Business plan). Paid access includes Weekly usage that resets weekly. Once that runs out, Grok Bot keeps going only on On-demand usage, and only if on-demand is enabled (on Cursor Teams it’s on by default).

This guide explains how those pieces fit together, what uses them up, and how to keep a team of Bots affordable. Apart from one clearly labeled community reply, everything here comes from Cursor’s help pages, the SpaceXSI docs, the Grok Bot changelog, and the official Grok Bot Guides. It gives no prices or usage amounts, because the official pages describe the tiers in relative terms and prices change. For current prices, see Cursor pricing and x.ai pricing.

1. Is Grok Bot free, and which plans include it?

Do you need a separate Grok Bot subscription? No. Ongoing access needs an eligible plan, and Cursor’s Plans and billing page lists the plans that qualify. It describes each tier’s Grok Bot usage in relative words, not numbers:

Cursor plans

Cursor Ultra: “Highest weekly usage”
Cursor Pro+: “Generous weekly usage, below Ultra”
Cursor Pro: “Weekly usage, below Pro+”
Cursor Teams (self-serve): “Follows the Teams plan allowance”
Cursor Enterprise: “Managed by your admin”

Linked Grok and X subscriptions

Individual SuperGrok Heavy: “Highest linked usage”
Individual SuperGrok Plus: “Generous linked usage, below Heavy”
Individual SuperGrok: “Linked usage, below Plus”
X Premium+: “Linked usage, below SuperGrok Plus”
A seat on a self-serve Grok Business plan: “Matches the license on your seat: SuperGrok or SuperGrok Heavy”
Grok Enterprise: “Managed by your account manager”
SuperGrok Lite: Grok Bot is not included.

The SpaceXSI docs FAQ and overview currently list only the SuperGrok tiers. Cursor’s page, which the SpaceXSI Teams doc calls “the canonical plan and usage matrix,” also includes X Premium+ and Grok Business seats, so this guide follows it.

Is there a free trial?

Yes. The Grok Bot trial is “a usage credit rather than a set number of days, though a 7-day window also applies.” The credit is “drawn down by how much work your agents do, measured by agent steps and tokens rather than the number of messages you send.” A large or long-running task can use most or all of it in one run, and used trial credit “is not restored or topped up.”

The trial never becomes a paid plan. On free-plan accounts, Cancel Trial on the plan screen ends it right away and removes any remaining trial credit, and you can’t claim the trial again.

One thing to watch: an App Store intro offer started in the iOS app is not the Grok Bot trial. Apple runs it, and it “turns into a paid Apple subscription when the trial ends unless you cancel first.” Cancel it in Apple ID > Subscriptions. Android has no in-app trial.

Does my SuperGrok plan cover it?

Yes, for individual SuperGrok, SuperGrok Plus, and SuperGrok Heavy, and for X Premium+, once you link that account from the Grok Bot plan screen. SuperGrok Lite doesn’t include Grok Bot. A link is “a usage grant, not a Cursor plan,” and it is permanent: you can’t unlink it or move it to a different Cursor account, so sign in with the right Cursor account before you link. If you hold a seat on a self-serve Grok Business plan, you don’t link anything; sign out of Grok Bot and sign back in with Sign in with Grok. Request-based Teams plans and Enterprise seats don’t take a personal SuperGrok link.

2. How Grok Bot usage works: Weekly usage, On-demand usage, and the monthly limit

How does Grok Bot usage work? Grok Bot draws from Weekly usage first, an included grant that resets weekly. When it runs out, Grok Bot can continue on On-demand usage if on-demand is enabled, and that extra usage counts toward the On-demand monthly limit.

Weekly usage is your included usage. It resets weekly. If the meter carries a SuperGrok tier name, that is the linked grant, not a second Cursor plan.
On-demand usage is extra usage after Weekly usage runs out. The row says Billed through Cursor. The SpaceXSI FAQ says it is “billed from model and token cost.”
On-demand monthly limit is the cap on that extra usage. On the web, the same cap is Spending > Monthly Limit on the Cursor dashboard.

Cursor puts it plainly: “Included weekly usage is not the monthly limit.” Grok Bot usage is metered on your Cursor account, not on Grok or X.

On an individual plan, the Grok Bot changelog says you can set your monthly on-demand limit to None, Fixed, or Unlimited in Usage & Billing. On the Cursor Teams plan, on-demand usage is enabled by default. To turn it on yourself, open Settings in Grok Bot, find On-demand monthly limit, and choose Enable. If Grok Bot asks for a card, finish on the web under Spending > Monthly Limit. If you subscribed in the iOS or Android app, set the limit on the web.

What happens when Grok Bot usage runs out?

With on-demand off: Grok Bot stops when Weekly usage runs out. The screen says you have reached your Grok Bot usage limit, and it resets with weekly usage.
With on-demand on: work continues until the On-demand monthly limit. “A limit is not a hard stop in the middle of a run. A bot already working can finish past the monthly limit.” After that, on-demand stops until you raise the limit or the billing cycle resets.
Routines: if a routine didn’t run, the troubleshooting doc lists “Usage or account access has not been paused” among the checks.

When does Grok Bot usage reset?

The official pages say only that Weekly usage “resets weekly.” They don’t give a day or a time. Since the September 29 release, Settings > Usage & Billing “shows your included usage and when it resets,” so check there for your own account.

Is usage shared between my devices?

Yes. Cursor says “macOS and iOS share a single usage bucket tied to your signed-in Cursor account.” Usage belongs to the Cursor account, not to a device.

Can I set a spend cap just for Grok Bot?

Not today. The SpaceXSI Teams doc says “A separate Grok Bot spend cap is not available today.” Account-level on-demand controls apply, and the per-product split is on the dashboard usage page.

Is this the same as Grok app usage?

No. Grok Bot usage is metered on your Cursor account, not on Grok or X, and extra Grok Bot usage comes from On-demand usage billed through Cursor. The SpaceXSI FAQ for the Grok website and apps covers a different product, and it says Grok Bot “is not the same as Grok on grok.com or the Grok mobile apps.” The official Grok Bot pages don’t mention the Grok app’s top-up options, so use only the Grok Bot labels above.

3. Do Cursor and SuperGrok plans stack? How to get more usage

How do you get more Grok Bot usage? Turn on On-demand usage, or move up within Cursor plans: “Moving from Pro+ to Ultra raises included Grok Bot usage to the Ultra tier.” Adding a SuperGrok or X Premium+ link on top of a Cursor plan is not a way to get more.

That’s because “A Cursor plan and a SuperGrok or X Premium+ link do not stack.” Only one grant applies at a time. Cursor’s own examples:

“If you are on Pro+, linking SuperGrok Plus does not add Grok Bot usage.”
“If you already have SuperGrok Heavy linked, purchasing Cursor Ultra does not add Grok Bot usage.”

Both subscriptions can stay active and keep billing on their own; buying one doesn’t cancel the other. The SpaceXSI FAQ says the same thing in different words: if you have both, “Grok Bot uses whichever has more usage.” On mobile, sign in with the same Cursor account, since usage is tied to it.

Changed your SuperGrok tier after linking? Allow up to 24 hours for Weekly usage to move to the new tier. You don’t need to link again, and you can’t unlink to force a refresh. If the old tier still shows after that, contact Cursor support.

On refunds, Cursor lists on-demand usage Grok Bot has already consumed, and mid-cycle downgrades with usage, as not refundable. Purchases made in the App Store or Google Play are refunded through Apple or Google Play, and SuperGrok and X Premium+ are billed by SpaceXSI or X, not Cursor.

4. Where to see your Grok Bot usage

In the desktop app: Settings > Usage & Billing shows weekly included usage and on-demand usage for eligible accounts, and the account menu can show Weekly usage at a glance. Cursor’s help pages also mention a “plan screen” for checking usage and for Cancel Trial, which the changelog places in Usage & Billing. The On-demand monthly limit is in Settings too.
On iPhone and Android: Settings lets you review usage or manage an eligible App Store or Google Play subscription.
On the web: the Cursor dashboard’s Spending > Monthly Limit holds the on-demand cap, and the dashboard usage page shows the per-product split.
If neither app surface appears: review usage from the Cursor account page or contact your organization’s admin.

The changelog shows what the app tells you as you get close:

The chat warns you near your weekly limit.
When a Bot can’t reply because of a usage limit, rate limit, or timeout, the chat shows a card that says why.
Hitting a usage or spend limit shows the full limit banner, with buttons like Upgrade, Set Spend Limit, or Request Upgrade (to ask your admins).
When you use up your plan’s included usage, Grok Bot shows the usage limit notice instead of “Bot failed to respond.”
A notice tells you when routines were paused while you were away.

5. What uses up Grok Bot usage

Why is Grok Bot usage running out so fast? The official measure is work, not messages. Cursor says the trial credit is drawn down by “agent steps and tokens rather than the number of messages you send,” and that “Larger or longer agent jobs use more.” That wording is written about the trial, but it is the clearest official description of how Grok Bot work is measured. So the answer to “how much does it cost to run an AI agent?” is that it depends on how much work the agent does, not on how often you talk to it. The official docs and guides point to these drivers:

Broad event listeners. The docs warn against listeners such as “every new message”: “They create noise, consume usage, and increase the chance of acting on irrelevant input.” Use a narrow matching rule instead.
Very frequent routines. The Grok Bot for Engineering guide’s author describes a temporary P0 routine that checks a cloud agent’s transcript every five minutes and warns that it “can burn tokens much faster than you think, so only use it for true urgency.” For reference, routine schedules must be at least five minutes apart, and a Bot can own up to 50 routines.
Unattended routines. “To control unattended usage, Grok Bot may ask whether to keep routines running after a long period away and pause them if there is no response.” Review paused routines when you return.
Tagging @bot on X. X tells you the first time that “tagged requests start work automatically and use your Grok Bot usage.” One common reason @bot stays quiet is that your weekly usage is used up.
Team Bots. When a teammate talks to a Team Bot, “the usage counts against that teammate’s own Grok Bot allowance, not the owner’s.” A routine counts against whoever set it up, and Slack messages that don’t come from a linked teammate, such as posts from a Slack workflow, count against the owner. If a teammate is out of usage, the Bot tells them instead of using the owner’s.

What one Cursor staff reply added (community information, not official docs)

In a September 2026 Cursor forum Help thread, a small team running a Grok Bot fleet asked whether a week of extra usage was expected. A Cursor staff member replied that they saw nothing wrong or anomalous in the account and explained that “Every turn re-reads that bot’s whole conversation,” so a Bot that has been in one chat all week “pays for its full history on every reply, even for a one-line handoff.” The reply also said that, in that account, about a third of all turns were Bots waking other Bots, and that each routine run has a cost. This is one staff reply about one account on a community forum. It isn’t in the official docs, so treat it as context rather than documented behavior.

6. How to keep a multi-bot setup affordable

None of these tips means giving up the team model. The aim is fewer, more purposeful runs and messages, not fewer teammates. No tip here comes with a promised saving.

Decide on on-demand before anything runs unattended. Leave it off if you want Grok Bot to stop when Weekly usage runs out, or set an On-demand monthly limit you’re comfortable with, remembering that a run already in progress can finish past it. On Teams it’s on by default, so check with your admin.
Start small and check usage before big jobs. Cursor’s advice for the trial is to “Start small and scope tasks tightly” and to check your usage on the plan screen before large or long agent jobs. It’s sound general advice after the trial too.
Prove a job by hand before you schedule it. Do it once in chat, save it as a skill, then make it a routine. See Skills before routines. A Test run “performs real work,” so use safe inputs.
Schedule less often and keep triggers narrow. Fewer, sparser routines that stay quiet when nothing is new, and narrow matching rules instead of broad listeners. The “Keep token and usage cost down” section of Scheduling AI agent routines covers the patterns. For a summary of how the official support guide turns support jobs into routines, see Grok Bot for support.
Give each Bot one job. The guides find that focused Bots stay sharper than a catch-all chat. See What is a one-job Grok Bot?
Make handoffs quieter. The docs advise: “Ask for a single owner at each stage. Too many parallel handoffs can create duplicate work and noisy updates.” The Grok Bot for PMs guide notes that agents “bias to action but can also over-communicate” and suggests asking them to stay quiet unless something needs your attention. The forum staff reply suggested a profile line like “Only message another bot when it needs to act. No acknowledgments, thanks, or progress pings. Send one summary when the work is done.” For rosters and group chats, see Small AI fleets: handoffs.
Keep your coordinator if it helps. The guides recommend a single front door once handoffs are real: “Add Project Manager after the handoffs hurt, not before.” A coordinator that keeps messages few and purposeful fits this advice.
Consider a fresh chat per task. The same staff reply suggested a new chat for each bug or feature, with standing instructions in the Bot’s profile and task state in a shared board such as Notion. The official docs don’t say a new chat reduces usage, but they do suggest starting a thread or a new Bot when a conversation has changed to a different long-lived job.
Audit your routines now and then. In the Grok Bot for Post-Sales guide, a chief-of-staff Bot checks which routines fired and got ignored and proposes fixes for a yes or no. The Grok Bot for GTM guide suggests asking it to clean up unnecessary routines. The Teams doc also recommends reviewing active routines regularly and pausing a routine when its source system changes.
Judge cost per finished job. As general advice rather than a Grok Bot feature, compare usage with the finished work you actually used, not with the number of messages.