Some Grok Bot users reported that their weekly allowance had suddenly run out over the Halloween weekend, including people who said they had not used the agent overnight. TechCrunch reports that Elon Musk confirmed the change was related to the cost of serving the product.
What users reported
The report describes users seeing their displayed usage rise sharply, in some cases from around half of their allowance to the full limit. Those accounts establish the reported experience; they do not provide a complete specification of the new limits for every subscription.
Musk said serving costs were too high relative to revenue. The report also states that he had not explained how subscribers' allowances would be affected going forward. A business using an agent therefore cannot infer a stable new capacity commitment from the explanation alone.
Why this matters for automated work
A weekly allowance is part of a workflow's operating capacity. If its effective limit changes, a task that was affordable or available during setup may become unavailable before the next reset. The immediate question for a team is which jobs require the agent to finish and what happens when that capacity is exhausted.
That is an operational implication of the reported change, rather than evidence that a specific customer lost data or that every Grok Bot task stopped. The captured source does not establish those outcomes.
What remains unresolved
Users should look for the current allowance, reset information and any official explanation for their own plan before relying on an earlier usage estimate. For recurring tasks, retain the inputs and completed outputs so an interrupted run can be identified and reviewed. A service's rapid adoption does not by itself establish predictable capacity, and the cost explanation does not answer how future limits will be communicated or measured.