looks fixed from my end! thank you ..
From my POV, perhaps that feature was meant to manage latency / resource use? once it was gone, quality increased dramatically with longer chat convos, but the longer the chat convo, performance degrades a bit. A simple restart of cursor works to fix the performance issues of long convos. but TBH i prefer optimizing for quality than performance. So im totally ok with a little lag as long as code completion remains accurate! just my thoughts
the feature is back! ughh why
I have had this issue after updating for previous updates actually, not sure if this is a one time issue or something that can occur after any update.
Your conversation is too long. Please try creating a new conversation or shortening your messages.
keeps appearing on every second chat, I have updated to latest version but issue persist
d7371a79-b7b7-441f-82b6-5651cec40e4c
Same issue, what is the ETA for the fix? This is making cursor unusable.
Hope to have improvements out today. Apologies again.
Hi @new_mik there were some degradations on Sonnet 4 today which could have caused the issue but should be improved now.
i also have been getting this message it only happned the past day ago when this started to occure which suggest this is Purely cursor back end Issue can you please fix this.. its one every conversation I’m getting now, no matter how big, new, old, or whatever. It happens literally after 30 seconds or so after posting the message, and AI gets halfway through, and boom, the conversation is too long. This was not a issue last week or week before and I have been doing everything the same, not touching any settings; everything is default… this does not happen if I select Claude-4, but I have used up all my Claude-4 stuff, so I am forced to use Auto.
getting this constantly today closing all chat windows restarting cursor. never had this issues once before.
“Your conversation is too long. Please try creating a new conversation or shortening your messages.”
Dear Cursor,
You have to understand how annoying this is to deal with while working on complex situations. I now have to make sure task are writen out in advance because the agent will stop in the middle of the work which leads to more bugs. The last couple of releases seem to have lead to more bugs.
ps. cursor is amazing please have your team work on error and bug handling and this weird message.
Hey, you might be adding too much context. This can also happen if you have a large file open in Cursor, even if it’s not in the context. Try closing it or switch to another one. Also, if you have MCP servers enabled, try disabling some that aren’t needed right now.
Can rules contribute to this as well?
Yes, the rules too, especially if they always apply.
Can you provide a tooltip to let us know what is occupying the context?
Cursor has limited window lenght, which shares context accross messages. So a limitation cursor set is to restart as to force you to redundantly share context as it burns more.
Same with the 25 action limitation. Why stop at 25 ? Well. Money.
Thanks for the feedback. We are actually working on extending the limits based on user requests. Several of the improvements will be in 1.4
This would be fine (if slightly annoying) if it turned up BETWEEN messages, but it seems Cursor will just randomly stop a response halfway through with this! Resulting in inconsistent state of the codebase, especially when it’s been doing a fairly large task autonomously…
If you want conversations to be shorter, perhaps allow ‘Start new thread with summary’ to be invoked from the new ‘amount of context used’ guage (since clicking on it does nothing), so we can do it at a natural stopping point? Or perhaps add a ‘switch to max mode’ button which does that and sets the current model to whatever is relevant?
Looking forward for this. For a long iterative task like unit test or TDD, it’s very easy to hit this threshold.
Agreed. Stopping half way really mess the code a lot. Hopefully Cursor at least find a way to avoid those kind of half cooked code
