Hey, thanks for the report. This is a known issue, especially on macOS Tahoe after updating to 3.0.13. The team is aware.
Let’s try a couple things to help diagnose it:
-
Check the contents of cursor-socket:
ls -la "/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-socket/"If you see a
dist/folder instead ofout/, create a symlink:cd "/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-socket" ln -s dist outRestart Cursor.
-
If that doesn’t help, try launching from Terminal:
cursor --disable-extensions -
Check if you have MCP servers set up:
cat ~/.cursor/mcp.json. If the file exists, paste the contents here. -
Try opening a new agent window instead of the current one. For some users this helps as a temporary workaround.
If none of that works, a reliable option is to roll back to 2.6.22. A few users with the same Tahoe bug confirmed 2.6.22 is stable: Cursor last update freeze on macOS
Let me know how it goes.