Thor
January 7, 2025, 1:48pm
1
Hi, thanks for reporting an issue with Cursor.
Before you report this, we’d appreciate if you can search this forum to see if this issue has already been reported.
If you have done so, please check this box.
on
Describe the Bug
Composer very frequently does not produce an answer when prompted.
[composer] Error in AI response: ConnectError: [resource_exhausted] Error
[composer] Failed to get complete AI response
(See the attached debug console screenshot for more details)
Steps to Reproduce
I just use the Composer.
Expected Behavior
I like it when it answers.
Screenshots / Screen Recordings
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 0.44.11
VSCode Version: 1.93.1
Commit: fe574d0820377383143b2ea26aa6ae28b3425220
Date: 2025-01-03T07:59:06.361Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.26100
Additional Information
Not much more to say. Sometimes it seems to help when I restart Cursor, but I dont know.
Does this stop you from using Cursor
Yes - Cursor is unusable
Experiencing the exact same thing on macos 15.3.
Version: 0.44.11
VSCode Version: 1.93.1
Commit: fe574d0820377383143b2ea26aa6ae28b3425220
Date: 2025-01-03T07:59:06.361Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 24.3.0
Submitting any request to the agent is a crapshoot. Sometimes you get a response, sometimes it generates forever and kicks back to the textarea. Looking at the console in devtools shows the exact same “Error in AI response” resource_exhausted type errors.
1 Like
Experiencing same thing on MacOS 14.6.1
Version: 0.44.11
VSCode Version: 1.93.1
Commit: fe574d0820377383143b2ea26aa6ae28b3425220
Date: 2025-01-03T07:59:06.361Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 23.6.0
jorve
January 8, 2025, 1:31am
5
I would lovea video about that because i have that problem pretty much every day
that would be helpful as a short term fix. I’ve been restarting the app regularly, and when that doesn’t work I start a new composer… but that seems like a pretty poor workaround. maybe your method removes some of that pain?