Grok Bot users hit their weekly limit early on November 1. What Musk said, what to do

What happened on November 1

Shortly after midnight Eastern time on Sunday, November 1, Grok Bot users began reporting that their weekly usage had jumped to 100%, days before it was due to reset. A bug report on Cursor’s forum, opened that night by a Cursor Ultra subscriber, says the meter “keeps flipping in real time: 74%, then 77%, then 100% (capped), back to 77%, back to 100%,” starting “around 12:18 AM ET on Nov 1,” with “no real spike in usage.” By early on November 2 the thread had more than 100 posts. Others in it describe going from “45% to 99% overnight,” and, on a legacy Pro+ plan, a dashboard that “suddenly showed over 90%, then immediately jumped to 100%.”

At 20:11 UTC that day, an X user who posts as Doge Norway asked Elon Musk: “Any chance for a Grok Bot reset, @elonmusk? Lots of people say their usage ran out really fast this week.” Twenty-three minutes later, Musk replied: “The cost of serving Grok Bot was unsustainably high relative to revenue.”

That reply is the only explanation anyone at SpaceXSI, the company behind Grok, has given. Anadolu Agency, reporting it on November 2, notes that he gave no figures for costs or revenue and didn’t say whether the limits would change or be reset.

What SpaceXSI and Cursor have said, and haven’t

Grok Bot is SpaceXSI’s agent that works on its own cloud computer, and it “signs in with your Cursor account,” its FAQ says. As of early on November 2:

• No announcement. SpaceXSI’s news page has nothing on Grok Bot’s limits; its latest Grok Bot post is from October 27.
• No incident. Grok Bot’s status page reads “Operational” and lists nothing for November 1 or 2. Its last incident, “Multiple services degraded,” lasted 44 minutes on October 31.
• No staff reply in the forum’s bug thread. On November 1, in another thread, a Cursor staff member explained the meter: “usage is counted based on the work the bot does, like tools, subagents, and browser use, not by the number of messages. Also, on every turn, the bot rereads the full chat history.”

Neither company has said whether the allowances changed or the rate Grok Bot draws from them did, and if so when; whether the jumps to 100% are real usage or a fault in the meter, as several users believe; or whether anyone will get a reset or their on-demand charges back. They have never published how big any plan’s weekly allowance is.

How Grok Bot’s weekly usage works

Here is where Grok Bot’s usage comes from, plan by plan, from Grok’s pricing and Cursor’s plans page on November 2:

Plan	Price a month	Grok Bot	Its weekly usage	When that runs out
X Subscription Plus	$8	No	Not included	Not included
X Subscription Premium	$30	Yes	Shared pool, 4 times Plus’s	Prepaid credit, if you buy it
X Subscription Super	$100	Yes	Shared pool, 15 times Plus’s	Prepaid credit
X Subscription Ultra	$200	Yes	Shared pool, 50 times Plus’s	Prepaid credit
Legacy Cursor Pro, Pro+, Ultra	$20, $60, $200	Yes	Its own weekly limit	On-demand usage, if it’s on

Yearly, Premium is $300, Super $1,000 and Ultra $2,000. On The X Subscription, which SpaceXSI introduced on October 12, and where new customers start, Grok Bot “draws from the same weekly usage pool as Cursor and the Grok apps, and prepaid credit covers usage past the pool.” The usage limits page adds that “Usage rates vary by product, so different activities can draw different amounts from the pool.”

On a legacy Cursor plan, which keeps working for those already on one, Pro includes “weekly usage,” Pro+ “generous weekly usage” and Ultra “the highest weekly usage,” and Grok Bot’s usage “is metered on your Cursor account, not on Grok or X.” A linked SuperGrok or X Premium+ subscription doesn’t add to a Cursor plan: “Grok Bot uses whichever one grants more weekly usage.”

You can’t choose a cheaper model to stretch it. “Grok Bot picks the model for each task, and there is no model picker,” and “Routing a task to Opus 5.5 doesn’t change what it costs you per token.” When the week’s usage is gone and extra usage is off, “Grok Bot stops when weekly usage runs out and resumes when weekly usage resets.”

