Hi, thanks for reporting an issue with Cursor.
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
Basically no matter which one you use (mostly Composer lately in agent mode) the conversation gets stuck after a while (maybe 30-40 messages or 30 minutes, see the screenshot for the looks of it). After going back and forth, you send the next prompt and there will be no answer. It is just stuck. The little dots “…” keep animating, indicating that an answer is in the making but it is over at that point. You can restart cursor/computer and it is still stuck - even if you send another test message it just keeps implying there will be an answer soon, but there never is and this is on a Pro account with like only 20 % of the premium used at this point. I feel like there is a glass barrier at like 1200 characters sent/received, which in it self would really ■■■■ especially if I still have premium answers left and even then I would rather get the slow version with wait time then just not being able to continue.
And if this really is the whish of the cursor team to have some sort of barrier (which I really hope there won’t be because it somehow kills a big portion of the appeal), I at least would want to have the option for a pop-up or some sort of link to start a new composer and have the new composer now a rundown of what the intention of the project is, which technology is used, which features have been implemented and which are still to be done and which bugs have occured and have been solved and which still need to be solved.
And ideally after that, a whole rundown of the structure and in the best case a quick read through of all the files and dependencies. So that I dont have to start at 0 with a new composer. Because if the devs really want this glass barrier then at least i dont have to take up 30% of my new chat budget with explaining what the old composer already new.
Steps to Reproduce
As I said it just happens after a while - I can’t tell if it’s character based or prompt count based.
And by the way: this has happened in all my projects in the last couple weeks/months and has always been a mood killer.
Expected Behavior
I really hope that the devs don’t aim to have this glass barrier in the product. Especially for pro users.
I would rather even if there is some sort of barrrier have slow responses than none at all or the option to get a pop up that I have reached my limit and then be asked if I wish to start a new composer/chat with the core information of what happened in the last one (where we started off, where we were heading, and what was still do be dont to get there with the tech stack at hand).
But again, just let the composer/chat go on and if you somehow really really need to have this barrier then give these slow responses or with the queue and then if people are too eager, let them have the option of these linked chats/composers that transcend the core infromation needed to keep on working.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
0.44.8 - x64
Additional Information
There is really no additionall info. I am working with Docker but I don’t think that adds to the equation.
I would just really love to get first and foremost the answer if this is really something that is intentional and if it is, that is really sad and makes me want to at least try other solutions,
but then at least there are more elegant ways of handling this (like i said, the linked chats/composers so that the first one gives the core information to the next one).
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor
