Switching from the “Cursor Grok” model worked for me.
Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
I’m frequently encountering a “High Load” error in Cursor that prevents requests from being processed.
Steps to Reproduce
any interact with Auto Agent
Screenshots / Screen Recordings
Operating System
Windows 10/11
Version Information
Version: 3.11.25 (user setup)
VS Code Extension API: 1.125.0
Commit: fc2563ec93d793fc275eef734405a4fdf8b47b20
Date: 2026-07-15T01:27:41.754Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26100
Does this stop you from using Cursor
Yes - Cursor is unusable
Where does the bug appear (feature/product)?
Somewhere else…
Describe the Bug
Request ID: 3f1468a5-44eb-44df-9d7d-b185752badad
{“error”:“ERROR_RESOURCE_EXHAUSTED”,“details”:{“title”:“High Load”,“detail”:“We’re experiencing high demand for Cursor Grok 4.5 right now. Please switch to Auto, another model, or try again in a few moments.”,“isRetryable”:true,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
We’re experiencing high demand for Cursor Grok 4.5 right now. Please switch to Auto, another model, or try again in a few moments.
[resource_exhausted] Error
RetriableError: [resource_exhausted] Error
at NVv (vscode-file://vscode-app/c:/Users/52936/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9157:6675)
at PAr (vscode-file://vscode-app/c:/Users/52936/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9157:5410)
at qgm (vscode-file://vscode-app/c:/Users/52936/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9158:11974)
at Object.classify (vscode-file://vscode-app/c:/Users/52936/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9158:16506)
at OVv (vscode-file://vscode-app/c:/Users/52936/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9158:5856)
at async c4a.runWithSharedTurnRunner (vscode-file://vscode-app/c:/Users/52936/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9158:15858)
at async Bq.runAgentLoop (vscode-file://vscode-app/c:/Users/52936/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:20122:3005)
at async _hl.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/52936/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:20182:14344)
at async _hl.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/52936/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:20182:23914)
at async ZBe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/52936/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9328:2476)
Steps to Reproduce
just start a task, and wait, and it happens really a lot
Operating System
Windows 10/11
Version Information
Version: 3.11.25 (user setup)
VS Code Extension API: 1.125.0
Commit: fc2563ec93d793fc275eef734405a4fdf8b47b20
Date: 2026-07-15T01:27:41.754Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.19045
Does this stop you from using Cursor
Yes - Cursor is unusable
same
Its on AUTO mode and also on GROK 4.5
Same issue facing - We’re experiencing high demand right now. Please try again in a few moments.
same issue, any solution for this
-> mode: auto
Request ID: 98af9a03-9d5b-4ec8-adc4-521b49a7a27b
{“error”:“ERROR_RESOURCE_EXHAUSTED”,“details”:{“title”:“Unable to reach the model provider”,“detail”:“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
[resource_exhausted] Error
RetriableError: [resource_exhausted] Error
at k_f (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9155:6669)
at pQi (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9155:5404)
at wfp (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9156:11972)
at Object.classify (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9156:16501)
at T_f (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9156:5856)
at async Dzo.runWithSharedTurnRunner (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9156:15853)
at async $z.resume (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:20557:7462)
at async ewa.streamFromAgentBackend (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:20585:14348)
at async ewa.getAgentStreamResponse (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:20585:23920)
at async aDe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9322:2475)
same issue +1
@deanrie, when will this issue be fixed? It’s been blocking my work for about 2 hours. Could you please look into it and fix it as soon as possible? Thanks!
same, so sad, I do not know how to solve it
same issue
same
same
Hey everyone, this is a temporary high-demand throttle on our side, and we’re already investigating the incident. There’s a traffic spike right now, so requests via Auto and Cursor Grok 4.5 are hitting capacity and returning “High Load”.
What helps right now:
- Switch from Auto to a specific model. A few users in the thread said Composer 2.5 (or another named model) works.
I’ll post in the thread if there’s an update. Let me know if switching models helped.
same issue for last 30 min with auto model.
We’re experiencing high demand right now. Please try again in a few moments.
same issue 
same
lol