Heyyy
I got similar errors of Extension Host. At the first I found It was about ‘cursor-socket’. After I turned off ‘Index Respositories for Instant Grep(BETA)’, It worked well.
Cursor Settings > Indexing & Docs > Index Repositories for Instant Grep(BETA)
Hope it works.
I’m having this problem on 2.6.19. I have a brand new macbook pro. Maybe something is wrong on new machines that the makers of cursor did not consider.
Waiting for Extension Host has already caused serious disruption to my work, and I have now developed a lack of trust in Cursor as a product.
This issue occurs frequently and interrupts my workflow, forcing me to stop what I am doing and wait without any clear indication of when it will recover. As a result, my productivity has been significantly affected.
What concerns me most is the lack of stability and predictability. A development tool should enhance efficiency, not introduce uncertainty or unexpected interruptions. At this point, I find it difficult to rely on Cursor for critical tasks.
I hope this issue can be addressed promptly, as stability and reliability are essential for maintaining user trust.
Version: 2.6.19
VSCode Version: 1.105.1
Commit: 224838f96445be37e3db643a163a817c15b36060
Date: 2026-03-12T04:07:27.435Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0
Same, just finished restoring to my new MBP from Time Machine. Waiting for extension host…
Hey, I ALSO just got cursor up and running on my new 2026 MBP. I had Waiting for Extension Host issues.
I restored my new 2026 ARM MBP from a Time Machine of a 2019 Intel MBP. I had Intel MacPorts, Brew, and conda/python bins that would give “bad cpu type in executable” errors. After deleting a lot of stuff (/opt/local/ related, /usr/local/bin/ related, etc) cleaning path in shell startup scripts, Cursor started working…
@Colin I hope you can recognize this issue and resolve the “Waiting for Extension Host” problem as soon as possible.
After updating to the latest version of Cursor, the IDE gets stuck on “Waiting for Extension Host” and never loads. The editor is completely unusable. Enterprise support has not been able to resolve this. Any help appreciated.
Version: 2.6.20
VSCode Version: 1.105.1
Commit: b29eb4ee5f9f6d1cb2afbc09070198d3ea6ad760
Date: 2026-03-17T01:50:02.404Z
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
Hey everyone,
Quick update on the extension host issue:
.rgignore file to your repo root with specific exclusions.Index Repositories for Instant Grep (BETA) under Cursor Settings > Indexing & Docs.Our team is actively investigating the issue and working on a fix.
Apologies for the inconvenience. If you’re still experiencing this, try these workarounds and let us know your results.
Cursor IDE
On Cursor 2.6.20 over SSH Remote, the Agent gets permanently stuck at “Waiting for extension host” when the workspace directory contains symlinked directories pointing to large filesystems (podman container overlay storage with NFS mount symlinks, or large wit workspaces).
Root cause: Cursor’s internal .cursorignore file search runs ripgrep with --follow, which causes it to traverse deeply nested symlinked directories. The search times out after 30 seconds and the agent never connects.
From the extension host log (exthost/remoteexthost.log):
ExtHostSearch [cursorIgnore] internal fileSearch still running after 30001ms reason=cursorIgnoreCheck roots=1
The ripgrep command being run:
rg --files --hidden --case-sensitive --no-require-git -g ‘**/.cursorignore’ --no-ignore-parent --follow --no-config --no-ignore-global
The --follow flag causes ripgrep to follow symlinks into massive directory trees. It also bypasses .gitignore, .ignore, and .cursorignore exclusion rules for symlinked directories, so users cannot exclude them via ignore files.
The only workaround is adding “search.exclude” to .vscode/settings.json, which causes Cursor to append -g ‘!pattern’ glob arguments that ripgrep does respect.
Note: This is similar to the issue fixed in 2.4 (ripgrep .jj filesystem walk), but the --follow + symlink traversal for cursorIgnore search was NOT fixed. VS Code works fine on the same directory because it does not run this cursorIgnore search.
The cursorIgnore search should either:
search.followSymlinks: false setting should be respected for this search.
Windows 10/11
Version: 2.6.20 (user setup)
VSCode Version: 1.105.1
Commit: b29eb4ee5f9f6d1cb2afbc09070198d3ea6ad760
Date: 2026-03-17T01:50:02.404Z
OS: Windows_NT x64 10.0.26200
Remote: RHEL 8 (kernel 4.18.0-553) via SSH
Yes - Cursor is unusable
Hi @Colin
I’m facing this bug in v2.6.20 on Ubuntu running on WSL2 on Windows 11.
Cursor worked fine for a day yesterday, but today, the chat tab shows “Waiting for extension host“ whenever I give a prompt on an old thread or new.
I tried both your fixes and restarted cursor after both as well, but no difference! Hope this can be resolved soon.
Thanks!
i have the same problem
Cursor
Version: 2.6.20
VSCode Version: 1.105.1
Commit:
b29eb4ee5f9f6d1c2af-
bc09070198d3ea6ad760
Date: 2026-03-17T01:50:02.404Z (6
days ago)
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 23.1.0
I tried both your fixes and restarted cursor after both as well, but no difference
Same issue!
Version: 2.6.21 still has the same problem
Hi, the same issue, and it does not work well for only one project, for other ones it works good.
Just a question. If cursor is so amazing why don’t you use it to identify this simple issue? 
Same issue here
Version: 2.6.21 (system setup)
VSCode Version: 1.105.1
Commit: fea2f546c979a0a4ad1deab23552a43568807590
Date: 2026-03-21T22:09:10.098Z
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: Windows_NT x64 10.0.26200
Same issue here on mac and the latest cursor version
On version 2.6.22 running on RemoteSSH (no way to run through no extensions or other) having the same problem and even more.
with the vim extension (though I don’t think it relates) sometimes the tab doesn’t work (probably waiting for autocomplete).
when creating a file it just stalls loading. If I press cancel, the file is created and I just casually continue my work, otherwise it just goes on and on.
when submitting a request to the chat, it says Waiting for extension host, then either starts processing the request after about 5 minutes or just throws an error.
These problems have been there for about some times now (even though I regularly updated the versions). I cleared the install directories, home directories (of cursor), .cursor and .cursor-server folders, reinstalled the client and server sides a bunch of times, nothing works. In the meanwhile, parallel on the same machines I have vscode which runs just flawlessly.
this worked for me
softwareupdate --install-rosetta --agree-to-license
