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?
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.
And I do not have out directory in cursor-socket: ls -la /usr/share/cursor/resources/app/extensions/cursor-socket drwxr-xr-x - root 14 Mar 11:41 dist .rw-r–r-- 182 root 12 Mar 07:49 extension.webpack.config.js .rw-r–r-- 477 root 12 Mar 07:49 package.json
I think it’s important that we sepearate two issues:
The issue specifically related to cursor-socket, which should now be fixed
“Waiting for Extension Host” issues, which can be a symptom of many different issues.
Since this thread was specifically about cursor-socket, if you’re still facing a “Waiting for Extension Host” issue, please follow the steps @deanrie outlined above and raise a new thread.
If the issue is still related to cursor-socket, please follow up here!
Hi,
I had the same problem today (it’s funny that I didn’t need AI until the end of the workday, and then I kept getting timeouts and “waiting to host” messages…)
I left it alone for about 20 minutes, then tried again, and it started working again.
The problem isn’t with the editor or the extensions (I haven’t installed any in the last few weeks)—the problem is on your end.
I understand that software development is complex, but I’ve already created a lot of threads here about issues.
I use Windsurf separately, and unfortunately (unfortunately for you), it works much better, and token usage is cheaper too.
Try a little harder
When I go to work, I wonder, “Won’t there be another update that breaks something for me?”
