Grok Bot Hit Its Weekly Limit: How to Continue and Why Subscriptions Do Not Stack

When Grok Bot halts with a limit-exhausted message in the middle of setting up a team workspace or executing tasks, the natural first reaction is to quickly pay for a second plan. You might be considering linking an individual SuperGrok or SuperGrok Heavy subscription to an already active Cursor plan. However, billing rules do not allow pooling included usage between a Cursor plan and a linked individual SuperGrok or X Premium+ subscription on the same Cursor account. Purchasing a second plan will only result in parallel charges to your card without adding any available usage.

In this situation, teams have three viable options:

1. Wait for the scheduled weekly quota reset if tasks do not require immediate resolution.
2. Enable on-demand usage and set a spending limit so the bot can continue working with additional usage billed through Cursor.
3. Upgrade your subscription tier within one chosen ecosystem—for example, upgrading from Cursor Pro+ to Cursor Ultra, or upgrading an already linked SuperGrok account to Plus or Heavy.

Hands-On Experience: What Teams Encountered on September 16

The easiest way to understand the logic behind these constraints is through real-world situations. On September 16, 2026, two users described their quota-exhaustion challenges on X.

At 11:56 UTC+8 (Shanghai), Dang Lu (post on X) shared that he had exhausted Grok Bot’s weekly limit on the very first day during baseline tool setup for his team. He highlighted an inconvenient catch: once a workflow relies on the bot, there is no quick shortcut to keep working. Buying SuperGrok on top of a Cursor Pro plan provides no additional usage pool. Even if a team is willing to pay for two subscriptions at once, they are forced to choose between waiting for the reset, enabling on-demand, or upgrading a plan.

Later, at 16:26 UTC+8 (Shanghai), user 360 AXE (post on X) described a scenario on a Cursor Ultra plan. According to his observations, the included IDE limit was about 3% used, while the weekly Grok Bot indicator had reached around 80%. The author also reported on-demand charges while IDE resources sat idle. In subsequent replies, he added that he had already spent six days locked out beforehand and feared another period of downtime. However, the published post does not explain the root causes of the billing discrepancy, and reaching definitive conclusions would require specific account details.

The published posts do not show how this situation was ultimately resolved, but the rules on the Cursor plans page directly explain the reasoning behind these restrictions.

How Limits Work: Weekly Usage vs. On-Demand

Grok Bot’s client and the Cursor web dashboard use two distinct accounting mechanisms:

• Weekly usage (weekly limit). This is the baseline included usage bundled with your Cursor plan (Pro, Pro+, Ultra, or a seat on Cursor Teams) or granted via linking an individual SuperGrok / X Premium+ account. This counter resets once a week.
• On-demand usage (additional usage). The usage volume billed once the included weekly quota is completely exhausted. Charges are processed through Cursor.
• On-demand monthly limit (monthly spending limit). A threshold to control additional expenses. In the Grok Bot application, this parameter is labeled On-demand monthly limit, while in the cursor.com/dashboard web interface under Spending, it is labeled Monthly Limit.

A zero balance of Weekly usage does not halt the bot on its own if on-demand is enabled. However, an important nuance must be noted: the On-demand monthly limit is not a hard cap in the middle of executing a task. If the bot is already running, the active run may finish even past the configured limit, though completion is not guaranteed. After that, further on-demand usage is halted until you manually increase the limit or a new billing cycle begins.

Why Subscriptions Do Not Stack and How to Scale

If you are considering purchasing a second subscription due to quota shortages, keep in mind that under Cursor rules, linking SuperGrok or X Premium+ constitutes a usage grant rather than an additive plan.

If an account already has an active Cursor Pro, Pro+, or Ultra plan, linking SuperGrok Plus will not expand Grok Bot’s available quota. Likewise, purchasing Cursor Ultra on top of an already linked SuperGrok Heavy will not add quota to what already exists. Furthermore, linking is permanent: you cannot unlink a SuperGrok profile or transfer it to another Cursor account.

If your baseline allowance is consistently insufficient, there are two predictable paths to scale without constant reliance on on-demand:

• Upgrade your Cursor plan. Moving from Pro to Pro+ or from Pro+ to Ultra increases Grok Bot’s included weekly tier to match the corresponding plan.
• Upgrade your linked SuperGrok subscription. If access is provided via an external subscription, you can upgrade SuperGrok itself to Plus or Heavy. The updated Weekly usage tier reflects within 24 hours. Purchasing Cursor Ultra while waiting is pointless—the limits will still not stack.

Step-by-Step Procedure to Continue Working

To bring Grok Bot back online and keep future charges under control, follow this sequence:

1. Check your client status. In the Grok Bot app, open Settings and check the values for Weekly usage and On-demand monthly limit. If on-demand is disabled, a depleted weekly balance prevents the bot from starting new tasks.
2. Set a monthly spending limit in your browser. Go to cursor.com/dashboard, open the Spending section, and specify a Monthly Limit. This caps subsequent on-demand usage expenses, keeping in mind that an already active run may finish above this amount.
3. Enable on-demand in the app. Toggle On-demand to Enable. If prompted for payment details, complete card entry in the web interface.
4. Verify responsiveness on a small task. Before launching autonomous agents on lengthy workflows, run a brief, isolated prompt to verify that the bot responds and usage tracks as expected.

We have not conducted our own billing measurements on paid accounts nor measured the exact cost of individual tasks, so we recommend starting with a minimal monthly limit and increasing it only as real workloads are confirmed.