On November 1, 2026, Elon Musk revealed that the cost of providing the AI agent Grok Bot had been unsustainably high relative to revenue. Unlike the regular Grok chat app, Grok Bot is an AI agent that operates a PC in the cloud to carry out tasks. Musk made the remark in reply to a post asking for a reset of usage limits, after many users reported burning through their weekly allowance early. However, it has not been confirmed how much the usage limits were actually reduced.
To understand Grok Bot's usage terms, it is important to distinguish between the weekly usage allowance included in a subscription and the monthly usage cap that controls extra charges after the limit is reached. Raising the monthly cap for additional usage does not increase the weekly allowance included in the plan itself. Users need to check not only how much allowance remains, but also which tasks consume it under their own plan and whether work can continue after the limit is hit.
Musk acknowledges the cost problem as users complain of sharply reduced weekly allowances
In response to a post from Doge Norway asking for a reset because many users had used up their weekly allowance quickly, Musk replied on X that "Grok Bot costs were unsustainably high relative to revenue". The remark suggests that an imbalance between operating costs and revenue lies behind the usage-limit issue. However, he did not explain the specific amounts of cost or revenue, or how much the usage limits were changed.
TechCrunch's November 2 report cites a user's report that weekly usage jumped from 50% to 100% over the weekend. That is, however, an individual user's account, not measured data showing that allowances were halved across all plans. A sudden change in the usage percentage alone cannot tell us whether the actual workload increased, whether the allowance shrank, or whether the way usage is measured was revised. Musk's comments also give no concrete figures for costs and revenue, so it is impossible to calculate the profitability of the Grok Bot business as a whole.
Grok Bot keeps working after you close your PC, and picks AI models automatically
Grok Bot's usage is harder to gauge than that of a typical chat AI, where the number of questions and answers is the main measure. According to the official product description, Grok Bot runs on a persistent cloud PC equipped with a browser, a file system, and a terminal. Even after the user closes their PC or the app, running tasks and recurring scheduled tasks continue in the background. Multiple bots can also run in parallel, each handling reasoning, app operation, and file processing. However, bots on the same account share a single cloud PC, so adding more bots does not assign each one its own independent PC.
The official FAQ also treats the regular Grok chat app and Grok Bot as separate products. Confusing their weekly usage limits could lead users to misjudge how much they can actually use Grok Bot. In addition, Grok Bot automatically selects which AI model to use depending on the task, and in some cases it may choose not only SpaceXSI's own models but also models from other companies listed among its contracted providers. There is no screen for users to specify a model, and the name of the model actually used for each request is not displayed.
According to the FAQ, the model that is automatically selected does not change the per-token price applied to the user. The rate at which the allowance is consumed, however, varies with the type of task and the effort required to process it. Even with the same number of requests, therefore, different background tasks will not necessarily consume the same amount of usage. It is difficult to estimate accurately how many more jobs can be completed from the remaining percentage alone. These product specifications by themselves, though, do not explain why the reported sudden change in usage rates occurred, or how much cost the operator bears for each model.
Different allowances and extra charges under legacy plans and the unified plan
Grok Bot's terms also change depending on whether a user keeps a legacy subscription or moves to "The X Subscription," which bundles Grok, Cursor, and other products. According to official materials, migration is optional for existing users, who can continue on their old plans. New users, on the other hand, start with the unified plan. Among the unified plans, Premium, Super, and Ultra include Grok Bot access; Plus and Free do not. Legacy plans apply a weekly allowance dedicated to Grok Bot, whereas the unified plan uses a weekly allowance shared across the eligible products.
The table below summarizes the differences between the two as of November 2, 2026, based on Cursor's explanation of plans and billing, the Grok Bot unified plan guide, and the official usage-limit documentation. The comparison covers legacy individual subscriptions with account linking and the unified plan; it excludes individual enterprise contracts, monthly prices, and the actual number of jobs that can be completed.
| Item | Legacy plan / account linking | The X Subscription |
|---|---|---|
| Weekly allowance | Grok Bot's weekly allowance is measured on the Cursor side | For eligible in-house models, the weekly allowance is shared across Grok, Grok Bot, and Cursor |
| After reaching the limit | Work can continue if additional pay-as-you-go billing is enabled. If it is disabled, work stops until the weekly allowance resets | Overage on eligible in-house models is paid with additional credits. Use of third-party models in Cursor is not included in the shared allowance and is billed separately |
| Where to check usage | cursor.com/dashboard | "Usage" on grok.com/dashboard |
Allowances from SuperGrok and similar subscriptions linked with a legacy Cursor subscription are not combined; the larger weekly allowance applies. Billing for each subscription may nonetheless continue separately. For example, Ultra and SuperGrok Heavy correspond to the same plan tier, so subscribing to both does not add their allowances together.
Under the unified plan, products other than Grok Bot also consume the same weekly allowance, so the number of requests to the bot alone may not explain a drop in the remaining amount. Under legacy plans, whether additional pay-as-you-go billing is enabled determines whether work can continue after the allowance is used up. However, these differences in billing methods do not explain the cause of the reported sudden rise in usage rates or indicate the rate at which allowances were cut.
Billing for the AI models Grok Bot selects automatically internally must also be distinguished from billing when a user explicitly uses a third-party model in Cursor. Under the unified plan, third-party models used in Cursor are outside the shared weekly allowance and incur extra charges. Automatic model selection inside Grok Bot, by contrast, is described in the official FAQ as a separate mechanism. The two therefore cannot be treated as the same billing method.
After the allowance runs out: managing continued work and extra costs
What users need to check is not only the monthly fee or the remaining allowance. Equally important is what happens when the weekly allowance is used up: whether work stops until the next reset, or whether the user pays extra to continue. Under legacy plans, if additional pay-as-you-go billing is disabled, work cannot continue once the weekly limit is reached. If it is enabled, work can continue, but extra charges apply to the overage.
Extra charges on legacy plans can be managed through "On-demand monthly limit" under "Usage & Billing" in settings, or "Monthly Limit" under "Spending" in the web version. Cursor does not state, however, that setting this cap will always stop running work at that amount. A bot that is already running may complete its work beyond the set monthly limit. Setting a monthly cap therefore does not guarantee that extra charges will stay within that range.
Under the unified plan, users manage whether auto-charge is on or off, as well as a monthly cap on additional usage. When use of eligible in-house models exceeds the shared weekly allowance, charges are paid from additional credits. Users therefore need to check this payment method separately from pay-as-you-go billing under legacy plans. Note also that on legacy plans, the desktop and mobile versions share the allowance of the same account.
The remaining weekly allowance and the setting for how much extra charge to permit after exceeding it are separate things. Trying to keep work going without interruption may incur additional costs, while trying to hold costs down may mean pausing work until the weekly allowance resets. In this case, it remains unclear which subscription plans were affected, how much allowances or consumption rates changed, and when the changes took effect. Whether such specifics are disclosed will matter for users as they plan their work and estimate costs going forward.