After last update, stuck at "Waiting for extension host"

Support Bug Reports
, ,
35

Same problem.

Others are saying that 2.3.35 is the latest without the problem, but I’m on 2.3.41 and can attest that it too does not have this issue.

Has anyone on the Cursor team acknowledged that they are aware of this issue (and ideally that they’re working on it)? Cursor has been completely unusable on linux for a month unless the user knows to downgrade.

Thanks,
James

36

This issue is back for me after updating to version 2.5.17 - I’m not sure how to roll this back on a mac. It says no updates are available in beta or the regular updates.

37

Same issue here. I rolled back via this and got it working GitHub - oslook/cursor-ai-downloads: All Cursor AI's official download links for both the latest and older versions, making it easy for you to update, downgrade, and choose any version. 🚀

38

Having same issue on 2.6.5

Version: 2.6.5
Commit: 49905a74f340e1f2fe8769b9ab567d1f085e3f00
Date: 2026-02-28T20:45:08.233Z
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Cursor/2.6.5 Chrome/142.0.7444.265 Electron/39.6.0 Safari/537.36

39

i also **run into**this problem on windows11 with cursor version 2.5.26, but i deal with it by waiting about 5-10 mins then is works well as before ,i gusee may it is a progress that cursors‘ agent is initializing.so may u can try wait 5-10mins then try again to see if the problem can solve or not

40

Same problem on Mac version too. Quite painful.

41

This is insane how Cursor became a unusable product where you just have to get used to navigate countless of errors, and where updates make things worse instead of improving/fixing them.

It’s like walking on a mine field.

4 Likes
43

I am also having the same issue, already 4th day I can’t use cursor.

Version: 2.6.13 (Universal)
VSCode Version: 1.105.1
Commit: 60faf7b51077ed1df1db718157bbfed740d2e160
Date: 2026-03-06T06:17:49.499Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

44

Same Issue, i think this is maybe server problem if its happen accross versions.

Version: 2.6.14 (user setup)
VSCode Version: 1.105.1
Commit: eb1c4e0702d201d1226d2a7afb25c501c2e56080
Date: 2026-03-08T15:36:54.709Z
Build Type: Stable
Release Track: Early Access
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26100

45

I haven’t seen any solution on Mac yet..

1 Like
46

Are there any updates on fixing the issue on mac?

47

It’s strange. I use Cursor on both Mac and Windows. The problem started after I updated to the latest version on Windows, and after that, even when I rolled back to a previous version, it still didn’t work. On Mac it continues to work normally, but I haven’t updated the version there. The Mac version is 2.4.37.

48

not work , and restart cursor is useless

2.3.35 is work

Version: 2.6.13
VSCode Version: 1.105.1
Commit: 60faf7b51077ed1df1db718157bbfed740d2e160
Date: 2026-03-06T06:17:49.499Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

49

@deanrie do you know if there is any progress, its been a while this issue exists and blocks development?

for me 2.3.35 doesnt work either

Version: 2.3.35
VSCode Version: 1.105.1
Commit: cf8353edc265f5e46b798bfb276861d0bf3bf120
Date: 2026-01-13T07:39:18.564Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.3.0

1 Like
51

Hey everyone, sorry for the long silence in this thread.

This is a known issue with the extension host that started showing up in versions 2,4.x. The team knows about it and is tracking it. It affects all platforms.

I’ll let you know if there are any updates on this bug.

3 Likes
52

I am working in a considerably large mono repo using remote SSH. When using the Cursor chat in the IDE, it gets stuck at “Waiting for extension host”.

I noticed that Cursor starts multiple processes like this

<path>/.cursor-server/bin/linux-x64/224838f96445be37e3db643a163a817c15b36060/node_modules/@vscode/ripgrep/bin/rg --files --hidden --no-require-git --no-config --color=never --follow --iglob */**/.cursor/rules/**/*.mdc --iglob !**/node_modules/** --iglob !**/.git/** --iglob !**/.turbo/** --iglob !**/.next/** --iglob !**/.cache/** --iglob !**/.pnpm/** --iglob !**/.yarn/** --iglob !**/dist/** --iglob !**/build/** --iglob !**/out/** --iglob !**/target/** --iglob !**/.vscode/** --iglob !**/.idea/** --iglob !**/venv/** --iglob !**/__pycache__/** --iglob !**/logs/** --iglob !**/tmp/** --iglob !**/temp/**

And they never finish. Also in Cursor settings in “Rules, Skill, Subagents” everything is stuck in a loading state.

I think the problem is that the rgcommand has */**/.cursor/rules/**/*.mdc as a pattern in conjunction with --follow which can quickly balloon the search space.

My hack for now is adding a .rgignore in my repo root that has something like:

*
!.cursor/
!AGENTS.md

This hack has fixed the problem for me. But it might have other side effects because rgis used by other tools/extensions as well. So hopefully there’s a official fix soon.

54

Environment

  • OS: macOS [e.g. Sonoma 14.x — replace with your version]
  • Cursor: [e.g. 2.6.19 — from Menu → About Cursor → Copy]

Behavior

  • The issue does not happen right after opening Cursor. It appears after leaving Cursor idle for a while (e.g. switching to another app or closing the laptop lid). When I come back, I see “Waiting for extension host” and it happens almost every time.
  • Disabling all extensions does not fix it, so it does not seem to be caused by a single extension.

From my local logs (for your triage)

  • In main.log: before/during the issue I see CodeWindow: detected unresponsive, followed by multiple Extension host with pid xxx exited with code: 0.
  • In exthost.log: Extension host terminating: renderer closed the MessagePort.
  • I also see No ptyHost heartbeat after 6 seconds and [backup tracker] suspended in the logs.
  • So it looks like after idle the window is marked unresponsive or suspended, the renderer closes the MessagePort, the extension host exits, and then the UI waits for a new one — hence “Waiting for extension host”.

Workaround

  • Cmd+Shift+P → “Developer: Reload Window” recovers the session until it happens again.

Hope this helps with debugging.