After using Cursor fine for a few months, as of the past week or two, it seems to consistently fail at persisting changes to disk.
It proceeds to try to make changes by writing powershell scripts to do Find+Replace on disk, and explaining that its search_replace tool is broken.
This makes Cursor pretty unusable for me if it takes me like 5 conversations of convincing it its broken, and then waiting a very long time for it to run powershell scripts for every change it wants to make.
I’ve tried updating Cursor, restarting PC, closing all other programs, etc.
It doesn’t happen all the time, but maybe 50% of the time – definitely enough to be disruptive.
Steps to Reproduce
I can’t seem to do a minimal repro.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Hey, thanks for the report. The fact that Agent decides its search_replace tool is broken and falls back to PowerShell scripts is definitely unusual.
The mismatch where read_file shows updated content but type/findstr still show the original clearly points to a cache - disk sync issue. This is pretty serious, because it looks like the changes were applied when they actually weren’t.
Could you please collect:
Request IDs - in the chat menu, choose Chat menu > Copy Request ID for the operations where this happens
Console logs - Help > Toggle Developer Tools > Console, and take screenshots of any errors when these tools are called
Environment details:
Do you have enough free space on your disk?
Where are the files stored? (local disk, OneDrive, network storage, SSH, etc.)
Is any antivirus or other security software running?
I’ll pass this on to the team along with your analysis.
