Agent execution timeout

Support Bug Reports
5

Hey, this is a known bug. ERROR_EXTENSION_HOST_TIMEOUT is fixed in 3.1.17, especially on Windows. I can’t share an ETA for the fix yet, but there are a couple of working workarounds.

  1. Enable Legacy Terminal
    Settings → Cursor Settings → Agents → Legacy Terminal → enable. Restart Cursor and try again.

  2. If that didn’t help, do a clean reinstall
    In a similar thread CURSOR UNUSABLE - " Agent execution provider did not respond in time. The extension host is not running or is unresponsive. ", the root cause was a corrupted cursor-agent-exec extension file inside the installer. The hash check failed, the extension didn’t activate, and that caused the timeout. On Windows:

  • Close Cursor, open Task Manager, and kill all Cursor.exe / cursor.exe processes
  • Apps & Features → Cursor → Uninstall
  • Download the latest installer from Cursor · Download and reinstall
  • You don’t need to delete your user data at %APPDATA%\Cursor, your settings and account will stay

Please confirm your Cursor version in Help → About, and let me know if the steps above helped. If the error still happens after reinstall, we’ll need the exthost.log file from %APPDATA%\Cursor\logs\<latest session>\exthost\ and a new Request ID.