# Cursor-socket extension missing out/ directory on macOS arm64 - Extension Host never starts (v2.6.14) **URL:** \ **Category:** Bug Reports\ **Tags:** crashes, macos, extensions, installation\ **Created:** [March 8, 2026, 10:03pm UTC](https://forum.cursor.com/t/cursor-socket-extension-missing-out-directory-on-macos-arm64-extension-host-never-starts-v2-6-14/154086 "2026-03-08T22:03:01Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Atul\_Kar](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/atul_kar/32/100922_2.png) [@Atul\_Kar](https://forum.cursor.com/u/Atul_Kar)\ **Post date:** [March 8, 2026, 10:03pm UTC](https://forum.cursor.com/t/cursor-socket-extension-missing-out-directory-on-macos-arm64-extension-host-never-starts-v2-6-14/154086/1 "2026-03-08T22:03:01Z")
### Where does the bug appear (feature/product)? Cursor CLI ### Describe the Bug Hi, I am on macOS Apple Silicon (arm64) and Cursor is completely broken after multiple clean reinstalls. The extension host never starts and I get “Waiting for Extension Host” indefinitely. Environment: macOS, Apple Silicon (arm64) Cursor version 2.6.14 (stable) Fresh install, no previous Cursor data Root cause identified: The cursor-socket extension is missing its out/ directory in the installed app bundle. Running this in terminal: ls /Applications/Cursor.app/Contents/Resources/app/extensions/cursor-socket/ Only returns package.json - no out/ folder or compiled code. Steps taken: Deleted Cursor.app completely Cleared all Cursor data from ~/Library/Application Support/Cursor, ~/Library/Caches/Cursor, ~/Library/Logs/Cursor, and preferences Downloaded fresh DMG from [Cursor · Download](http://cursor.com/download) multiple times Removed quarantine flag with xattr -cr Reinstalled - same result every time Error from console: Activating extension ‘anysphere.cursor-socket’ failed: Cannot find module ‘/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-socket/out/main’ Followed by repeated auth\_ready\_timeout and extension host becoming unresponsive. This appears to be a broken build on the download server for arm64. Has anyone else hit this? ### Steps to Reproduce Download Cursor DMG for macOS arm64 from [Cursor · Download](http://cursor.com/download) Install and launch Extension host never starts - stuck on “Waiting for Extension Host” ### Expected Behavior Cursor should launch normally with the extension host running. ### Operating System MacOS ### Version Information Version 2.6.14, VSCode Version 1.105.1 ### Does this stop you from using Cursor Yes - Cursor is unusable ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [March 9, 2026, 8:14am UTC](https://forum.cursor.com/t/cursor-socket-extension-missing-out-directory-on-macos-arm64-extension-host-never-starts-v2-6-14/154086/3 "2026-03-09T08:14:57Z")
Hey, thanks for the detailed report. The fact that `out/` is completely missing from cursor-socket is really unusual. A couple things to check and try: 1. Try the Universal build instead of the Apple Silicon-specific one. Go to [Cursor · Download](https://cursor.com/downloads) and grab the “Mac Universal” DMG. This will help rule out a packaging issue with the arm64 build. 2. Check if macOS Gatekeeper or any security software is stripping files. Sometimes macOS quarantine or third-party antivirus removes unsigned binaries from app bundles without warning. After installing, run: 3. What macOS version are you on? For example, Sequoia 15.x or Tahoe 26.x. 4. SHA256 of the DMG you downloaded. This helps confirm the download is not corrupted: If the Universal build works, that confirms an issue with the arm64 package and I’ll escalate it to the team. Let me know how it goes. ---
**Author:** ![Atul\_Kar](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/atul_kar/32/100922_2.png) [@Atul\_Kar](https://forum.cursor.com/u/Atul_Kar)\ **Post date:** [March 9, 2026, 7:38pm UTC](https://forum.cursor.com/t/cursor-socket-extension-missing-out-directory-on-macos-arm64-extension-host-never-starts-v2-6-14/154086/6 "2026-03-09T19:38:17Z")
![Screenshot 2026-03-09 at 2.33.02 PM](https://us1.discourse-cdn.com/cursor1/original/3X/0/0/001196946ce69890db2791c8ab267209f63a9d44.jpeg)I installed the Mac universal DMG, and ran what you asked on terminal(see screenshot) it stil lshows the same error - I’m using mac version Tahor 26.2 ![Screenshot 2026-03-09 at 2.38.02 PM](https://us1.discourse-cdn.com/cursor1/original/3X/c/6/c68ed2b03756bbc46d1f041f7df8e737d4a5a341.jpeg) ![Screenshot 2026-03-09 at 2.34.21 PM](https://us1.discourse-cdn.com/cursor1/original/3X/7/d/7d1127c910977609975d4b34ebec5655cf839518.jpeg) ---
**Author:** ![Atul\_Kar](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/atul_kar/32/100922_2.png) [@Atul\_Kar](https://forum.cursor.com/u/Atul_Kar)\ **Post date:** [March 11, 2026, 7:31pm UTC](https://forum.cursor.com/t/cursor-socket-extension-missing-out-directory-on-macos-arm64-extension-host-never-starts-v2-6-14/154086/8 "2026-03-11T19:31:34Z")
was there any resolution for this ?.. checking in if there’s any update on this issue.. ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [March 12, 2026, 10:15pm UTC](https://forum.cursor.com/t/cursor-socket-extension-missing-out-directory-on-macos-arm64-extension-host-never-starts-v2-6-14/154086/9 "2026-03-12T22:15:36Z")
Hey all. This should be fixed in 2.6.18! Please [download the latest version](https://cursor.com/download) (if your client hasn’t auto-updated). ---
**Author:** ![Atul\_Kar](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/atul_kar/32/100922_2.png) [@Atul\_Kar](https://forum.cursor.com/u/Atul_Kar)\ **Post date:** [March 13, 2026, 6:35pm UTC](https://forum.cursor.com/t/cursor-socket-extension-missing-out-directory-on-macos-arm64-extension-host-never-starts-v2-6-14/154086/10 "2026-03-13T18:35:42Z")
Hi, tried the Universal build on 2.6.19 with a full clean install (deleted app + all Library files) and still getting the same issue, but only when opening a specific existing project. New projects work fine. New error in console logs: Error: No Connect transport provider registered. at Bfa.transport (workbench.desktop.main.js:34180:614683) at async ZS.createSingleServer Other errors: [auth] Timeout waiting for auth ready signal [PluginsProviderService] getPluginMcpServers timed out after 29999.9ms POST [https://api2.cursor.sh/aiserver.v1.AnalyticsService/UploadIssueTrace](https://api2.cursor.sh/aiserver.v1.AnalyticsService/UploadIssueTrace) 429 (Too Many Requests) Steps already tried: Clean install (arm64 and Universal builds) Deleted all Cursor data from ~/Library Switched to HTTP/1.1 in Network settings Signed out and back in Created .cursorignore to exclude large CSV files Network diagnostics show Authentication UI, HTTP/2, Agent endpoint hanging indefinitely Key observation: Works fine on new projects, breaks only on existing project. Project contains large CSV files (148,920 rows) and Python backend files. macOS: Apple Silicon (arm64), Cursor 2.6.19 stable ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [March 16, 2026, 3:12pm UTC](https://forum.cursor.com/t/cursor-socket-extension-missing-out-directory-on-macos-arm64-extension-host-never-starts-v2-6-14/154086/11 "2026-03-16T15:12:44Z")
Hey @Atul_Kar Are you specifically facing an issue with `cursor-socket`, or experiencing a symptom like “Waiting for Extension Host…”? ---
**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\ **Post date:** [April 7, 2026, 3:13pm UTC](https://forum.cursor.com/t/cursor-socket-extension-missing-out-directory-on-macos-arm64-extension-host-never-starts-v2-6-14/154086/12 "2026-04-07T15:13:23Z")
This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.