-
The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive.Request ID: 2f386468-c5ae-4d2a-8d2b-a93dd63ec173. I ve try delete state.vscdb; disabled http2; still not work ;
-
always index ,always loading,how to close index?
-
After reinstall ,login has new peoblem,always loading.(pic 2)
same can not use it anymore, nothing loads
Hey, I see the screenshots - Agent Execution Timed Out, indexing stuck on Loading, and login not loading after reinstall. These are different signs of the same issue - the extension host isn’t starting.
You’ve already tried deleting state.vscdb and disabling HTTP/2. Let’s try something else:
- Launch Cursor without extensions - in Command Prompt:
"C:\Program Files\Cursor\Cursor.exe" --disable-extensions
If everything works this way, one of the extensions is breaking the extension host.
- GPU rendering (common Windows issue) - create or edit the file
%AppData%\Cursor\User\argv.json:
{
"use-angle": "gl"
}
Restart Cursor.
-
Full cache clear - close Cursor, delete contents of:
%AppData%\Cursor\User\workspaceStorage%AppData%\Cursor\Cache%AppData%\Cursor\CachedData
For workspaceStorage (make a backup first)
-
If login hangs on “Loading…” after reinstall, try disabling VPN/antivirus/firewall and repeat. Also make sure you fully deleted the
%AppData%\Cursorand%LocalAppData%\Programs\Cursorfolders before reinstalling.
This is a known issue, the team is aware. Please share:
- Cursor version (Help > About)
- Logs from Developer Console (Help > Toggle Developer Tools > Console) - any red errors there
Let me know how it goes.
Thank you very much for your reply. After using the command Prompt, it found an error, and after it automatically updated the version, the loading issue was resolved. However, I noticed many network-related problems that may be preventing me from using it. I have already turned off the VPN, etc., and I can access the relevant websites normally using my browser. Looking forward to your reply.
Hey, I can see the screenshots and the situation is clear. The cursor-socket folder only has dist/, and out/ is missing. That’s what triggers all the “No Connect transport provider registered” errors in the console.
This is a known packaging bug with the cursor-socket extension. The extension host can’t start because it looks for the compiled code in out/, but it’s actually in dist/. The team is aware and working on a fix.
Try this workaround: create a symlink. Open Command Prompt as Administrator:
cd "C:\Users\PICC\AppData\Local\Programs\cursor\resources\app\extensions\cursor-socket"
mklink /D out dist
Then restart Cursor.
If that doesn’t help, try a full cache cleanup. Close Cursor and delete the contents of these folders:
%AppData%\Cursor\Cache%AppData%\Cursor\CachedData%AppData%\Cursor\User\workspaceStorage
Please share your Cursor version (Help > About) and let me know if the workaround helped.




