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.