I’m encountering a persistent issue with Cursor where a specific composer instance is stuck at the “Generating” stage. This prevents me from continuing work on my project within that specific composer.
Here’s a breakdown of the problem:
Specific Composer Issue: The problem is isolated to one particular composer. If I create a new composer, it functions correctly and generates code as expected. This indicates it’s not a global issue with my Cursor installation or setup.
Tried Solutions: I’ve already tried the following troubleshooting steps without success:
Restarting Cursor
Reinstalling Cursor
Impact: Because the issue is specific to this composer, simply creating a new one isn’t a viable solution. I lose all the context and progress I’ve made within the stuck composer.
No Error Messages: There are no error messages displayed; the composer simply remains stuck at “Generating” indefinitely.
I’m looking for any insights or suggestions on how to resolve this issue and recover my work within the affected composer. Has anyone else experienced this problem? Any help would be greatly appreciated!
Hey… any luck on this yet? I’m still seeing stuck Composer sessions. I’ve just upgraded to 0.44.10; my current session which was stuck in 0.44.9 remains stuck in 0.44.10.
It sits on “generating” for a long time, and then eventually it silently gives up (same in both versions).
It looks like while it’s “Generating” it’s sitting there calling checkQueuePosition over and over, but nothing else fun is happening, and then eventually when it gives up it looks like it’s because:
“error”:“ERROR_MAX_TOKENS”,“details”:{“title”:“Request attempted to use too many tokens.”,“detail”:“Max tokens used”,“isRetryable”:false}
We do have a fix for the main cause of the generating issue that most people were facing, but your issue seems to be something different! I’ve reported this to our team and will get back to you soon hopefully!
Does this happen on a brand new composer, or only on composer session that existed before the upgrade?
Thanks for coming back on this, much appreciated. I’ve not encountered it on a fresh session yet, but I’ll keep a close eye on it and will report back with as much detail as I can if I can reproduce it on the most recent version.
Sounds good, it’s possible this is due to a change between the updates you did, but if you’ve faced this, it’s likely others have too, so we want to resolve this regardless!
Hey @danperks is there any fix yet? I’m a new user, downloaded Version: 0.44.11 and started a project on it. Been using it a couple of days and composer chat window fairly long, and I’m experiencing the same as the users above. I’ve not made any updates to the Cursor version since downloading.
Hey @danperks I went back into the app last night, the screen was a little odd, and then it started deleting my tabs across the top which were all the different files I’d created over the last 3 days. I’ve ended up with this message in the screenshot. Please tell me there is a way to get the info back. Thanks in advance.
Can you confirm, from your screenshot it looks like you are using workspaces over SSH?
While I don’t have a good answer on why the workspace no longer exists, my hope is that you can recreate it and carry on where you left off pretty quickly!
Hi @danperks I’m new to all of this so apologies if I missed important info out. I connected cursor to replit via ssh with all the prompts taking place in cursor and then going into replit to see the front end. Does that make sense?
I was following a tutorial from Riley Brown who, at that point anyway, used cursor composer to create the code as that was far better than replit in his opinion, and connected it to replit as that was better at the connecting to databases (firebase) and deploying the code.
Ah, I see. Not sure on the specific tutorial, but you probably don’t need to set up a whole workspace, but instead just SSH directly into the machine and open the folder the code is stored at in Replit.
My guess is this may be something to do with the Replicit itself as if you pause the project and come back to it at a later stage you’re probably not running it on the same machine and therefore the workspace information is no longer available.
Hey @danperks thanks for the reply. I had a look, and it’s this tutorial. https://www.youtube.com/watch?v=ltdl4yqwBUI I managed to get cursor and replit reconnected, and I can see all the files showing in cursor now. When I try and do more in the composer, it still gives me that original error were speaking about in this thread, the stuck on generating loop.
