Model name is not valid: "grok-4-7-0907" - Grok Bot

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Product: Grok Bot for macOS
Account: same Cursor / SuperGrok account used to sign in to the desktop app
Date / timezone: Monday, September 7, 2026, America/Chicago (CDT)

Summary
Grok Bot on Mac returns “AI Model Not Found.” The model string it tries to use is not valid: “grok-4-7-0907”. The error persists after the official recovery steps. There is no in-app “Report an issue” control.

Exact error
AI Model Not Found
Model name is not valid: “grok-4-7-0907”

Steps already tried

  1. Fully quit Grok Bot with Cmd+Q and reopen
  2. Sign out and sign back in
  3. New chat with the existing Bot
  4. New → Create new agent
  5. Confirmed there is no model picker in Settings → General → Agent
  6. Confirmed there is no in-app Report an issue option

Result
Same error on existing Bots and on a new agent. Local app recovery does not change the model ID.

Notes
grok-4-7-0907 looks like a dated Grok 4.7 snapshot. Grok 4.7 does not appear in the public model docs yet. This looks like a backend assignment to an unpublished model, not a corrupt local install.

I can provide another screenshot, About panel text, or a new request ID if needed.

Steps to Reproduce

Grok Bot on Mac returns “AI Model Not Found.” The model string it tries to use is not valid: “grok-4-7-0907”. The error persists after the official recovery steps. There is no in-app “Report an issue” control.

Expected Behavior

Expecting a valid model. Grok Bot to stop requesting grok-4-7-0907 and use a live assigned model again (currently documented flagship is grok-4.6). I cannot change the model myself. Official docs say Cursor manages model selection and there is no model picker.

Operating System

MacOS

Version Information

  • App: Grok Bot for macOS
  • Grok Bot version: v0.44.0
  • macOS version: macOS 26.6.2
  • Chip: M1 Max - 64 GB RAM - 3 TB of SSD Available

For AI issues: add Request ID with privacy disabled

21c255ea-ee3c-4076-aea1-645e0054a3bd

Does this stop you from using Cursor

No

5

Looks like this has resolved on its own.

6

Hey, thanks for the detailed report, and you were right to dig into it and confirm it wasn’t a corrupt local install.

You didn’t do anything wrong here, and there was nothing to fix locally. For about 20 minutes earlier today, a change to the model configuration on our side caused Grok Bot to return this error on Mac, iOS, and Android: Model name is not valid: "grok-4-7-0907". Your Request ID confirms all the failed messages landed exactly in that window, so quitting, signing out, and creating a new Bot wouldn’t have helped at the time.

It’s all restored now, which matches what you’re seeing. If you run into the error again, send a new Request ID and the send time, and we’ll look into it right away.