Cursor err (Agent Execution Timed Out

Support Bug Reports
5

Hey, this is a known issue. On Windows, the extension host sometimes doesn’t start or gets stuck, so any request to the agent fails with ERROR_EXTENSION_HOST_TIMEOUT. We’re tracking the bug, but I can’t share an ETA for a fix yet.

For now, please go through this checklist. It helped in a few recent similar reports:

  1. Fully close Cursor. In Task Manager, make sure there are no Cursor processes left, then start it again. Don’t just use Reload Window.
  2. Start Cursor from a terminal with cursor --classic so it opens the classic layout. If you see the dialog “Do you trust the authors of the files in this folder?” click Trust. In the Glass layout this dialog isn’t visible, and it can block the extension host. This was the cause in this thread Failed to start new Agent chat
  3. If that doesn’t help, in classic mode open the Command Palette with Ctrl+Shift+P, then run Start Extension Bisect and go through your extensions to rule out a conflicting one, especially if you recently installed anything Node.js-related.
  4. Run Cursor Settings > Network > Run Diagnostics and send the result if the steps above don’t help.

Also, can you tell me:

  • Your Cursor version from Help > About or Cursor > About Cursor. In the report form, the version got replaced with an error JSON.
  • Which layout you’re using, Glass or classic.

Let me know how it goes.