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
The Cursor stopped working; it is stuck on the Generating code. I have been getting the same issue for the last three days, and it has only stopped at Generating. It has only been loading for the last three days but is not working.
Yes, it happens to me too (3 times, 2 today), I was told I just had to use ctrl-N, that works too, but it starts a new conversation and then composer loses all files and I don’t know what’s going on and it becomes a mess, furthermore, you should be able to make a narrow list of files for a conversation so you don’t have to start over, it’s quite an annoying problem
This has started happening to me again and i have just downloaded the latest version. I have tried quitting cursor, restarting but no luck. I really don’t want to lose the context of this composer session. It sits on generating and nothing happens. I’m on a Mac.
sorry Dan the notification went to junk. Yes a new composer session does respond but i didn’t want to lose the history. But actually recently the composer seems far more intelligent at spidering existing files to work out what is going on so it’s not as much of an issue now.
Super frustrating. Just started happening today for me. Haven’t been able to get cursor (with sonnet 3.5 or 3.7) to generate any code. It’s stuck on generating.
It is still happening also with 0.46.7 and is definitely not solved. Its confirmed as Cursor IDE not making AI requests while it makes other API requests successfully (subscription check).
While Cursor is otherwise great, this needs to stabilize, its not a toy we can just put aside, its a busines tool and is expected to be more stable. (its not related to any AI models)
Same issue with the Pro.
Developer Tools console shows “[composer] Error getting conversation summary: ConnectError: [invalid_argument] Error”
I can reproduce it everytime that I left the chat idling for a few minutes (usually 2 to 5 minutes, sometimes more), then I speculate that some connection or cache seems to get stale and every subsequent “Send” from the chat gives me that error.
If I reply shortly after the last llm message ended then everything works fine, that means that every time I leave the computer I know that I’ll have to kill Cursor and reopen it when getting back to work. Very annoying.
Happens both on my desktop and laptop, both Cursor version 0.46.11 AppImage on Ubuntu 24.04.
edit: If I could suggest an UX change, maybe optional to keep the UI minimalism, but something that shows the state of the connection/requeset along side the “Generating…” text, so even if it fails, we can know faster that something went wrong, at least I wouldn’t have to open the Developer Tools everytime…
