Hello community,
I’m experiencing a significant issue with Cursor on my Mac after upgrading my macOS version, and I’m hoping someone here can offer some assistance.
The Problem:
It appears that Cursor is unable to correctly write or save changes to files. This is causing various unexpected behaviors and making the editor essentially unusable for making and saving code changes. The editor doesn’t seem to persist modifications correctly.
My Setup:
-
Operating System: macOS Sonoma 14.4.1 (Build 24E263)
-
Cursor Version: The latest release available.
-
Hardware: Mac (Apple M3).
Troubleshooting Steps I’ve Already Taken:
I’ve tried the following steps based on general troubleshooting for editor issues, but none have resolved the problem:
-
Reinstalling Cursor: Completely uninstalled and then reinstalled the latest version.
-
Deleting Cache/User Data: Removed all local Cursor application support files and cache directories.
-
System Restart: Restarted my Mac multiple times.
-
Checking Permissions: Ensured that Cursor and the Terminal application (in case I launch it from there) have appropriate file system permissions (like Full Disk Access) granted in macOS System Settings > Privacy & Security.
Despite these efforts, the issue persists. I’m still unable to reliably save files or see changes reflected correctly.
I will attach screenshots to illustrate the kind of errors and behavior I’m encountering, including the linter error shown in the image (which I suspect is a symptom of the underlying inability to save the file correctly).
Has anyone else encountered similar file writing/saving problems with Cursor on macOS Sonoma, especially after a recent upgrade to 14.4.1? Are there any known compatibility issues or alternative troubleshooting steps I could try?
Any help or suggestions would be greatly appreciated.
Thanks in advance for your time and support!
Following up on my previous post about being unable to save files in Cursor after upgrading to macOS 14.4.1.
First of all, thank you for the input and suggestions so far. Based on advice I received (specifically from Google AI Gemini), I attempted to troubleshoot by opening the Developer Tools console in Cursor.
Here’s the strange update:
I navigated to the menu Help → Toggle Developer Tools. However, the moment the Developer Tools window appeared, the file writing/saving issue seemed to resolve itself spontaneously.
I did not make any changes within the console, run any commands, or adjust any settings after opening it. Simply having the Developer Tools window open caused Cursor to start working correctly again.
Cursor is now saving and writing files without any problems, and the linter error I was seeing (which I suspected was a symptom of the saving issue) has also gone away.
This is a very unexpected and puzzling outcome. Since the problem resolved itself immediately upon opening the console, I unfortunately don’t have any error messages from the console or logs related to the original problem to share anymore.
I’m relieved that I can use Cursor normally again, but I’m still very curious as to why this happened and why merely opening the developer tools would fix such an issue. Has anyone ever encountered this specific behavior with Cursor or perhaps another Electron-based application on macOS?
Anyway, for now, the issue seems to be resolved, even if the root cause remains a mystery.
Thanks again for the help and suggestions!