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
I’ve been using Cursor Agent and Chat for a few weeks and today (17th of December) Cursor Agent started saying “Generating…” indefinitely. I let it run for a few minutes before realising that it was never going to finish.
So I simply used “Chat” for the day to do my work. Then at around 15:30 (UK time), Chat also started behaving the same way and now I can’t generate anything.
Both Chat and Composer both just say “Generating…” whenever asked anything. It’s not saying I’ve run out of credits, or that I don’t have access to the internet. So I have no idea what it could be.
Steps to Reproduce
Try typing anything into Chat or Composer
Expected Behavior
It should respond
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
To resolve this issue, you can try starting a new session by clicking the + icon at the top. We’ve also released version 0.44, which fixes this. You can read about the update here:
I also updated to 0.44 thinking it was going to solve the ‘generating forever’ bug but Ive had several instances today where the generations have stopped working-- sometimes I restart and it starts generating then. Its making cursor a miserable experience / unusable. I keep having to retry retry retry to get it to start and when it does it starts streaming immediately. I bought extra fast requests too/ still no joy.
I personally wouldn’t do any work with it where you need agent composer to work or expect it to finish reliably— I’ve heard someone say it only affects agent mode but I havent tried regular composer or chat enough yet to confirm.
it definitely affects agent mode - 0.44 still doing the same thing. i did have a bit better result using normal composer mode but it makes the workflow much more difficult for me after using agent mode…was really hoping this update would have addressed it
Thanks @rishabhy for the help. On my end the new 0.44.2 Cursor resolved the issue. Also in the older 0.43 version, I can start a new composer (by clicking the [CMD N +] button) to get around it.
