still happening
If you’re seeing this happen, the most helpful thing you can do is to share with them the information about your stalled request:
Troubleshooting this ‘in the dark’ is undoubtedly very difficult, since it’s only affecting a limited number of users. If you’re one of them, you can help enormously with just those few simple steps.
So sorry to hear you’ve been so unlucky right out of the gate. While I’m not a Cursor employee, I have been a user for well over a year, and I know how frustrating it can be when things aren’t right first time.
It’s a fast-moving product in very active development, and on rare occasions there are temporary bumps like this along the way. I know the dev team are doing their very best to track down anything that can trigger this issue right now.
It’s a hard problem, because it only affects a limited number of users, so they’re reliant on user reports to dig into. Of those affected, plenty are saying “it’s still there” but hardly any have stepped up and shared their request data so far.
Hang in there, I know it’s not ideal, but they’re working flat out to solve the issue once and for all. From experience, it’ll be worth the wait.
Im noticing that composer is breaking (twice in a row now) dealing with this type of input:
Parse error: syntax error, unexpected identifier “subject”, expecting “,” or “;” in C:\todo.php on line 362
I have submitted a report per your instructions. For me the stopping seems to mostly occur when running terminal commands that have large-ish output. Today I have the problem immediately in a new session if I have the composer, in agent mode, run a script that has a long json output. In the terminlal window I can see just the first several lines out output from the script and then many blank lines that seem to represent the rest of the expected output but the lines are all blank. And then it seems as though the composer stops, waiting on the terminal output, but it’s mostly blank, so composer just waits forever. I hope this makes sense and somehow helps resolve the problem. I would love to try a previous version but I can’t find prior version downloads.
I’m using Cursor in windows 11 with claude 3.5 sonnett.
Thanks @AMIAI! Really appreciate you taking the time to report the issue directly in the IDE, that’ll be really helpful for them.
That’s some interesting detail too. I wonder if that might be something slightly different. Do you get it stuck on ‘Generating…’ or do you mean it stalls at the end of the tool script?
Here is a screenshot (I hope, new to this forum). I have a “Cancel and resume” button. There is an animated whirly at the bottom right of the inset terminal window (next to the terminal window’s cancel button)
I have had what appears to be the same problem when composer is running other terminal commands (git commands, parsing other script results like unit tests, etc…). Only some of the output visible (if I scroll up in the terminal) but then many blank lines and composer just waiting for it to finish. If I click cancel and resume, it might think the few lines it saw at the top was what it was expecting and continue on, or in the case of my test script here, it will recognize that what it saw was a truncated response. This has been intermittent up until today where it happens right out of the gate when running this specific script that has a long json output. I will try a few things, like a new fresh start in a new project folder with just a test script, no cursorrules, etc. and see if I can reproduce.
Edit: That cursor box in the middle of the terminal window was left over from me clicking in it and scrolling up to see the first few lines of output followed by the many blank lines. In the screenshot I had scrolled back down so only see the blank lines.
1 Like
Not sure if this is just a coincidence (probaly) but my cursor has been working much more reliably the last couple days, which corresponds to me maxing out my 500 fast requests. Now by default all my requests are slow requests.
I’ve also gotten in the habit of having cursor create a agentcontext.md file and update it every once in a while to retain the current context in the event I do need to start a new composer window. Then I can have the new composer window read in that context summary to easy the transition to a new session.
1 Like
Issue
Some users experience the Composer stalling on “Generating…” after submitting prompts, especially during long conversations. This is the primary focus of this thread. For unrelated issues, please create a new topic or email hi@cursor.com.
Workarounds
- Partial: Starting a new Composer session may help, though it requires re-populating your conversation context.
- Unconfirmed: Some users report success by rolling back to a previous checkpoint in the conversation, or by retrying the same request.
If you discover other effective workarounds, please share them here.
Current Status
The development team is prioritizing this issue. They’ve addressed some triggers, reducing occurrences for some users, but continue to investigate the root cause. Troubleshooting is challenging due to the issue’s sporadic nature, so user-reported details are crucial.
How to Help
If you encounter this issue, please follow these steps: Reporting an issue with a request
Additionally, share any relevant details about your project (e.g., source file sizes, codebase size, conversation length, use of image attachments, terminal commands, checkpoint rollbacks etc.). A few more detailed reports from users could significantly speed up resolution. Thanks for your patience!
Who is @three?
Not a Cursor employee, just an end user like you (so please don’t shoot the messenger! 
).
1 Like
Any updates on the resolution for this?
The frequency of it seems to be significantly down now. I’ve seen a ‘stuck’ on an Apply by the agent, but after hitting Cancel and then prompting ‘please continue’ it worked fine again, so that’s not the same perma-stuck Generating we were seeing before, where the session can’t be resumed.
If you’re still seeing sticks that can’t be un-stuck that way, please do follow the steps to share the request ID and some details of the circumstances. (+3000 karma points and a virtual hi-five for anyone who also includes a screen recording of it happening along with the request ID).
Still getting stuck on … in new Composer sessions.
This forum does not allow uploading videos, so imagine this for an hour 
I’m not sure if my issue is different. I don’t think I ever get stuck on the file generating part, it’s always when I initially send a new message (where it says …). I have to resend the message around 3 times before it replies.
It happens even on fresh Composer sessions with only 1 file of context too (to rule out context overload as the issue.)
1 Like
Thanks for sharing, @KamilTheDev!
It’s good to hear that it unsticks after a few tries rather than being permanently stuck, but frustrating that you have to resend it at all. Really useful to know about ruling out context overload, I’ll make sure they’re aware. It’s possible there’s a couple of slightly different things in play here, but I’ll leave it to the dev team’s expertise.
If you find it happening again, could you share the IDs: Reporting an issue with a request
Incidentally, I think you can add videos either by embedding/linking from your favourite video hosting platform, or by converting to a format like webp or even gif, with something like ffmpeg (ChatGPT knows the syntax).
Not an official Cursor animation, just an example I hacked together
Appreciate you taking the time to share the info, thanks.
Hello same with me still stuck here. when generating the code
Could you try following the steps to share the request IDs?
Reporting an issue with a request
Thanks!
just become normal a few minutes ago. but got stuck sometimes
I will report in case happening again later
1 Like
Super Slowdown after long conversations… I was wondering and I think its the size of GlobalStorage…
Can others cheek the size of theirs once you experience UX/UI lag (composer lags like mad on input when my GlobalStorage is >~100MB
FWIW, I’ve been working all day today with no issues. I have a Composer session running now that has been running for many hours without any performance issues. My state.vscdb file has been around 750MB for most of the day. This is on a 2019 MBP with 2.3 GHz 8-Core Intel Core i9 and 64GB of RAM. Maybe worth noting, I don’t think I’ve attached a single image to the Composer in this session.
1 Like
