A Grok Bot error rejected the model name grok-4-7-0907 for several users over the past 48 hours. This error might seem like just a minor thing, but with Grok 4.7 supposed to be releasing this week, it is a good sign that xAI intends to implement the newer, updated model immediately for users of Grok Bot.
On 7 September 2026, David Ondrej posted a screenshot of what he called the first error he had seen in Grok Bot. The error seems fairly simple, and notes that the AI model that Grok Bot was trying to run on was not found. The key here is that it was a Grok 4.7 build: grok-4-7-0907.
Not Public Yet
The model version isn’t yet available on xAI’s public model list, but it doesn’t tell us why the call was rejected silently in this particular version. It seems that the 0907 indicator in the back could also indicate a rough version date – September 7th, the same day that David noticed the error.
If the model identifier is real, Grok Bot tried to route to a dated 4.7 name and the backend refused it, which seems like a staging miss on xAI’s part. Either Grok 4.7 wasn’t quite ready for showtime, or the team behind Grok Bot pulled the pin on a release a bit too fast.
Sadly, as the prompt errored out, they never got to see the public capabilities of Grok 4.7.
Stealth Public Testing?
Mark Kretschmann, quoting that post about half an hour later, mentioned an interesting theory that the Cursor and xAI teams are already stealth-testing Grok Bot with Grok 4.7 behind the scenes. That doesn’t mean wide user access, but likely access for the internal team members who are actively working on projects like Grok Bot and Grok Build.
Still on 4.6 For Now
The developer docs still point code and chat at grok-4.6. There is no grok-4.7 listing on the models page, the 4.7 model card returns a 404, September release notes do not mention 4.7, and x.ai/news still has no 4.7 post. The latest model post there is still Grok 4.6, from 12 August 2026.
We’ll likely be waiting another few days for the official release of Grok 4.7, but it seems that it might already be running in the background for some users, especially as Grok Bot doesn’t actively indicate what model it is running a task on – it just pulls from the “Grok Bot bucket” through your Cursor, xAI, or X subscription.
