Today in Grok

Musk says Grok Bot usage fixes are underway, with no date or numbers

On 8 November (9:17pm MYT) Elon Musk posted that Grok BotGrok Bot An AI teammate from SpaceXAI that has its own computer, connects to your apps, and can keep working on tasks for you. fixes for "improved token efficiencyToken efficiency How much of your usage allowance an AI spends to do the same job. AI tools read and write text in small chunks called tokens, and usage limits are often counted this way. and smarter behavior" are underway. It came after days of public complaints that Bots were using up weekly usage quickly. As of our check on 9 November, nothing in the official changelogChangelog A dated list of what changed in each new version of an app, published by the company that makes it. shows a fix has shipped.

What we learned

1. Musk's post is one line. It gives no release date, no measured saving and no detail on what "smarter behavior" means. X showed about 4 million views and 4,064 replies when we checked.
2. About four hours later, Matt Palmer (@mattyp, whose X profile lists @bot at SpaceXSI) asked users to reply with feedback and said he would read it all. That is a request for input, not a release. His post had 1,978 replies at our check.
3. The official Grok Bot changelog still lists v0.78.1 from 27 October as its latest entry, with nothing about these fixes. So there is no shipped change we can test or measure yet.
4. SpaceXSI's own routinesRoutine A saved instruction that runs on a schedule or when something happens, even when you are away. guide (last updated 29 October) says each routine run spends usage, and an hourly schedule or a busy Slack triggerTrigger The event that starts a routine, such as a new Slack message or a set time. can use a week of usage in a day. It advises pausing routines you don't need and widening schedules before raising a plan or on-demand limit. Individual users' posts about how fast their usage vanished are anecdotes we could not verify.

Why it matters: Treat this as a promise, not a fix. Until the changelog lists a release, don't expand Bot workflows on the hope of lower usage; instead check which recurring routines still need to run and how often.

Share this story