It would be nice to hear something more from staff on this. It’s not fair for a paid product to perfrom this way.
This product doesn’t work that way.
בתאריך יום ה׳, 5 בפבר׳ 2026 ב-17:49 מאת Brett <[email protected]>:
I’m having the same issue on Windows with the latest version. Guys, this has been reported a million times. Please do finally fix the issue as it’s really bothering users of your paid product.
1 Like
It doesn’t work that way with this product, I think they make sure they have at least two serious bugs every time.
בתאריך יום ו׳, 6 בפבר׳ 2026 ב-15:00 מאת umberto <[email protected]>:
1 Like
Same issue. I’m paying for Pro+ but can’t use it because of this lol.
1 Like
At least they are very fair, the bug is the same for all levels of subscribers, I’m on ultra, and I still have the same thing
Due to this issue combined with the following ones, I’m no longer using Cursor to view files or manage my source control:
My current workaround is to use Visual Studio Code to view and edit files manually, check the diffs after a chat edits the code, and commit code to my repository. In my Cursor instance on a second monitor, I only have open the Chat panel, the agents panel, and sometimes a plan file.
Note that this isn’t much different than my previous setup which used Visual Studio Code alongside Claude Desktop. Cursor is slightly better than that, due to things like the semantic indexing making it better at manually pulling in files as needed, the @ and / commands making it easy to manually add context, and the summarize functionality being useful to get extra context window usage when a chat goes long. But needing to constantly work around and troubleshoot multiple bugs is wasting my time and making me lose confidence in Cursor.
I just had this issue happen again after restarting Cursor after installing the most recent update:
Version: 2.4.31 (system setup)
VSCode Version: 1.105.1
Commit: 3578107fdf149b00059ddad37048220e41681000
Date: 2026-02-08T07:42:24.999Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26100
What’s more, the phantom unsaved changes showed up in my open Visual Studio Code instance the moment Cursor launched. My same workaround from before also works in Visual Studio Code: If you stage all changes, the phantom changes disappear, while any actual changes remain and can then be un-staged.
The version has been updated to 2.4.31, and I have also encountered this problem.