Agent host bridge timeout on Windows

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Local Agent chat does not work on Windows.
Every message fails with:
Timed out waiting for the agent host bridge to register; please retry.

Request ID: 07948a72-aac2-4f2a-b8b5-077eb7933ecf

Cloud Agents work fine. Only local Agent fails.

Steps to Reproduce

  1. Open Cursor on Windows
  2. Open any folder
  3. Open Agent and send a message
  4. Wait until timeout error appears

Expected Behavior

Local Agent should reply normally.

Operating System

Windows 10/11

Current Cursor Version

(Please check Help → About in Cursor and paste here)

Does this stop you from using Cursor

Yes - local Agent is unusable. Cloud Agents still work.

Steps to Reproduce

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Local Agent chat does not work on Windows.
Every message fails with:
Timed out waiting for the agent host bridge to register; please retry.

Request ID: 07948a72-aac2-4f2a-b8b5-077eb7933ecf

Cloud Agents work fine. Only local Agent fails.

Steps to Reproduce

  1. Open Cursor on Windows
  2. Open any folder
  3. Open Agent and send a message
  4. Wait until timeout error appears

Expected Behavior

Local Agent should reply normally.

Operating System

Windows 10/11

Current Cursor Version

(Please check Help → About in Cursor and paste here)

Does this stop you from using Cursor

Yes - local Agent is unusable. Cloud Agents still work.

Expected Behavior

Local Agent should reply normally.

Operating System

Windows 10/11

Version Information

Version unknown - Windows user setup. Request ID: 07948a72-aac2-4f2a-b8b5-077eb7933ecf

Does this stop you from using Cursor

Yes - Cursor is unusable

7

Hey @iPhone, thanks for the detailed report.

This timeout means Cursor’s local Agent host did not finish starting, so the message never reached our servers. Cloud Agents use a different path, which explains why they still work. We’ve linked your report to an issue we’re tracking.

One possible cause on Windows is a missing or damaged Microsoft Visual C++ runtime. Repairing it has resolved a similar report, so please try:

  1. Download the latest Visual C++ Redistributable for x64 from Microsoft: https://aka.ms/vc14/vc_redist.x64.exe
  2. Run the installer. If it is already installed, select Repair.
  3. Restart your computer.
  4. Open Cursor and try sending another message to the local Agent.

If it still times out, press Ctrl+Shift+P, run Capture and Send Debugging Data, and let us know once it finishes. If Cursor saves a zip file to your Desktop instead of uploading it, please attach that file here.