This new version actually doesn’t work that well for me.
I have a workspace with both BE and FE repositories for the same app and the agent (“edit” mode) doesn’t understand where to put the changes anymore. Using it made me unproductive.
3 Likes
Is the @terminal feature not mentioned in the “full” changelog?
This version doesn’t work so well…
- Sometime, tab just not working, time to time, the prompt changes already showed up, but hitting tab doesn’t bring the prompt in, instead, it just did what tab key actually do, and bring in a tab and killed the contents selected
- Response is slow, when using CMD+L, the response is slow, compare to before
- AI Response failed time to time
Actually, I heard same complaints from my colleages, the recent updates sucked…
1 Like
Where is the chat with codebase mode? Super annoying…
1 Like
The look and feel is nice but this might be the worst update
1 Like
Guys, you need to maintain a certain standard with your releases. Every single update introduces major changes that break previously working methods, making it unbearable at this point. With every release, I feel cautious because I’m afraid the user experience of Cursor will change so much that I won’t be able to use it effectively anymore.
For example, in this current version, it feels like you are trying to phase out the edit mode—not the agent, but the edit version—which I was using much more efficiently because that’s what I need. Previously, it was possible to tag the codebase, but now this functionality is gone. Additionally, things that used to run smoothly now have many issues, making even simple modifications difficult. This is extremely frustrating to work with.
It’s exhausting to constantly worry about whether something essential will break with every new release. The agent is also not functioning properly, and forcing us to use it instead of the composer/edit mode is not a viable solution. I genuinely love what you guys are building and have been one of your biggest supporters, but these constant drastic changes are significantly disrupting my development process. I can no longer establish a standardized workflow because every update forces a completely different way of working.
Please take a more professional approach to version management and allow users to download previous versions if they prefer. The way you are handling releases is not suitable for a software company with a large user base. Many people use Cursor in different ways, and just because you believe a change is better doesn’t mean it actually improves the experience for your users. I also feel like you’re not gathering enough feedback before rolling out these changes.
A more stable and user-conscious approach would benefit everyone. Frequent, fundamental changes are not sustainable for those who rely on Cursor for their workflow.
2 Likes
0.46 is great! I like the new design. However since the last update I have an extremely annoying bug: [BUG] Terminal tool gets stuck after exit code
I had to revert to version 0.4.5 because it kept applying changes to the wrong file, and the reapply feature was missing. They had a successful UI but decided to follow the Agent hype-train trend found in like a certain Surf application (why can’t we mention it by the way?). I’m not opposed to it, but why disrupt existing workflows? Just add an agent mode without killing all that was good. I also, like the colors more in 0.4.5.
1 Like
Image upload failed, can not parse the image
Eventually had to revert to 0.45 although I like the new UI, 0.46 seems very unstable and inconsistent
Why is there no Linux version of 0.46?
1 Like