The previous version was excellent. Now, I don’t understand what the hell is going on here. The software is almost unusable. I understand that things like this happen, especially with startup companies. And yes, Cursor is a developer’s best friend. Please, kindly restore the old functional version.
I find this old version via brew:
https://download.todesktop.com/230313mzl4w4u92/Cursor%200.42.5%20-%20Build%2024111460bf2loz1-arm64-mac.zip
Please fix all the stuff and revert to old UI. Sidebar have to be an option.
Thanks
Agreed, its totally borked, its hallucinating all over the place!!
Yep. My day is pretty gone.
Its a disaster, please rollback or fix.
This also scares me going forward that every update cannot be reverted when bad things happen. SCARY!!!
I really miss the old cursor UI. The COMMAND + SHIFT + I (Composer pane was) remarkable. I’m glad to see it’s not just me. I went from cooking and flying to stuck
Please roll back!
Today, you charged me for the next month, then I agreed to the update, and now I feel robbed.
they have combine the composer to the chat, at ctr + alt + B
or click the 3 dots at top right corner and tick the toggle AI Pane
Would love to directly address these issues. What are the problems you are seeing?
Could you share some examples of where the new client struggles where the old one performed better?
Sure @amanrs
Copying from the terminal or a file to the chat doesn’t paste references; instead, it’s just plain text.
The “new feature” suggesting files to add to the context is a complete mess. It keeps suggesting random files that have nothing to do with what I want to do. On top of that, the suggestions look almost identical to the files I actually added, which is extremely frustrating. If you absolutely must add such odd options, please use a completely different background color to make them distinguishable.
Additionally, the quality of responses has deteriorated. I keep getting strange “suggestions” like this below all the time.
From my observations - if you ask on chat to add emoji to your logs, it will generate 999999999 of ‘?’
The response is always the same regardless of the chosen model—I’ve tested it on 3.5 Sonnet and gpt-4o
I’m suffering from the new version too. I have added the files needed to the context but Cursor/AI is not able to see them:
Just updated and have been struggling to get things working for the past hour, so I figured I’d pop in here and see what’s up. Too many little issues to describe however the main issue is it automatically undoes all of my changes after applying a suggestion. The inconsistent nature of the problems are preventing me from being able to reliably reproduce so I can’t really articulate them to further the discussion. …I’m currently working on trying to figure out how to rollback to previous, which was amazing. Truly amazing.
Version: 0.43.4
VSCode Version: 1.93.1
Commit: 48d735e3dec42accfdf71efabf00bb49e242b880
Date: 2024-11-26T00:13:53.586Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Darwin x64 22.6.0
agreed. the previous version was sooooo good at troubleshooting issues and building out new features in the existing codebase. This version seems blind and every “Feature” it adds breaks something and is unable to repair it. I’ve had to revert every feature built with the app today because it was garbage.
agree - it creates new things which breaks perfectly working things as it seems not to see them. New files, changing structures, new modules. I’ve spent more time chasing my tail today
EDIT: I’m also having to share the same error 3+ times for a resolution.
I noticed clicked “Codebase” from the context window instead of hitting enter includes all the files added to the context (that were there, but for some reason Cursor AI couldn’t ‘see’)
I did not use CursorAI for two days and now suddenly:
-
The Composer Floating Window is now stuck as “Open Composer as pane” and can’t be made to float.
-
When you use the Composer pane, the green and red highlights are there but no chance to accept to reject them, but it had the full “Accept All” button functional.
After the entire afternoon of figuring it out, I gave up! I suspect there’s something going on with the whole shebang. Here’s to meeting my Monday deadline for my project! Rollback to version 2 days a ago is a good idea for now…
Please provide us with a way to revert to the previous version, even if we don’t actually need to revert. Thank you.
Did they change logic to caching and context size to save on costs?
lolol → I wonder if this is where we start seeing the VC effect.
replit and all the others went downhill after trying to cut costs and optimize in the same way. Time to go back to vscode + cline or similar.
Yeah everything about this update feels like the dramatically reduced the context window. I’m skeptical if it will ever be good again.