Grok 3 - Mini - Beta is not working

Thanks for reporting a bug you have found in Cursor!
Please add the following info to help us diagnose your issue:
:white_check_mark: Yes I have checked
:lady_beetle: Grok 3 mini beta is not working. I am not on a VPN and have good connection.
:counterclockwise_arrows_button: Just try and use the model and i get an error.
:camera: Screen shot has been attached

:laptop: I am using a MacbookPro 2019 and here are the version details:
Cursor Version: 0.49.6

VSCode Version: 1.96.2

Commit: 0781e811de386a0c5bcb07ceb259df8ff8246a50

Date: 2025-04-25T05:07:16.071Z (3 wks ago)

Electron: 34.3.4

Chromium: 132.0.6834.210

Node.js: 20.18.3

V8: 13.2.152.41-electron.0

OS: Darwin arm64 24.3.0
:prohibited: Yes it will because i want to use this model over the other models.

2 Likes

Same here. It has been failing for me consistently for the last three days. Mini and full-sized versions. When is this going to be fixed?

Version: 0.50.5
VSCode Version: 1.96.2
Commit: 96e5b01ca25f8fbd4c4c10bc69b15f6228c80770
Date: 2025-05-18T04:14:41.252Z
Electron: 34.3.4
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0

1 Like

I have this issue too. Same with grok-3-beta

1 Like

2380ce3f-b5af-40f5-9718-67df10c22507

1 Like

I’ll add my voice here, too. 39380c6d-a122-4244-a189-f406365b0213

1 Like

I tried again today and it still isn’t working.

I have the same issue too. Any updates?

1 Like

+1 Same error, tried clearing app data, disabled http2 and still

and after following all steps shared by Cursor support , i am getting this weird error, in-spite of pro subscription , i am getting this error.

The Grok 3 mini beta has been updated to Grok 3 mini. You can select Grok 3 mini in the model selection and delete Grok 3 mini beta, which is no longer proxied by cursor now.

Thank you. Confirmed working now.

Really? I’m still getting an error with grok-3-mini. It just doesn’t show anything.

gets stuck here after that:

Hey, do you have any MCP servers currently enabled? Try disabling them to see if one might be interfering with Grok’s response. I’ve previously noticed that MCP Firecrawl can sometimes disrupt Grok’s functionality.

It’s still documented as supported a week later.