Waiting for Extension Host

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Im always facing an Error: Waiting for Extension Host. Everyday!!!

Steps to Reproduce

Fix it!

Expected Behavior

Operating System

Linux

Version Information

Version: 2.6.14
VSCode Version: 1.105.1
Commit: eb1c4e0702d201d1226d2a7afb25c501c2e56080
Date: 2026-03-08T15:36:54.709Z
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: Linux x64 6.17.0-14-generic

For AI issues: which model did you use?

Opus 4.6 Max

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like

Hey, this is a known issue. We’ll need a bit more data to figure out what’s causing the crash in your case.

Try these in order:

  1. Launch Cursor from Terminal with cursor --disable-extensions. If it works, the issue is caused by one of your extensions.

  2. If it still doesn’t work, run cursor --profile-temp. This rules out your settings and profile state.

  3. I need logs from Developer Tools:

    • Open the Console tab
    • Wait for the error “Waiting for Extension Host” or “Extension host terminated”
    • Copy all red errors and paste them here

A similar issue on the same version 2.6.14 is already being debugged on Windows and macOS, so it might be the same root cause.

Let me know what you see in the logs.

Same issue for me since this morning… I can’t start Cursor , got this

[error] Activating extension anysphere.cursor-socket failed due to an error:

2026-03-09 12:40:33.509 [error] Error: Cannot find module ‘/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-socket/out/main’

Require stack:

- /Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js

at Module.\_resolveFilename (node:internal/modules/cjs/loader:1390:15)

at Module.n.\_resolveFilename (node:electron/js2c/utility_init:2:16319)

at Module.e.\_resolveFilename (file:///Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:224:32179)

at defaultResolveImpl (node:internal/modules/cjs/loader:1032:19)

at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1037:22)

at Module.\_load (node:internal/modules/cjs/loader:1199:37)

at Module.c.\_load (node:electron/js2c/node_init:2:17993)

at Module.s.\_load (file:///Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:680:3563)

at Module.e.\_load (file:///Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:224:31897)

at Module.i.\_load (file:///Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:216:26927)

at TracingChannel.traceSync (node:diagnostics_channel:328:14)

at wrapModuleLoad (node:internal/modules/cjs/loader:244:24)

at Module.require (node:internal/modules/cjs/loader:1470:12)

at require (node:internal/modules/helpers:147:16)

at n0s.\_doLoadModule (file:///Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:262:2141)

Terminal sandbox could not start. This may be caused by an AppArmor configuration on your Linux system (kernel 6.2+). See the documentation for how to resolve this.
What kind of error is this?

When im waiting for the Host. It always just loading without any Error.

@Kira18 Two separate things here:

Extension Host loading forever with no errors: this matches what we’re seeing from other users on 2.6.14 today. The cursor-socket extension might be missing files. Can you run this in your terminal and share the output?

ls -la /opt/Cursor/resources/app/extensions/cursor-socket/

(If Cursor is installed somewhere else, check which cursor or find the install path first.)

If the out/ directory is missing or empty, that’s the root cause. It’s the same packaging issue other platforms are hitting right now.

Terminal sandbox error: this is a separate known issue on Linux with kernel 6.2+ and it’s not related to the Extension Host hang. More details and discussion here: Terminal sandbox could not start. For now you can safely ignore it. It only affects the terminal sandbox, not the agent itself.

@Priska Your error confirms the same issue. The cursor-socket extension is missing its out/main module. This is the same root cause as this macOS thread: cursor-socket extension missing out directory on macOS arm64, Extension Host never starts (v2.6.14).

Can you run this and share the output?

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

That will confirm what’s actually in the folder. We’re tracking this across all platforms on 2.6.14.

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

total 8

drwxr-xr-x@   3 priska  staff    96 Mar  6 06:34 .

drwxr-xr-x@ 111 priska  staff  3552 Mar  6 06:34 ..

-rw-r–r–@   1 priska  staff   595 Mar  6 06:02 package.json

There it is — the out/ directory is completely missing from the cursor-socket extension. Only package.json exists:

total 12

drwxr-xr-x 2 root root 4096 Mar 9 11:43 .

drwxr-xr-x 111 root root 4096 Mar 6 20:41 ..

-rw-r–r-- 1 root root 595 Mar 8 22:24 package.json

Sry. Which version is stable and dont have this bug?

I have the same issue with Cursor Version: 2.6.13 since today.

1 Like

Hey all.

This specific issue with cursor-socket should be fixed in 2.6.18! Please download the latest version (if your client hasn’t auto-updated).