My test prompt - which migrates about 600 lines of code from one file to its own file still fails. This is an action that used to routinely be done without issue prior to about a week ago. The issues range from an outright “Error calling tool” to only migrating a few lines of code instead of the 600 or so needed.
Unfortunately, Cursor is still fundamentally broken. Going to try out Cline, because I have no choice.
I’m also facing the same issue. I can’t apply the modifications in all three modes, and it prompts “no changes made”. This seriously affects efficiency.
Its inappropriate to hijack threads for promoting yourself.
Bad product
My previous post was removed by Cursor staff within 30 seconds of posting it so now that we know Cursor staff are reading these, albeit not responding…can you guys fix your app?
I think it’s the same issue, but I’m also seeing it on non-generated code. I make changes, and they don’t show in the changes to commit. When I try updating the changes get lost. When I switch back to the same branch in VScode, everything works fine again. Very frustrating.
It’s getting frustrating for sure dealing. Going to start trying the competitors soon. You can see the file it says “Apply to…” isn’t the same as the header and therefore gives me the “no changes made”. This was yesterday.
uninstall cursor, and reinstall it.
note: i remove cursor application to trash at first time, but it is still consistent with the previous issue.
And i notice Tencent Lemon (a software uninstaller) reminded me that there are still some additional file contents. remove it, and Cursor is back to normal
issue persists on PC but mac is totally fine.
going to try a deep uninstall and purge of file and PC and will report back
Good morning, I’ll tell you about my specific case. I’ve had the same problem as everyone else for a week now. The ■■■■ thing hasn’t made any changes…
I contacted technical support. I have everything updated with Sequoia 15.4. I cleared caches, uninstalled the cursor, and reinstalled. Nothing worked. Support told me to try opening the cursor without the extensions. In my specific case, with the terminal code:
open -a “Cursor” --args --disable-extensions
The cursor opened without the extensions. To test, I had already downloaded a version older than the official one from the website. In this case:
Version: 0.46.0
Confirm: 1.96.2
Date: aff57e1d9a74ed627fb5bd393e347079514436a0
Electron: 2025-02-21T04:41:48.775Z
ElectronBuildId: 32.2.6
Chromium: undefined
Node.js: 128.0.6613.186
V8: 20.18.1
OS: 12.8.374.38-electron.0
And with that, everything’s working again, I’m back to working as before.
Best regards.
… deleting the folder “~/Library/Application Support/Cursor”
This actually worked for me, it’s like a new installation. Apparently the tool stumbles over its own feet, which it accumulates in the folder over time?
It’s definitely related to ‘legacy’ issues with the tool, since I deleted the folder Cursor is talking and working successfully with me again.
Das hat bei mir tatsächlich funktioniert, es kommt einer neuinstallation gleich. Scheinbar stolpert das Tool über seine eigenen Füße, die es im Laufe der Zeit in dem Ordner ansammelt?
Es hängt definitiv mit ‘Altlasten’ des Tools zusammen, seit ich den Ordner gelöscht habe redet und arbeitet Cursor wieder erfolgreich mit mir.
When I edited small web.xml in manual mode using claude 3.7 sonnet, the changes were shown in the chat but not applied.
Deleting folder “~/Library/Application Support/Cursor” suggested here has not changed it.
I was able to apply the changes switching to the "ask"mode and pressing the apply button myself.
Is there any chance the tool starts working again as it used to be?
Update: I removed cursor from my mac and installed it again in the new version, it seems to fix the issue for the moment.
Started happening for me late yesterday (4pm Sydney/Australia) and is still persisting:
Things I tried:
“~/Library/Application Support/Cursor” as people suggestedMacOS: Sequoia v15.2 - Apple M4
Cursor Version: 0.48.9
Hey, dude, hi. Please tell me if you solved the problem, I also have a Mac Sequoia v15.2 - Apple m2. And the same problem “no changes made”
I had to split the file into smaller parts. If it’s a massive file, try putting large functions into smaller files for import and then ask it specifically to address those smaller parts instead.
Not ideal but that’s what got me going again.
It seems so uncomfortable.