Musk says Grok Bot limits were cut because serving costs were 'unsustainably high'

Elon Musk has confirmed that Grok Bot usage limits were deliberately tightened, saying the cost of running the AI agent was "unsustainably high relative to revenue." TechRadar reported the statement on 2 November 2026.

What happened

The confirmation came after an X user asked Musk for a Grok Bot usage reset. The user said they had hit their 100% usage limit four days before it was due to reset, and added: "Normally I don't even reach 100%."

Musk replied: "The cost of serving Grok Bot was unsustainably high relative to revenue."

User reports

Several X users said their Grok Bot usage reached the 100% limit while they were sleeping and not running any AI agents. Users claimed their usage meter jumped:

• from 50% to 100%
• from 35% to 78%
• from 70% to 100%

All of these were reported without the users having supposedly used Grok Bot in between. These figures are user claims and have not been independently verified.

A Reddit thread described the move as an "indirect rug pull" of Grok Bot, saying features and usage were limited to cut costs.

Wider context

TechRadar places the change within broader scrutiny of AI product economics. It reports that tech stocks, including those of many leading AI firms, fell sharply last week as investors worried about industry profitability, and that Google revealed its own AI summaries have hurt its search advertising revenue.

TechRadar also notes that users of tools like ChatGPT and Claude Code can often spend many times more in tokens than they pay in monthly subscriptions. It says OpenAI quietly announced tighter usage limits recently, which frustrated users.

The new Grok Bot cap, the size of the allowance in tokens or requests, and any pricing changes have not been disclosed. Usage is displayed to users as a percentage of a limit.

What this means

Musk's statement is a direct acknowledgment that Grok Bot's serving cost exceeded the revenue it generated, and that the usage allowance was reduced in response. For users, the practical effect is that the same workload now consumes a larger share of the cap, with the cap size itself not stated publicly.

The reports of meters jumping while idle are user claims, and the cause of those specific jumps is not explained. Anyone running Grok Bot in agentic workflows should check their usage meter directly instead of assuming earlier consumption patterns still hold.

TechRadar's own view is that AI producers are unlikely to subsidize product costs for users indefinitely, and that Grok Bot's lower cap may be the first of many such changes. That is the outlet's opinion, not a statement from Musk.