CURSOR_HOME ignored — Cursor hardcodes .cursor directory, causing EPERM errors on macOS with SIP#3024

On macOS systems with System Integrity Protection (SIP) enabled, Cursor fails to respect the CURSOR_HOME environment variable. Even when this variable is explicitly set, the app continues to try writing to ~/.cursor, which may be protected — resulting in EPERM: operation not permitted errors and failure to launch. Steps to reproduce: 1. On macOS (Ventura or later) with SIP enabled: 2. Grant Full Disk Access to Terminal. 3. Run in Terminal: export CURSOR_HOME=~/Documents/cursor_data /Applications/Cursor.app/Contents/MacOS/Cursor 4. Cursor still attempts to create /Users/yourname/.cursor, ignoring the environment variable. Expected behavior: Cursor should fully redirect all config/data writes to the path provided by CURSOR_HOME. This would allow users with SIP or strict permissions to run the app without disabling core OS protections. Actual behavior: The app throws: Error: EPERM: operation not permitted, mkdir '/Users/yourname/.cursor' Attempts to pre-create or symlink this folder also fail. Suggested fix: • Check for and respect the CURSOR_HOME variable in all path resolutions. • Fallback to .cursor only if the variable is unset. • Document this variable in official setup instructions. System info: • macOS Ventura • SIP enabled • Terminal has Full Disk Access • Cursor version: last Thanks — love the product otherwise, but this issue is a real blocker for macOS users. NOTE: We will try our best to check Github Issues, but [forum.cursor.com](https://forum.cursor.com/) is our main site for bug reports / user feedback. We'd recommend you post there for the fastest response.