Whenever I am prompting something in composer, it is stuck in saying “Generating”. I tried to cancel and change the model, the issue persists. It has been a couple of days.
When I am checking Help ->Toggle Developer Tools → Console, there are hundreds of thousands of errors and they keep increasing. They are saying “Error on Ai response”. I am not sure if they are related to this. AI chat is working just fine though. My project progress has been stalled.
Just a thought, have you tried creating a new Composer session and using that?
Anecdotal at the moment only, but I noticed recently that when Anthropic had issues, I seemed to have Composer sessions get into a bad state where they’d stick on “Generating…” after the API failure. It would stay that way from then on, even when trying to choose non-Anthropic models.
Creating a fresh Composer session seemed to unstick it for me. Might be something different for you, but worth a try if you haven’t already.
Thank you for your suggestion. It worked for a new session. But the whole context window/history is gone. So it is like investing double time for the same task.
Yeah, definitely an awkward workaround at this stage, not a proper fix.
For what it’s worth, I did manage to get back to where I’d been pretty quickly by copying some of the most recent context from the ‘dead’ Composer session, mostly the model’s responses. That along with some standard “read the project description and read the code before you do anything” boilerplate got me going again.
But you’re right, it’s certainly frustrating, so I hope they can get to the bottom of it ASAP. Good luck with your new session(s)!
I’ve been having trouble with Cursor Composer for about the last 12 hours. No matter what I type or which model I choose, it just stays in “generating” mode and never gives me an answer. It happens with all the models. I’m wondering if it’s a general problem with Cursor. Are you having the same issue?
Yes, I’ve tried that. It’s working very slowly in the new session, and only sometimes gives me a response. But even when it does, the changes aren’t being applied to the files.
I’m experiencing the same problem since yesterday 12/9/24. I purchase more fast requests once I reached 500 but now the system is not responding at all.
I tried a new composer and started working properly.
yep I have the same issue… i have lost about 40 hours of work though… emailed customer service … and i think I had an AI email me back … even my AI told me i should get my money back … so far … the chat history option is really a joke you can lose data … and then you are FUCKED … good luck to you all … save you convo history
IMO the issue is related to a “time limit” to the Composer sessions (how long a Composer session can be active). I think Cursor developers should be more transparent about a lot of these decisions and strategies.