Who it affects

Everyone who uses Grok Bot, which, on SpaceX’s October 20 earnings call, Gwynne Shotwell said “already had paid weekly users of 800,000 earlier this month,” as FourWeekMBA quotes her. It hurts most where Bots run routines, which “run in the cloud while your laptop is closed,” so a week’s allowance can go while nobody is watching.

On The X Subscription, the pool isn’t only Grok Bot’s. Grok’s pricing says “Every tier includes a pool of AI usage shared across Grok and Cursor,” so once Bots empty it, Grok chat, Grok Build and Cursor’s Grok models move onto paid extra usage too, or stop. Teams should check their settings: on legacy Cursor Teams plans, “on-demand usage is enabled by default.”

What to do now

1. Look at your meter and its reset date. On The X Subscription, open Usage at grok.com/dashboard; the usage view “shows how much has been used and the next reset date.” On a legacy Cursor plan, it’s in Grok Bot under Settings → Usage & Billing, or at cursor.com/dashboard.
2. Cap extra charges before you carry on. On The X Subscription, leave Auto Top-up off or set a monthly additional usage limit under Additional usage credits at grok.com/dashboard/billing; alerts alone “do not stop usage,” says the spending caps page. On a legacy plan, turn off on-demand or set On-demand monthly limit. Either way, “The cap does not stop a Bot in the middle of a run.” One user on the forum, who upgraded from Pro+ to Ultra on October 31, reports “about US$358 paid in under a week” and “no warning before it moved to paid on-demand.”
3. If the meter doesn’t match your work, send support the numbers. Export your usage and write to support@x.ai: Cursor’s staff tell users to “email support@x.ai and they can check the details.”
4. Make what’s left last. Cursor’s staff advice is to “start a new chat for each task, use routines less often, and hand off heavy implementation work to Cursor cloud agents.” Pause routines you don’t need this week, and narrow their triggers: the routines docs warn that broad listeners such as “every new message” “create noise, consume usage, and increase the chance of acting on irrelevant input.”
5. Think twice before upgrading for more. The same user reports that after moving to Ultra, “the weekly allowance ran out after about 710M tokens, within 21.5 hours,” against about 1,346M tokens the week before on Pro+. That’s one account’s export, not a measurement, but until SpaceXSI says what changed, a bigger plan buys a bigger share of an allowance nobody has sized.
6. A referral can earn a reset, but not today. On The X Subscription, a friend who signs up through your link gets two weeks of Grok Bot free, and “A usage reset is recorded on your account 7 days after your friend’s first payment,” per Cursor’s help. It’s rolling out gradually, for individual Premium, Super and Ultra plans “billed in the US, bought on the web.”

Keeping work going while Grok Bot waits

If you can wait, the reset costs nothing. If you can’t:

• Pay for extra usage, with a cap set first, as above.
• Use another lab’s plan. Claude Code runs on a Claude plan and Codex on a ChatGPT plan, each with limits of its own. For an agent that works while you’re away, Anthropic’s Claude Duet is “available as a research preview to users on Pro, Max, and Ultra plans in the US, through a waitlist,” and “can keep working after you close the app,” per its help article. It draws on your Claude plan’s limits, background work included.
• Don’t count on Grok Build. On The X Subscription it draws on the same pool, so moving the work there doesn’t get around the limit.

Enjoy doesn’t run Grok Bot. It runs Grok Build on your Grok or X subscription beside Claude Code and Codex, each signed in to its own plan, so when the Grok pool is empty you can switch the conversation to another agent and the work comes with it. It shows Grok Build’s weekly usage and when it resets. Enjoy’s scheduled workflows can take over some routine jobs, but they run on your computer, only while it’s awake and Enjoy is open, not on a cloud computer while your laptop is closed.

We’ll update this memo when SpaceXSI or Cursor says what changed.