@yang_zhenfang, thanks for coming back with an update. After updating to 3.3.30 it looks a bit different. The out\ folder is already created (5/13), but Diagnostics shows Timeout waiting for EverythingProvider on four services, plus Marketplace: Failed to fetch. That suggests the extension host isn’t starting properly at all, not just cursor-socket.
Please do this step by step and don’t skip anything:
Fully close Cursor. Check Task Manager to make sure there are no Cursor.exe processes running.
In an admin PowerShell, recreate out\ from a clean copy (in case the previous copy is incomplete after auto-update):
cd "$env:LOCALAPPDATA\Programs\cursor\resources\app\extensions\cursor-socket"
Remove-Item "out" -Recurse -Force -ErrorAction SilentlyContinue
Copy-Item -Path "dist" -Destination "out" -Recurse
dir "out"
Send the output of the last command. I want to confirm out\ has the same files as dist\.
Add %LOCALAPPDATA%\Programs\cursor to your antivirus exclusions. After a reboot, the antivirus may have cleaned out\ again or blocked the extension host from starting.
Launch Cursor and if the issue happens again, send logs from:
%APPDATA%\Cursor\logs\
Open the newest session and grab main.log and everything from the window1 and window2 folders. If there are any files with exthost or extension-host in the name, those are especially important.
We’re tracking an extension host issue on Windows, but there’s no exact ETA for a fix yet. The logs will help confirm whether this is the same out\ packaging issue or something new after the update.
@yang_zhenfang, thanks for the logs, now the cause is clear. This isn’t the same issue as before.
In exthost.log there’s a key line:
[error] Extension verification failed for anysphere.cursor-socket: Extra files: out/main.js
[error] Activating extension anysphere.cursor-socket failed due to an error:
[error] Error: Extension verification failed for anysphere.cursor-socket: Extra files: out/main.js
After a Cursor update, they added extension signature verification. Now the out\ folder we created earlier via Copy-Item is treated as an extra file and fails verification. So our old workaround is now breaking cursor-socket. This is a known verification issue, it’s being tracked, but there’s no ETA yet.
Let’s roll back the workaround. Fully close Cursor first and check Task Manager so there’s no Cursor.exe left, then run this in admin PowerShell:
cd "$env:LOCALAPPDATA\Programs\cursor\resources\app\extensions\cursor-socket"
Remove-Item "out" -Recurse -Force -ErrorAction SilentlyContinue
dir
Send me the output of the last command. I want to confirm only dist\ and package.json are left, with no out\.
Then launch Cursor. On recent versions, cursor-socket should load directly from dist\ without out\, so verification should pass and the extension host should start normally.
If after deleting out\ the agent still fails with the same timeout, send a fresh exthost.log from a new session in %APPDATA%\Cursor\logs\, and your exact Cursor version from Help > About. Then we’ll dig deeper, that’ll be a different case.
Great, the logs show the main thing: the Extension verification failed for anysphere.cursor-socket error is gone, and out\ is really deleted (only dist\, extension.webpack.config.js, and package.json are left). So that step worked.
Can you confirm the agent is working normally now, with no Agent Execution Timed Out? If yes, we can close the case.
About the other log lines:
[error] No bundle location found for extension anysphere.cursor-commits
This looks like a similar packaging issue, but for a different extension (cursor-commits, used for AI-generated git commit messages). It does not affect the agent. If you want to fix that feature too, you can check the same way:
dir "D:\Program Files\cursor\resources\app\extensions\anysphere.cursor-commits"
If out\ is also missing there and dist\ exists, do not change anything yet, since after deleting out\ for cursor-socket, the next verification might behave differently. First, let’s confirm the agent is stable.
[error] Error: Failed to execute git
This is a separate issue and not related to the extension host. Most likely git is not in PATH, or the project has a problematic submodule or lock. It should not affect the agent either.
For the future: after the next Cursor update, the out\ folder for cursor-socket might show up again (or it might not). If the timeout comes back, the steps are still the same as in post #28. A permanent fix on the team side is being tracked, but there is no ETA yet.
