After last update, stuck at “Waiting for extension host”. Cursor Version 3.0 >

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I type a message in Cursor, it shows “Waiting for extension host”, then the editor freezes and does not continue responding.

Steps to Reproduce

Steps to Reproduce:

  1. Open Cursor
  2. Open a chat
  3. Start typing any message

Expected Behavior

Typing in chat should work smoothly without freezing, and the message should be processed normally.

Screenshots / Screen Recordings

Screenshot 2026-04-09 at 18.00.25.png
Screenshot 2026-04-09 at 18.00.25.png1256×308 9.47 KB

Operating System

MacOS

Version Information

Version: 3.0.13 (Universal)
VSCode Version: 1.105.1
Commit: 48a15759f53cd5fc9b5c20936ad7d79847d914b0
Date: 2026-04-07T03:05:17.114Z
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
OS: Darwin arm64 25.3.0

For AI issues: which model did you use?

Auto

For AI issues: add Request ID with privacy disabled

e2b41cf9-9040-4f2d-afa8-d389d45dd765

Additional Information

Old issue link which was closed:

Does this stop you from using Cursor

Yes - Cursor is unusable

3

Hi @mohitjain as you requested, I opened new issue for Cursor Version 3.0 >

6

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:

  1. Check the contents of cursor-socket:

    ls -la "/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-socket/"

    If you see a dist/ folder instead of out/, create a symlink:

    cd "/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-socket"
ln -s dist out

    Restart Cursor.

  2. If that doesn’t help, try launching from Terminal:

    cursor --disable-extensions

  3. Check if you have MCP servers set up: cat ~/.cursor/mcp.json. If the file exists, paste the contents here.

  4. 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.

7

Hi @deanrie all these steps did not work, I will test if 2.6.22 works

8

Doesnt work either

9

Hey, if even 2.6.22 didn’t help, it’s most likely not the version. It’s your local state. Let’s try a full cleanup and collect logs.

First I need:

  1. Your exact macOS version. Apple menu > About This Mac. I need the line that looks like 26.x
  2. The latest file from ~/Library/Application Support/Cursor/logs/main.log. Please attach it here
  3. The output of cat ~/.cursor/mcp.json. If the file doesn’t exist, just say so

While you’re collecting that, try a full state cleanup. Before you do it, back everything up just in case:

# 1. Fully quit Cursor using `Cmd+Q`, and make sure there are no Cursor processes in Activity Monitor
# 2. Delete Cursor.app
# 3. Clean the state:
rm -rf ~/Library/Application\ Support/Cursor
rm -rf ~/Library/Caches/Cursor
rm -rf ~/Library/Caches/com.todesktop.230313mzl4w4u92
rm -rf ~/.cursor
# 4. Reinstall the latest from https://cursor.com/downloads

If the issue is still there after a clean install of 3.0.13, try installing 2.6.22 again on top of the already cleaned state. What usually works is clean state plus older version, not just a downgrade.

And please still send main.log. It usually shows what’s crashing exactly like SIGTERM on processes, slow DB close, and so on. That speeds up troubleshooting a lot.