All grok models do not respond

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

All grok models start “thinking” the three dots appear then the chat or its response fails

2c883c03-7ccb-4b66-989d-892757fa4a1a

this is happening to 100% of the time with grok code fast 1 and grok 4 fast

Steps to Reproduce

Chat with grok code fast

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.40 (system setup)
VSCode Version: 1.99.3
Commit: df79b2380cd32922cad03529b0dc0c946c311850
Date: 2025-10-09T02:55:11.735Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

For AI issues: which model did you use?

grok code fast

For AI issues: add Request ID with privacy disabled

2c883c03-7ccb-4b66-989d-892757fa4a1a

Does this stop you from using Cursor

Yes - Cursor is unusable

2

Hey, thanks for the report. We’ll investigate this.

3

any update on this? all grok requests get errored

4

yeah wtf, no grok models work

5

@deanrie :

image
image1774×437 31.9 KB

[composer.submitChat] Last leg time taken: 18.80000000447035ms
workbench.desktop.main.js:6358 [composer.submitChat] client side ttft: 51ms
workbench.desktop.main.js:7969 [composer] Failed to record usage data: Error: [composer] No AI message found
at pdr.handleUsageData (workbench.desktop.main.js:7969:5502)
(anonymous) @ workbench.desktop.main.js:7969
Promise.catch
onChatStreamFinished @ workbench.desktop.main.js:7969
(anonymous) @ workbench.desktop.main.js:7942
t.value @ workbench.desktop.main.js:7942
r.value @ workbench.desktop.main.js:7942
capabilityFn @ workbench.desktop.main.js:3445
measureCapabilityExecution @ workbench.desktop.main.js:3463
(anonymous) @ workbench.desktop.main.js:3445
runCapabilitiesForProcess @ workbench.desktop.main.js:3445
(anonymous) @ workbench.desktop.main.js:52
Qms @ workbench.desktop.main.js:52
I5 @ workbench.desktop.main.js:52
n.value @ workbench.desktop.main.js:52
submitChatMaybeAbortCurrent @ workbench.desktop.main.js:6359
await in submitChatMaybeAbortCurrent
(anonymous) @ workbench.desktop.main.js:52
Qms @ workbench.desktop.main.js:52
xxu @ workbench.desktop.main.js:52
n.value @ workbench.desktop.main.js:52
ha @ workbench.desktop.main.js:7208
await in ha
(anonymous) @ workbench.desktop.main.js:6677
Xe @ workbench.desktop.main.js:6677
onClick @ workbench.desktop.main.js:6677
(anonymous) @ workbench.desktop.main.js:3511
workbench.desktop.main.js:7991 [composer] on settled was run without a previous ai bubble
onComposerSettled @ workbench.desktop.main.js:7991
(anonymous) @ workbench.desktop.main.js:52
Qms @ workbench.desktop.main.js:52
I5 @ workbench.desktop.main.js:52
n.value @ workbench.desktop.main.js:52
maybeRunOnComposerSettled @ workbench.desktop.main.js:7991
(anonymous) @ workbench.desktop.main.js:52
Qms @ workbench.desktop.main.js:52
I5 @ workbench.desktop.main.js:52
n.value @ workbench.desktop.main.js:52
(anonymous) @ workbench.desktop.main.js:7985
_deliver @ workbench.desktop.main.js:49
fire @ workbench.desktop.main.js:49
fireMaybeRunOnComposerSettled @ workbench.desktop.main.js:590
submitChatMaybeAbortCurrent @ workbench.desktop.main.js:6359
await in submitChatMaybeAbortCurrent
(anonymous) @ workbench.desktop.main.js:52
Qms @ workbench.desktop.main.js:52
xxu @ workbench.desktop.main.js:52
n.value @ workbench.desktop.main.js:52
ha @ workbench.desktop.main.js:7208
await in ha
(anonymous) @ workbench.desktop.main.js:6677
Xe @ workbench.desktop.main.js:6677
onClick @ workbench.desktop.main.js:6677
(anonymous) @ workbench.desktop.main.js:3511
workbench.desktop.main.js:7934 [Explicit context] took 8ms
workbench.desktop.main.js:6368 [composer] Warm submit chat completed

7

Thanks for the extra info. Could you let me know if you’re using any MCP servers? If yes, try disabling them and see if that fixes the issue.

8

yes it fixed. thank you.

9

Hi Deanrie I found this thread as I was having the same issues - Grok models not responding.

I disabled Posthog MCP server and that fixed it. Thanks

1 Like
10

Hi @deanrie, same happening for me. disabling the MCP is only a temporary solution IMO. I want to be able to use Grok with my MCPs

Any update about this?

11

Hey, you’re right that disabling MCP is only a temporary workaround. This is a known compatibility issue that’s been escalated to the engineering team.

I’ll check on the status of the fix.

14

Hi @deanrie,

Any update on this?

This keeps happening to me.