# Grok Bot weekly usage limit: why it runs out, how to cap it > Grok Bot's weekly allowance is unpublished and Cursor's on-demand cap isn't a hard stop. What burns usage, when it resets, X Subscription top-ups, and settings that help. - Canonical page: https://www.grokbotwiki.com/guides/grok-bot-weekly-usage-limit - Sources checked: 2026-11-01 - Evidence: The X Subscription usage, top-up and spending-cap docs, cursor.com/pricing, and Cursor billing and routines help rechecked October 25, 2026 · x.ai/bot and the Grok Bot changelog through 0.75.5 read in a browser October 25, 2026 · changelog entry 0.77.0 and docs.x.ai's Shared Bots page read October 28 · changelog entry 0.78.1 read October 29 · x.ai/pricing last read October 14, 2026 · forum staff replies rechecked October 14, 2026 · Cursor staff forum replies and user cost reports attributed, not reproduced · forum token-usage thread read October 27 · Cursor forum grok-bot tag rechecked November 1 · status.x.ai incidents API read November 1. Suggested workflows have not been independently tested. - Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X. ## How the meter actually works The X Subscription, launched October 12, 2026, changes the meter for anyone who buys or switches to it. SpaceXSI's docs say each paid seat gets one weekly pool shared across eligible Grok and Cursor use, including Grok Bot, rather than a separate Grok Bot allowance, and that usage rates vary by product. Once the pool is used, further use is Additional Usage paid from prepaid credit bought with top-ups, and third-party models in Cursor are paid from that credit from the first use. On a team, each seat has its own pool and the team shares one prepaid balance. After switching, usage is under Usage at grok.com/dashboard. The rest of this section describes the existing Cursor and SuperGrok plans, which continue for current subscribers. On the existing plans, every eligible plan includes Grok Bot usage that resets weekly, in a bucket separate from Grok chat and Cursor editor usage; Cursor staff confirmed in September that Grok Bot chats and routines do not draw on Cursor plan quota, with one exception: a Cursor Cloud Agent that a Bot launches bills to your Cursor plan. Allowances do not add together: Cursor's billing page says a Cursor plan and a linked SuperGrok or X Premium+ subscription do not stack, and Grok Bot uses whichever grants more weekly usage. After upgrading a linked SuperGrok tier, allow up to 24 hours for the weekly allowance to move. 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. That separation has a limit, and even Cursor staff got it wrong once. In an August thread a Pro user asked why Grok Bot was showing up against their Cursor model quota after an email had promised a dedicated pool. A staff reply first said Grok Bot simply used the plan's Cursor quota, not a separate limit; after the user quoted the announcement email back, staff corrected themselves: the weekly included Grok Bot pool genuinely is separate from Cursor plan usage, but only up to that weekly limit. Once the weekly pool is used up, any further Grok Bot usage on an on-demand-enabled account bills from the same shared on-demand pool as the rest of your Cursor usage, not a second dedicated on-demand allowance. If your dashboard shows Grok Bot eating into Cursor spend before your weekly allowance looks exhausted, that overflow behavior, not a bug, is the likely explanation; check the usage screen for which pool it charged. A second, cosmetic version of the same confusion turned up on a Teams seat in September: grok-bot-default and grok-bot-cua rows were appearing inside the Cursor Models and Other Models breakdown on the Spending page, making it look like Grok Bot was eating the Cursor quota even though the headline percentages stayed Cursor-only. Cursor staff (mohitjain, Colin) called it a display bug they were tracking and confirmed by September 11 that the rows were removed from that breakdown. Asked on October 20 whether the same separate-pool behavior carries over to the new Ultra, a Cursor staff member said no: on The X Subscription (Premium, Super and Ultra) there is no separate Grok Bot allowance at all, Grok Bot draws from the same shared weekly pool as your Cursor and Grok usage, and only third-party models such as Claude or GPT bill from prepaid top-up credit; the legacy separate-allowance behavior described above applies only to the older Cursor plans. Usage readings jumped for many accounts on November 1. In a forum thread started at 04:25 UTC, AerethoS, on Cursor Ultra, wrote that the weekly meter at the bottom of the app kept flipping between about 77% and 100% while their own tracking read 77.7%. Within hours about twenty users in all had reported similar jumps, many of them roughly a doubling (33% to 66%, 44% to 88%, 50% to 100%) with no new activity, some on legacy Cursor Pro+ and Super; some saw the Bot and Settings disagree, and at least one said the Bot later stopped replying with limit reached. At 05:38 UTC the status page opened an incident on a degradation affecting the billing and usage dashboard, listing cursor.com and the Enterprise Dashboard rather than Grok Bot, and it was still being investigated at 08:44 UTC. No Cursor staff member had replied in the thread by 10:00 UTC, and the incident does not say whether usage will be corrected. The official step for now is to follow that incident on [our status guide](https://www.grokbotwiki.com/guides/is-grok-bot-down) or status.x.ai, and note your reading before and after so you can raise it with support. Cursor staff also explained why long chats get expensive: every turn re-reads that Bot's whole conversation, and it only auto-summarizes near the model's limit. In one account staff reviewed, the busiest Bots were re-reading roughly 80,000 to 90,000 tokens per step, and about a third of all turns were Bots waking other Bots. A second staff explanation, from October 14, covers the usage page itself. A user asked why rows on the usage page showed 50,000 to 165,000 tokens for one-line replies. A Cursor staff member replied that the Tokens number on each row counts everything the model read on that call, including the Bot's instructions, memory, tool list and recent chat, that most of it is cached context billed at a much lower rate than new input, and that hovering over a token count on the usage page splits it into input, output, cache read and cache write; all of those rows count against the plan's included usage, so nothing extra had been charged. Staff endorsed the same levers: fewer event-triggered wake-ups (the user's change-watch routine had been waking a Bot on every pull request), fewer Bot-to-Bot messages, and a leaner background for each Bot, which cut the user's per-call size to roughly a third. Cloud Agent coding jobs are always much larger than a single reply, and staff pointed to an AGENTS.md map of each repo and a .cursor/CLOUD.md file to shorten them. The same user later reported spending $100 of on-demand usage in under a day, and another user agreed on October 27; there is still no way to route a coordinating Bot to a cheaper model. 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. Since 0.63.0, running out shows the usage limit notice rather than Bot failed to respond, and since 0.59.0 the limit banner offers Upgrade, Set Spend Limit, or Request Upgrade to ask your admins. Since 0.75.5 (October 23), if your Grok Business seat does not cover Grok Bot yet, the usage limit message says to ask your Grok Business admin to connect your team. See [our plan and pricing guide](https://www.grokbotwiki.com/guides/grok-bot-which-plan) for the plans and spending controls; the linked forum report describes an earlier user experience. The usage banner can be dismissed but returns, which one thread asks to fix. Since 0.77.0 (October 26), when usage cannot load, Usage & Billing keeps the last reading with Try again, even after a relaunch, instead of going blank. Since 0.78.1 (October 27) the usage limit banner closes on its own once you are back under your limit, and a usage breakdown from a Bot labels its catch-all row Deleted bots, group chats and other people's bots. On a shared Bot (the docs' new name for a Team Bot), the docs say a reply uses the usage of the person it is answering, in your own chat, in Slack and in group chats, and that Your usage limit has been reached in a teammate's shared Bot means your own allowance ran out, while This Bot's owner has reached their usage limit means that reply was billed to the owner. Sources: https://x.ai/changelog/bot#v0.78.1, https://docs.x.ai/grok-bot/shared-bots, https://x.ai/changelog/bot#v0.77.0, https://docs.x.ai/x-subscription/usage-limits, https://docs.x.ai/x-subscription/extra-usage, https://docs.x.ai/x-subscription/grok-bot, https://x.ai/news/x-subscription, https://docs.x.ai/grok-bot/faq, https://cursor.com/help/grok-bot/plans, https://x.ai/changelog/bot, https://forum.cursor.com/t/grok-bot-spend-cursor-usage-i-cant-accept-it/169796, https://forum.cursor.com/t/does-grok-bot-consume-cursor-quota/171742, https://forum.cursor.com/t/1-500-in-one-week-running-a-grok-bot-fleet-expected-or-a-bug/172705, https://forum.cursor.com/t/grok-bot-gives-no-warning-before-weekly-usage-spills-into-paid-on-demand/169679, https://forum.cursor.com/t/grok-bot-token-usage/174723, https://forum.cursor.com/t/is-grok-bot-eating-at-cursor-usage-i-thought-it-had-its-seperate-usage/170990, https://forum.cursor.com/t/grok-bot-weekly-usage-meter-flips-between-77-and-100-in-real-time/176909, https://status.x.ai/history?incident=cursor-com%2Fps_838fe2a3a154acfa ## 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. Cursor staff add four more: start a fresh chat for each task from the + at the top of the sidebar, keep standing instructions in the Bot's profile so a fresh chat loses little, tell Bots to message each other only when action is needed, and space routines out rather than running them every few minutes. Cursor's routines help puts the last point bluntly: an hourly schedule, a short interval, or a Slack trigger on a busy channel can use a week of usage in a day. The run caps are no brake on that: since 0.75.5 your routines can run up to 300 times an hour in total, up from 100, and each routine up to 200 times an hour. A forum thread on stretching the weekly allowance (380 views by October 31) collects similar user tips. Its author, linkd, notes that a long chat re-reads its whole history on every step and suggests starting new conversations with the same Bot; another user, bee, batches requests into one text file that a Bot reads and splits into tasks for other Bots, keeps shared rules in a common workspace, and avoids spreading work across many Bots. A third user said they had sent Cursor feedback asking for chat branches that carry a short core memory of the Bot's role instead of the full history. No Cursor staff member had replied there by October 31; the official step remains the one above: start a fresh chat per task and keep standing instructions in the Bot's profile. Coding work a Bot hands off is billed separately. Cursor staff said in September that a Cursor Cloud Agent launched by a Bot bills to your Cursor plan, and on a team, everything you run, including the Cloud Agents your Bot starts, is billed through your team seat. Our [shared-computer guide](https://www.grokbotwiki.com/guides/grok-bot-shared-computer) explains why long chats cost more on every reply. Troubleshooting during an outage burns usage too. When scheduled routines failed on October 8, several users said they spent a large share of their week having Bots investigate, one reporting over 90 percent used with five days left. Cursor staff said pausing, editing or recreating routines would not help during that incident. Check [Is Grok Bot down?](https://www.grokbotwiki.com/guides/is-grok-bot-down) and the forum before asking a Bot to debug itself. Retry loops are cheaper on current versions. The October 11 release (0.69.0 to 0.70.2) says Bots now wait for a rate-limited connector's retry delay instead of looping, and connector calls fail less often, so update the app if a Bot seems to spend usage retrying the same connector. Sources: https://x.ai/changelog/bot, https://cellcog.ai/blog/grok-bot-problems/, https://forum.cursor.com/t/all-grok-bot-routines-failed-to-run/174125, https://forum.cursor.com/t/anyone-used-grokbot-on-the-api-very-high-costs/169551, https://forum.cursor.com/t/grok-bot-ultra-users-how-do-you-make-the-weekly-allowance-last-mine-reached-99-in-three-days/171221, https://forum.cursor.com/t/1-500-in-one-week-running-a-grok-bot-fleet-expected-or-a-bug/172705, https://cursor.com/help/grok-bot/routines, https://forum.cursor.com/t/does-grok-bot-consume-cursor-quota/171742, https://forum.cursor.com/t/cloud-agents-by-grokbot-using-team-cloud-credits-instead-of-personal-usage/173419, https://forum.cursor.com/t/best-practices-for-using-grok-bot-more-token-efficiently/175188 ## The setting that protects you Review the on-demand control described in [our plan and pricing guide](https://www.grokbotwiki.com/guides/grok-bot-which-plan); do not assume a spending limit interrupts work immediately. Decide deliberately whether on-demand is enabled, and if it is, set the limit before the first routine runs unattended. On a legacy self-serve Cursor Teams plan, on-demand is enabled by default. On The X Subscription the controls are different. SpaceXSI's docs list four: the weekly pool, a prepaid balance, a monthly additional usage limit, and Auto Top-up, which is off unless you turn it on. Set them under Additional usage credits at grok.com/dashboard. Adding credit does not raise the monthly limit, and spend alerts warn without stopping usage. The steps below are for the existing Cursor plans. 1. In Grok Bot, open Settings → Usage & Billing and find On-demand monthly limit (choose Enable if it is off); on the web, the same cap is Spending, Monthly Limit at cursor.com/dashboard. If Grok Bot asks for a card, or you subscribed in the iOS or Android app, set it on the web. 2. Either disable on-demand, accepting that Bots stop when the allowance ends, or set a monthly limit you can afford, remembering that a run already in progress can finish past it. 3. In the Grok Bot app, open Settings → Usage & Billing and note today's level and when it resets, which the screen shows since 0.63.0. Since the October 11 release the meter labels its percentage as used, so 80% means 80% gone, not left, and Current plan shows your plan's name. 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 (or, on The X Subscription, Auto Top-up and the monthly additional usage limit) is deliberately set. - [ ] Each new task starts in a fresh chat instead of one ever-growing thread. - [ ] 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. Sources: https://docs.x.ai/grok-bot/faq, https://cursor.com/help/grok-bot/plans, https://docs.x.ai/grok-bot/settings-and-notifications, https://x.ai/changelog/bot, https://docs.x.ai/x-subscription/spending-caps, https://docs.x.ai/x-subscription/extra-usage ## Quick answers ### Is there a Grok Bot spending cap? Yes, and how it behaves depends on your plan. On The X Subscription, SpaceXSI's docs say a monthly additional usage limit is how you put a hard stop on paid extra usage, and extra usage also stops when your prepaid balance is empty; spend alerts only warn. On the existing Cursor plans there is a caveat. The On-demand monthly limit in Grok Bot Settings is the same cap as Monthly Limit under Spending on the Cursor dashboard, and Cursor's billing page says it is not a hard stop in the middle of a run: a Bot already working can finish past it. With on-demand off, Grok Bot stops when weekly usage runs out. A Cursor staff reply also suggests a $0 on-demand limit if you want a hard stop. ### How big is the weekly allowance? Unpublished. On The X Subscription, x.ai/pricing and cursor.com/pricing give Premium 4x the usage of Plus, Super 15x and Ultra 50x, without an absolute figure, and that pool also covers your Grok and Cursor use. The x.ai/bot pricing panel words it relative to Premium instead: Super 3.5x and Ultra 12x Premium usage. For the existing plans, the docs describe it only relatively: Pro below Pro+ below Ultra, with SuperGrok tiers following the same pattern and an X Premium+ link below SuperGrok Plus. Cursor staff said on September 22 that there is no tier above Ultra and no published dollar figure, and on September 10 that Cursor Ultra and SuperGrok Heavy give the same top-tier Grok Bot allowance. 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. Cursor's billing page says the included grant resets weekly but does not name a day; on The X Subscription, SpaceXSI's docs say the live usage view shows the next reset date. Since version 0.63.0 (September 29), Settings → Usage & Billing shows your included usage and when it resets; before that fix, some accounts saw a message saying their plan had none. If your app is older, update it, or note the day the meter moves back up. ## Sources - [SpaceXSI: Introducing The X Subscription (October 12, 2026)](https://x.ai/news/x-subscription) - [Grok Bot docs: Shared Bots (whose usage pays for a shared Bot chat)](https://docs.x.ai/grok-bot/shared-bots) - [Grok Bot changelog: 0.78.1 (usage limit banner closes itself, October 27)](https://x.ai/changelog/bot#v0.78.1) - [Grok Bot changelog: 0.77.0 (Usage & Billing keeps the last reading, October 26)](https://x.ai/changelog/bot#v0.77.0) - [x.ai pricing: usage by plan](https://x.ai/pricing) - [Forum: Grok Bot token usage (staff reply on what the usage page's Tokens column counts, October 14)](https://forum.cursor.com/t/grok-bot-token-usage/174723) - [Forum: best practices for using Grok Bot more token-efficiently (user tips, October 18 to 31)](https://forum.cursor.com/t/best-practices-for-using-grok-bot-more-token-efficiently/175188) - [Forum: weekly usage meter flips between 77% and 100% (user reports, November 1)](https://forum.cursor.com/t/grok-bot-weekly-usage-meter-flips-between-77-and-100-in-real-time/176909) - [Status: billing and usage dashboard degradation, November 1](https://status.x.ai/history?incident=cursor-com%2Fps_838fe2a3a154acfa) - [Cursor pricing: usage by plan](https://cursor.com/pricing) - [Grok Bot product page: usage by plan](https://x.ai/bot) - [The X Subscription docs: usage limits](https://docs.x.ai/x-subscription/usage-limits) - [The X Subscription docs: extra usage credits and top-ups](https://docs.x.ai/x-subscription/extra-usage) - [The X Subscription docs: spending caps](https://docs.x.ai/x-subscription/spending-caps) - [The X Subscription docs: Grok Bot on The X Subscription](https://docs.x.ai/x-subscription/grok-bot) - [Billing and access FAQ](https://docs.x.ai/grok-bot/faq) - [Cursor Grok Bot docs](https://cursor.com/help/grok-bot/plans) - [Settings: usage and billing](https://docs.x.ai/grok-bot/settings-and-notifications) - [Forum: "Grok Bot spend cursor usage, I can't accept it" (staff correction, 1,369 views)](https://forum.cursor.com/t/grok-bot-spend-cursor-usage-i-cant-accept-it/169796) - [Forum: Ultra allowance at 99% in three days (staff tips)](https://forum.cursor.com/t/grok-bot-ultra-users-how-do-you-make-the-weekly-allowance-last-mine-reached-99-in-three-days/171221) - [Forum: about $1,500 in one week running a Bot fleet (staff reply)](https://forum.cursor.com/t/1-500-in-one-week-running-a-grok-bot-fleet-expected-or-a-bug/172705) - [Forum: usage too low even on Cursor Ultra (staff reply)](https://forum.cursor.com/t/grok-bot-usage-too-low-even-on-cursor-ultra/172584) - [Forum: does Grok Bot consume Cursor quota? (staff reply)](https://forum.cursor.com/t/does-grok-bot-consume-cursor-quota/171742) - [Forum: no warning before weekly usage spills into on-demand](https://forum.cursor.com/t/grok-bot-gives-no-warning-before-weekly-usage-spills-into-paid-on-demand/169679) - [Forum: very high costs on the API](https://forum.cursor.com/t/anyone-used-grokbot-on-the-api-very-high-costs/169551) - [Forum: usage-limit banner keeps coming back](https://forum.cursor.com/t/grok-bot-let-dismiss-of-weekly-usage-limit-banner-stick-x-keeps-coming-back/172013) - [CellCog problems tracker](https://cellcog.ai/blog/grok-bot-problems/) - [Cursor help: routines (usage warning)](https://cursor.com/help/grok-bot/routines) - [Grok Bot changelog (usage screens in 0.59.0, 0.63.0 and the October 11 release)](https://x.ai/changelog/bot) - [Forum: Cloud Agents started by Grok Bot bill to the team seat (staff reply, September 30)](https://forum.cursor.com/t/cloud-agents-by-grokbot-using-team-cloud-credits-instead-of-personal-usage/173419) - [Forum: all Grok Bot routines failed to run, October 8 (staff replies; users report usage spent troubleshooting)](https://forum.cursor.com/t/all-grok-bot-routines-failed-to-run/174125) - [Forum: is Grok Bot eating at Cursor usage? (staff replies fixing a display bug, then clarifying the new Ultra's shared pool, October 20)](https://forum.cursor.com/t/is-grok-bot-eating-at-cursor-usage-i-thought-it-had-its-seperate-usage/170990)