Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Context:
I am currently in a production environment with tight deadlines. I have had to switch to a personal OpenAI API key to continue working, but I would like my account state fixed so I can return to using my included credits.
Ironically I was considering moving to Cursor pro because up until a few days ago I was able to use Cursor AI chat without issue. This problem causes me to reconsider that decision.
Environment:
- OS: Ubuntu 24.04 LTS
- Cursor Version: 2.2.43
- Installation Type: apt install / .deb
Description:
My built-in Cursor AI chat has stopped responding entirely. When a prompt is sent, the UI remains blank or returns immediately without a response. The Developer Console confirms a ConnectError: [resource_exhausted] error.
However, my dashboard shows that I have not hit my limits. I am currently on a Free plan with approximately $20 in credit and only $3.00 in actual usage.
Steps Taken (To avoid redundant troubleshooting):
- Account Refresh: Logged out and back into the IDE.
- Protocol: Disabled HTTP/2 in settings.
- System: Rebooted machine and restarted Cursor multiple times.
- Networking: Verified
api2.cursor.shis reachable. - Verified Connections: Using Cursor’s network diagnostics
- Isolation Test: External AI extensions (Claude) are working perfectly in the same environment, indicating this is specific to Cursor’s internal API handler.
- Logged out and back in - no change
- Cleared out ~/.config/Cursor/User/globalStorage/state.vscdb and recreated - no change
- Rebooted my machine - for those of you in IT
Log Trace / Request ID:
(anonymous) @ workbench.desktop.main.js:10010
workbench.desktop.main.js:13074 [composer] Error in AI response ConnectError: [resource_exhausted] Error
at szc.$endAiConnectTransportReportError (workbench.desktop.main.js:12375:456006)
at xBo._doInvokeHandler (workbench.desktop.main.js:13027:22831)
at xBo._invokeHandler (workbench.desktop.main.js:13027:22573)
at xBo._receiveRequest (workbench.desktop.main.js:13027:21335)
at xBo._receiveOneMessage (workbench.desktop.main.js:13027:20152)
at zLt.value (workbench.desktop.main.js:13027:18244)
at Ee._deliver (workbench.desktop.main.js:49:2962)
at Ee.fire (workbench.desktop.main.js:49:3283)
at Tvt.fire (workbench.desktop.main.js:12360:12156)
at MessagePort.<anonymous> (workbench.desktop.main.js:15027:18433) {arch: 'x64', platform: 'linux', channel: 'stable', client_version: '2.2.43', requestId: '97379bad-6f59-4ed0-ad67-a8f76874e03d', …}
Request ID: 97379bad-6f59-4ed0-ad67-a8f76874e03d
Steps to Reproduce
Start Cursor.
Type ANYTHING into the Cursor AI chat window.
Select ANY model / automatic, ANY type of chat (Agent, Ask, etc)
Results: NOTHING. No error message. Console logs show false positive resource_exhausted error
Expected Behavior
Well… I expect Cursor AI to work.
At the barest minimum, I expect some kind of error message, hopefully an informative one.
Operating System
Linux
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.2.43
VSCode Version: 1.105.1
Commit: 32cfbe848b35d9eb320980195985450f244b3030
Date: 2025-12-19T06:06:44.644Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Linux x64 6.14.0-37-generic
For AI issues: which model did you use?
ALL MODELS including Auto
For AI issues: add Request ID with privacy disabled
97379bad-6f59-4ed0-ad67-a8f76874e03d
Additional Information
Note: my chat prompt was “ping”.
Does this stop you from using Cursor
Yes, at least the AI aspects (which is the only reason to use Cursor instead of vscode)
