The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive. Request ID: 0cf1d422-b88a-413a-aed2-ea6b429f8605
Steps to Reproduce
1: open cursor IDE
2: new agent
3: input anything and submit
4: keep displaying: taking longer than expected
5: report : The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive. Request ID: 0cf1d422-b88a-413a-aed2-ea6b429f8605
Hey, thanks for the detailed report with screenshots and the Request ID. This is ERROR_EXTENSION_HOST_TIMEOUT, a client-side error. The agent loop runs in the extension host, and if it doesn’t start up and register within about 60 seconds, you hit this timeout. The logs show that request 0cf1d422-... never reached the backend, so this is about the extension host startup on your machine, not the model or the server.
One important detail: on Windows, uninstalling Cursor doesn’t remove user data at %APPDATA%\Cursor, so uninstall plus clean can leave the extension host state unchanged. That’s why it didn’t help.
Try this in order:
Click Reload Window on the error, or fully close and restart Cursor.
Add Cursor to your antivirus or EDR exclusions. This is the most common cause on Windows. Scanning the extension host process or files can delay registration past the 60 second deadline.
With Cursor closed, clear caches in %APPDATA%\Cursor: CachedData, Cache, GPUCache, Code Cache.
Test with extensions disabled. A stuck third-party extension can block the host: Command Palette > Extensions: Disable All Installed Extensions.
Make sure Cursor is installed in the default local path with no special characters, not on OneDrive or a network drive, and that the project folder is marked as trusted.
If it still happens after that, send a new Request ID with Privacy Mode turned off, plus the log from Output panel > Extension Host. With those, we can narrow down where registration is failing.