Hey, this is a known bug: ERROR_EXTENSION_HOST_TIMEOUT. The extension host can’t finish initializing, and the agent ends up stuck on “planning next move”. On macOS it happens more often, especially after 3.2.11. I can’t share an ETA for a fix yet.
What you can try right now:
- Logout + login: one user with the same symptom said this was the only thing that helped after reinstall didn’t work. Cursor Settings → Sign out, then sign in again. Windows loading - nothing works
- Reset cache: close Cursor, rename or delete
~/.cursor(you can back it up first), then start Cursor and log in again. - Start without extensions: from Terminal run
cursor --disable-extensions. This helps confirm if a specific extension is causing it. - Downgrade: if nothing helps, manually install the previous stable version while the issue is active.
To debug faster, please share:
- macOS version Apple menu → About This Mac and Cursor version Help → About if Settings won’t open
- Help → Toggle Developer Tools → Console and the first errors that show up when the window loads
~/Library/Application Support/Cursor/logs/content, especially the latestmain.log- If you use MCP:
cat ~/.cursor/mcp.json
Related threads you can follow for updates:
- Cursor last update freeze on macOS
- My chats are just hanging with "Planning next moves" and "Taking longer than expected..."
Let me know which step worked.