CursorAI 0.46 Issues – Bugs, Workflow Disruptions & Need for Better Support

Bug Reports
1

Hi, CursorAI team (I hope you monitoring your forums) and everyone,

I wanted to share an update regarding the ongoing issues with CursorAI (starting from version 0.46). After testing, I can confirm that reverting to version 0.45 resolves all major problems. Claude 3.5 Sonnet provides the same level of control over the codebase without introducing unnecessary changes. Additionally, version 0.45 does not have the frustrating bug where file edits are blocked, Cursor AI is creating a diff and a script to apply it instead of editing the file—something that has made the experience quite cumbersome.

A few thoughts for the CursorAI team, in case you’re following this discussion:

First and foremost, you’ve built an excellent product and were among the pioneers in this space, which is a remarkable achievement. However, it’s disappointing to see how turbulent things have become since the release of version 0.46. I’m not sure if this is due to internal constraints or resource limitations, but for a commercial product with a relatively high price point, reliability is crucial.

New features are always welcome, but not at the cost of breaking essential workflows. As developers, we rely on CursorAI to be a stable tool that enhances our productivity, not one that forces us to troubleshoot issues that previously didn’t exist. The time spent searching forums and workarounds is frustrating and counterproductive.

To help address these concerns, I strongly recommend:

  1. A Dedicated Support Portal – A structured way to submit support tickets would improve user experience and ensure customers receive timely assistance. Forums are good for community support and free products.

  2. Stronger Quality Assurance (QA) Processes – The current approach to QA appears inconsistent. Whether testing is limited to a small team or an individual, the impact of insufficient testing is evident. Automated testing is an industry standard for a reason, and without it, ongoing issues will likely persist.

  3. Compensation for Disruptions – Given the strict request limits in place, it seems unfair that paying users end up exhausting their quotas just to test and troubleshoot product issues. A refund or credit for affected users—particularly those impacted since the release of version 0.46—would go a long way in maintaining goodwill.

The broader community has expressed similar frustrations, and some users have already started exploring alternative products. While competitors may not yet have the same issues, this should be a wake-up call. Maintaining a leadership position in this space requires both innovation and reliability.

I truly hope the team takes these concerns seriously and implements changes to prevent similar incidents in the future. CursorAI has great potential, but its success ultimately depends on the trust and satisfaction of its users.

Wishing you all the best and looking forward to improvements.

20 Likes
2

Just to add to this. Cursor IDE is a great tool that I use daily and will continue to use. I have noticed a lot of people just saying “we are going to stop use it” who let’s be honest are going to keep using it instead of providing feedback. Remember constructive criticism, not crying.

With that said, I do think the release process needs to be improved. The Cursor team is good at cleaning bugs up to an eventual stable version so I appreciate them for that but is there something happening that is letting unstable versions being released pretty consistently in the first place? I often times find myself waiting for the next hot fix to come out before I can start working with Cursor. I recently discovered how to downgrade so I’ve been dong that instead now.

0.46 seems like an amazing release on paper with all the feature’s and improvement they’ve added and I was excited for it to release and am still excited for it to be stable but since it was so unstable I feel like it’s left a pretty bad taste in people’s mouth.

The main point I want to get across is the Cursor team is amazing with the constant improvement to the IDE. The team is clearly capable of addressing all the issues that come up and I know some things you just might not find untill it’s been deployed but Cursor would be even more amazing if something like 0.46.10 was released as 0.46.0 and then I’d understand if there need to be additional hotfixes. Right now all the versions below 0.46.9 seem like a 0.45.5 release.

3

I’m just going to stick my head out and suggest a slight modification to your opening line

“Cursor IDE was a great tool before they started to ensh’t’fy it”

4

You should also stick your head at the last sentence of my first paragraph.

5

Please see my latest post in the bug report forum.

6

Shut up

You Expect Too Much

I Would Much Rather Get New Features To Code Faster Than Wait For A Polished Version

7

wtf with you

8

I completely agree with everything, Cursor is a good IDE, but there are too many problems with version 0.46, and there are really few useful changes

9

Agreed. Love Cursor and have converted people to using it. But one I know is walking away from it due to this update. They need to cater to their professional customers that will stick around long term. And professional customers need more reliability, and direct pathways to downgrading when they new major version is working it’s kinks out. Without the path to downgrading having first party support, you’re introducing too much burden on your team to fix issues rapidly for the current version. Professionals need things to work, and if the hot new update genuinely impedes their ability to ship, then that has very real world impact for them. Not taking that seriously will simply have professionals walking away from Cursor.

5 Likes
10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.