In one specific project, Cursor displays a persistent “message too long” error for all conversations, including brand-new ones.
Restarting Cursor does not resolve the issue. Other projects are not affected.
Steps to Reproduce
In the Review interface, use “Find issue” to locate a problem.
Click “Fix it”, then run the generated fix.
The run immediately fills the entire context window (even though only ~20% was previously used), triggering an automatic summarize action.
The issue remains unfixed because Cursor seemingly ignored the identified problem.
After this point:
Opening a new conversation (any model) still results in “message too long”.
The error occurs even when sending extremely short messages.
Expected Behavior
Running “Fix it” should only use reasonable context and should not corrupt the project’s conversation state.
Opening new conversations should reset the context and not inherit errors from previous tasks.
“Message too long” should only appear when the input actually exceeds size limits.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
That message is too long is on all models. I’ve found a way to get around it, tell Cursor to check the folder e.g. Temp which contains a file called 123blah.whatever and it will check the file, regardless of length. The length could be 100 pages and it will still check it.
I often place files in that folder and tell cursor to examine the files or take code from those files and place them in other files.
I don’t think it’s “context” problem. I’ve been using cursor for this project for months and it worked well. As I remember this problems exist mainly in last few weeks.
