(3.6.21) Cursor is completely bricked on my M3 Max Macbook pro after new update

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Specs:
2023 MacBook M3 Max, latest software.
Cursor version 3.6.21

Problem:
As soon as I upgraded to the latest version of Cursor, the IDE is COMPLETELY unusable and will not connect to the internet. Terminal, tab, Git, and basically anything useful is impossible to get working. Network diagnostics timed out. My VSCode and Antigravity work fine.

[2026-05-29T23:41:41.393Z] Error: Error: Timeout waiting for EverythingProvider

Uninstalling and reinstalling Cursor does not work. I am quite literally locked out of Cursor IDE, as I have no clue how to revert. Cursor is notoriously difficult to revert to an earlier version.

Steps to Reproduce

1- Upgrade to latest version of cursor.
2- Get screwed.

Expected Behavior

To not get your app bricked after an update.

Screenshots / Screen Recordings

Screenshot 2026-05-29 at 6.42.18 PM.png
Screenshot 2026-05-29 at 6.42.18 PM.png2002×1872 210 KB

Operating System

MacOS

Version Information

Version: 3.6.21 (Universal)
VS Code Extension API: 1.105.1
Commit: e7a7e93f4d75f8272503ecf33cedbaae10114a10
Date: 2026-05-28T21:45:36.072Z (1 day ago)
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.220
OS: Darwin arm64 25.3.0

For AI issues: which model did you use?

None. I cant use them…

Does this stop you from using Cursor

Yes - Cursor is unusable

6

This is a known bug. After certain updates, the Extension Host can fail to initialize due to leftover extension state from the previous version, which causes exactly the symptoms you’re seeing (Authentication UI, Cursor Tab, Agent Endpoint, and Codebase Indexing all timing out).

A fix for the underlying race condition shipped in your version (3.6.21), but it doesn’t automatically clean up pre-existing state from the update. A standard reinstall also won’t clear it since the extension data lives in a separate folder. Here’s what should fix it:

  1. Fully quit Cursor – open Activity Monitor, search for “Cursor,” and force-quit all Cursor processes

  2. Delete the extension cache:

rm -rf ~/Library/Application\ Support/Cursor/Cache
  1. Remove the obsolete extension marker (if it exists):
rm ~/Library/Application\ Support/Cursor/User/extensions/.obsolete
  1. Relaunch Cursor

If that doesn’t resolve it, try launching with extensions disabled to rule out a corrupted extension:

/Applications/Cursor.app/Contents/MacOS/Cursor --disable-extensions

If that works, you can re-enable extensions normally on the next launch.

You may also find this related thread helpful, where our engineering team confirmed the root cause and fix.

Let me know if that gets you back up and running!