2 people reported

All time, since Sep 19.

Remote-WSL breaks in mirrored networking

“The agent execution provider did not respond in time.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/cursor/issues/2307/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Remote-WSL connection breaks under WSL2 mirrored networking. Management connection reconnects every ~20 s and agent chat hangs; works with WSL Networking set to NAT.

Is this your bug?

File my report
Where
Remote-WSL extension
Error text
The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive.
Versions
3.21.18
Platforms
Windows
How bad
Breaks a normal workflow.

Original reports2, newest first

  1. Remote-WSL: permanent 20 s reconnect loop under WSL2 mirrored networking — client hard-codes 127.0.0.1 (via wslrelay.exe), which deadlocks on the connect-time burst#172729
  2. WSL Mirrored Networking breaks Cursor integration#172366

Do you work on Cursor?

Claim its RAP Sheet to see what your users report and answer them in one place.