I think the Cursor team needs to stop worrying about features, and focus full team on bug fixes. There are some DEVASTATING and DEBILITATING bugs right now. Using Cursor on Windows with WSL2 is effectively unusable, due to SEVERE issues with how Cursor interacts with terminals. I reported this over a month ago, had some conversations with a Cursor rep about it, then was ghosted. I ultimately had to have the company I am working for send me a Mac M4 to get moving again, because the issues on windows are SO SEVERE. There are MANY people reporting bugs with terminals in Cursor agent while on Windows (10 or 11) with WSL. Lot of people paying for a product that simply doesnāt work! This is really bad, Cursor Team!
I now have another DEBILITATING issue on Mac, due to every new agent chat throwing a āconversation too longā error immediately. I literally cannot use the agent. I also literally JUST upgraded to the Ultra plan ($200/mo!) just a couple days ago. Iām dead in the water right now. Cursor is UN-USABLE.
I could CARE LESS about features right now. Cursor is in very desperate state right now, with debilitating bugs that literally prevent cursor from being usable. Please stop focusing on features, maybe table the GPT-5 integration for now, and give your PAYING users some attention by fixing bugs that are preventing us from being able to get any value of the significant amount of money we are paying each month for a product, that increasingly, seems to be broken and unusable.
Hey, itās possible that your chat is overloaded with context. Have you tried creating a new one? Or is this happening in a relatively new chat? If so, you might be attaching too many files or folders. Itās also possible that you have multiple MCP servers connected. If youāre using rules, that could also be affecting it.
I have the same thing as @jrista constant āYour conversation is too long. Please try creating a new conversation or shortening your messages.ā in 1.4 - I never had this before and I use a very strict workflow with what I do (same few prompts in a cycle to work through a task list). Now i canāt even get passed one prompt, from a new chat with my spec document attached (only 300 lines long). I have a whole team (enterprise edition) experiencing the same thing. This is starting to get unusable and has rendered it from being my daily driver, to a chore. Pushing me back into just doing it all myself. The last few updates to this app have completely ruined the experience.
It rarely uses to-do lists and when it does it uses them wrong, I get better results with an attached markdown file with a task list in it and simple .cursorrules. Whatās the point of this functionality if it barely works? It adds extra tokens to the context for very little results.
It fails to use mcp tools anymore without explicit instruction, and when it does it uses them wrong a bunch of times before eventually figuring one of them out (usually executing the wrong one because it confused itself). It used to use them really well and I havenāt changed my servers.
It gets caught in loops doing the same prompt over and over again.
It keeps asking me to store memories of memories it should already have or almost identical to previous and things that are already in the .cursorrules so donāt need to be remembered again and fill up the context
It randomly drops files off the context meaning I have to add them back
It always re-adds the active tab to the context which I donāt want it to do.
I use it in editor mode in zen mode but now it constantly opens all files in another side panel.
Constant āconversation is tool longā warnings EVEN when on my first prompt in a new chat with barely any context
Requests take ages to run, tools take ages to execute, responses are massively long and verbose, all of which mean it takes many times longer to do simple things compared to v1.2.x and prior performance
Many more issues which I canāt remember off the top of my head but as a really heavy user of the application my list is getting much longer with each release.
I am assuming these are changes under the hood to reduce the token usage and improve the cost scaling of the product but it is severely gimping the real USP which should be improving code delivery. I would suggest as a business owner myself you survey your customer base more to get better feedback about user experience as it seems you are not aligned with the customer base.
Whatever decisions you are making with the product direction at the moment, they are the wrong direction. You have taken something which was an exciting tool to use to an over-bloated mess with useless additions and gimped main usp functionality. Unless the main agent actually goes back to producing at least passable quality results without all the friction introduced recently then I for sure will be looking at alternatives for my team. Looking around the forums it seems many people want the same things - consistency and results.
@deanrie The problem is not that the chat is overloaded with context. Iāve closed Cursor, restarted it, started a brand new empty chat, removed all default context, given it a prompt, and not even half-way through working that initial prompt right after starting cursor, I get the error about āconversation too long" right away. The agent & llm sometimes only produce a few blocks of output before the error occurs, and sometimes it occurs right in the middle of a file edit.
Iāve worked through this enough now, including multiple full reboots of my Mac M4, that Iām sure there is a bug here. Closing and reopening the app and starting with a fresh chat without context, will instantly run into the āconversation too longā in brand new chats, all of them. If I reboot, then Iāll have a short window of time where I can use the agent before the issue reoccurs. I think it was introduced with 1.4. There is some kind of āleakā of something, that is burning up chat length in a persistent manner.
It is also a progressive issue. It started out relatively infrequent, but as time progressed over the last couple of days, the āconversation too longā issue has progressively become worse and worse. It first started happening a lot with Linear MCP usage, and I thought it was something to do with the MCP. But it happens with any prompt, any chat tab, even with zero context attachments and a very, very simple prompt. Once it reached that point, the only thing that gives me any usage even for a little while is rebooting the computer entirely, but that only works for maybe 20 minutes or so?
This is a SEVERE issue and has stopped me dead in my tracks. I had a bad and busy week last week with other obligations, and I intended to use this weekend to catch up. Instead, the latest round of Cursor Bug releases has brought the agent to a grinding halt and Iāve done nothing but fight with the IDE.
This is a very severe issue, and it really needs some attention from the Cursor dev team ASAP.
On Windows + WSL, Cursor agent is all but unusable due to terminal integration bugs. I reported a LOT of additional information direct to Cursor via a rep for a while a couple weeks ago or so, that is not captured in my bug report thread here on the forums. Sadly, my thread was auto-locked (22 days lock time is a ridiculously short time period when the Cursor team does not even seem to read or respond to bug reports.)
The company I work for sent me one of their Mac M4s, and I was able to switch to that. The terminal integration in the agent works fine on MacOS X. It is specifically Windows+WSL that seems to have the issues, and they are very, very severe as well. I sent a significant amount of information to Cursor via emails, but after the first few days I stopped hearing from them, no further responses via email, and no responses on my (now closed) ticket.
It is frustrating, the number of rather debilitating bugs that seem to exist in Cursor right now, that donāt seem to be getting attention.
Windows + WSL2. Iāve only started noticing with v1.4 that Cursor uses quite a bit of CPU and gets laggy (when typing, etc). This seems like a software issue. Iām on an i9 processor with plenty of capacity. Slowness happens in particular when chat is processing a message from the LLM.
Edit: actually itās now kind-of laggy all the time.
For all new comments here. At this time Cursor 1.5. is stable release version. Please update to that as there are a lot of improvements. Version 1.4.x is no longer receiving updates.
In case you have issues with 1.5.x post a full separate Bug Report with more info Create Bug Report
