I started using the new update today and, while I appreciate some of the changes, I’m fairly disappointed overall. Here’s my detailed feedback:
What I Like
The cleaner UI and the idea of having the composer as a side panel. These are solid improvements that enhance usability conceptually.
Major Issues
“Add Files to Composer” Feature Removed
The removal of this feature is a significant setback. Previously, I could select multiple files in the file explorer, right-click, and add them all to the composer at once. Now, this functionality is gone, making the workflow far less efficient for large projects.
Decreased Output Quality and Performance
The output quality has noticeably dropped compared to the previous version. The composer takes much longer to process files, and debugging tasks seem to drag indefinitely.
The agent feels slow and unresponsive. Compared to Windsurf, there’s a clear lack of flow and reliability. While I valued Cursor for its superior output quality and was okay with longer processing times, the current experience doesn’t justify the wait—often resulting in the agent getting stuck or providing lackluster results.
Tedious Context Management
For advanced projects with large schemas and backends, adding context file by file is time-consuming. When the chat history gets too long and I need to reload the composer for better performance, I must re-add all the context manually.
This is an area where Windsurf excels—its ability to find and handle context more seamlessly when the provided inputs are insufficient is a game-changer.
Overall Impression
The latest update feels like a downgrade in terms of usability and performance. While the visual improvements are welcome, the loss of essential functionality and decline in reliability are frustrating. I would definitely hope for more ideas regarding transfering already existing context to a new chat as well (like an option to save context you provided for a new session).
That said, I remain optimistic about your work. I’ve always appreciated the Cursor team’s efforts and hope to see these issues addressed in future updates.
I’m noticing similar issues on my end and yes please bring back the add files feature. Composer is the killer feature of this application and should be enhanced not degraded. Thank you!
The new feature suggesting files to add to the context is completely frustrating. Not only does it suggest random files without any logic, but they also look identical to the ones I actually added. This made me believe that files I didn’t want were being transferred.
Could you please provide an option in the settings to disable this feature?
After the recent “improvements,” I’m seriously considering switching to alternative solutions from competitors. Please fix this as soon as possible!
When clicking on “apply” in suggested code in the composer, it used to immediately open the relevant file. Not anymore after this upgrade. Now I have to go to the file explorer, find the file and click on it to open it so I can see the suggested changes. Or find it in the open file tabs.
That’s a SERIOUS loss of functionality which makes using cursor more annoying than helpful!
Am I the only one with this problem?
2: changed keybindings
After this update, which I was initially not even aware of, some shortcuts suddenly didn’t work anymore. Ctrl-shift-K for example, which I normally use for deleting a line of code, suddenly made me jump to the cursor composer window! I had no idea why all kinds of strange behavior suddenly occurred, until I realized cursor had been updated!
I never even got asked if I wanted to update, and I didn’t get a notification or anything either. I just suddenly noticed that everything had changed! And NOT in a good way!
There also doesn’t seem to be a setting in the cursor preferences for specifying if I want to update automatically or not.
Suggestion: If you’re going to push radical changes to how cursor works, and the update will be activated automatically, then please at least give people some kind of warning, so they know about it.
I am experiencing similar issues after updating to version 0.43, just as @Voskesss described here.
I’m also having problems applying changes to files when using it through Chat, similar to what @poltje described.
It seems the ‘temperature’ parameter of the Chat API has increased. The models are now more prone to hallucinations, which significantly hinders the generation of usable code through Chat.
I have been a power user of Cursor for over a year, contracting and using 1.5k fast completions per month. I am confident that the parameters of the Chat API have changed and, for my use case, worsened.