Still happening for me; just update the new version and run into this problem. Any way to workaround? I got this error when running the command using mcp get jira ticket
This bug will actually make me leave the product. after starting numerous threads, I am not able to complete a simple task of creating a new svg file…restarted my computer multiple times and still running in to the same issue! SMH
I start seeing this your conversation is too long! I never saw this bug before now it’s so so annoying i’m planning to leave cursor for windsurf they might have a better solution to this
1 Like
Cursor is completely useless to me on any version after .46.11 until this gets fixed. And I can’t turn off auto update. I’m really freaking annoyed and I’m about to fork my own version that has auto-update turned off!
me either, I see this message alrady two last days: Your conversation is too long. Please try creating a new conversation or shortening your messages. Cursor is uselless with i, not possible to use it. I tried to delete cursor and install it, removed chat history, but it doesn’t help. Useless, but I already switched to Windsurf, better now. Also using Trae.Ai also good replacement and it’s free
With the current resurgence of this issue I’ve had to rely on Cursor’s (questionable quality) summary + multiple screenshots of recent conversation.
Because the timing is never acceptable and not at all related to conversation length anymore.
I mean, honestly, stopping the entire process mid-tool call interrupts a critical process then denying us the ability to even have cursor update a .md backlog…
Hey! Thanks for the ping. I’ve been seeing the same thing the last couple of days too. My best guess (don’t forget I’m just an end user like you, not an employee) is that this isn’t an issue with the IDE app itself, nor with the length of the chat as a whole. It’s coming from the back end refusing to handle the size of the context on the prompt.
The longer the chat the greater chance of there being lots of relevant info to include, hence the loose correlation with total conversation length.
I’ve had success several times by just backtracking one prompt, slightly rewording it to result in a different context being sent, and continuing several more rounds (YMMV).
Sometimes this may be down to subtle “improvements” to the LLMs themselves that slightly move the goalposts in terms of total supported message size.
I’ll make sure the folks at Cursor HQ are aware though.
Please fix this. This is making it unworkable. I can’t imagine this not being one of the most important fixes at the moment.
The “conversation too long” is like a death popup I had to deal with multiple times already. You just never know when it pops up. You can’t prepare for it and nor should you.
To think this was an issue in the past and it’s resurfacing makes me question how the cursor team is checking their updates. Is there anything in place that checks for past known issues or is it rolled out as it comes?
3 Likes
1000% agree, this is ridiculous. In the middle of fixing something, it pops up, and is a death call, I spend 1/2 of the next conversation limit getting back to where I was? Give me a warning or something. Totally unnecessary.
Since yesterday I constantly run into this error.
1 Like
Well I found the workaround.
Back up the conversation by one (use that handly + sign when you click the left rail). Swap to “Auto”
Have the process resume/continue.
Run that way until it does something highly stupid
Flip back over to 3.7 max, which you’re probably using if you see this a lot.
Get through the hard part.
Set back to auto.
Cursor is just hitting it’s context limit becuase 3.7 Max is so data/context heavy.
I encountered the same issue: “Your conversation is too long. Please try creating a new conversation or shortening your messages.”
In my case, it happened when querying Figma MCP information, as the data returned was too large.
To solve this, I downloaded the Figma metadata as a .json file and referred only to the necessary parts.
Similarly, in other cases where this issue occurs, breaking the results into smaller pieces and requesting to reference them part by part resolved the problem.
cursor version: 버전: 0.47.8 커밋: 1.96.2
1 Like
I’m also getting it. I was trying to setup an MCP for Unity. Now the moment I mention anything to do with Unity, I get this message and it never resets on new chats. I literally can’t use it with Unity anymore
2 Likes
Same issue here.
I was trying to setup an MCP for Figma.
This warning stop me.
cursor version: 0.48.7
1 Like
I’m having the same issue, trying to use Figma MPC. Any component with more than a couple of nested frames gives “Your conversation is too long” error.
This is on a fresh conversation, only passing 1 (small) file for context.
Is there a way to see the logs of how long a given request is?
Using v0.48.7
Same issue for myself as well 
Its making this unusable for me currently.
V0.48.7
I’m experiencing the same issue, despite requesting a completely new conversation and confirming that I still had available credit. I’ve updated to the latest version, but I’m still encountering this problem. I don’t understand what’s causing it, as everything was working fine until now
Same here, the issue still persist. Occur when using MCP
Maybe you have too many MCP servers enabled. Try disabling the ones you don’t need at the moment. I also hope we’ll release an update soon where you can disable individual MCP server tools, which I think will help in the future.