This is a known issue where the extension host becomes unresponsive, which blocks all agent tool calls. Our team is actively working on it.
Since you’ve already tried switching from Nightly to Stable and reinstalling, here are some more targeted steps:
1. Check for a leftover out folder in cursor-socket
An older workaround created an out folder that now causes problems on newer versions. Open PowerShell and run:
dir "$env:LOCALAPPDATA\Programs\cursor\resources\app\extensions\cursor-socket"
If you see an out folder alongside dist, delete it:
cd "$env:LOCALAPPDATA\Programs\cursor\resources\app\extensions\cursor-socket"
Remove-Item "out" -Recurse -Force
Then fully quit and restart Cursor.
2. Start without extensions
Run cursor --disable-extensions from the command line. If the agent works, a heavy extension is interfering with the extension host startup. You can re-enable extensions one by one to find the culprit.
3. Clear workspace state for the affected project
This can help if the issue is specific to one project. Close Cursor, then delete the workspace storage for the affected project from %APPDATA%\Cursor\User\workspaceStorage\. Each subfolder corresponds to a project — you can check the workspace.json inside each to find the right one.
Important: Back up the folder before deleting, as this removes chat history for that project.
4. If none of the above help
Please send your Extension Host logs so we can diagnose further:
-
Press Ctrl+Shift+P > “Developer: Open Logs Folder”
-
From the newest session, grab exthost.log and everything in the window1 folder
-
Share them here or email to [email protected]
@Clement_Gonin - since your issue is project-specific (one project broken, another works), step 3 above is most likely to help in your case.
@Elton_Nicolau - if resetting the IDE sometimes fixes it for you, that’s consistent with a stale extension host session. Steps 1 and 2 should make the fix more reliable than repeated resets.
