Cursor 0.45 vs 0.46: Experiences and Feedback Request
Hi everyone,
I’m sharing this post to compare versions 0.45 and 0.46 of the Cursor tool, and to invite you to log your specific use cases and experiences here.
My Testing Process
• Setup:
I downloaded both Cursor 0.45 and Cursor 0.46 as separate versions, renaming them accordingly. After installation, I opened the same projects in both versions and executed the identical command within the same composer environment.
• Test Execution:
• Cursor 0.46:
• I ran the same command 10 times using the same model. Unfortunately, in about 5 to 6 of those runs, I encountered connection issues with Anthropic.
• For the remaining runs, I experimented with different models (including 3.7 Thinking, 3.7, and 3.5) in an attempt to resolve the error. Despite this, I repeatedly received nonsensical responses.
• These responses not only attempted to fix the script but also, inexplicably, created new scripts in entirely different directories instead of correcting the existing one. The error persisted throughout all trials.
• Cursor 0.45:
• When I performed the same tests using Cursor 0.45, both the 3.5 and 3.7 models in one shot were able to resolve the error I encountered. This clearly indicates that something in the handling between the versions has been compromised in 0.46.
Concerns and Call for Feedback
I conducted these tests in a controlled manner and observed that version 0.46 is not working as expected. This leads me to wonder whether the Cursor team is fully aware of these issues or prioritizing their resolution. Moreover, it seems that new versions are being released without addressing these critical problems. Frankly, I find the current explanations provided by the Cursor team to be quite insufficient, and it appears that they might not fully grasp the severity of the situation.
I kindly request that you share your own experiences with both Cursor 0.45 and 0.46. If possible, please test the same use case across both versions and log your results here. Your input will be valuable in providing better feedback to the team.
My previous topic was flagged as inappropriate. As a regular customer, I’m asking the team not to do that again. I pay for this service and believe I have the right to share my ideas freely, as long as I’m respectful.