All file listing and reading operations by Agent fail in WSL

Support Bug Reports
, , ,
5

Hey, thanks for the report. This is a known bug on Windows + WSL2. The agent tools like Glob, Grep, Semantic search, and shell all go through a single exec backend on the WSL side, and when the remote extension host crashes, they all fail at once with Execution backend unavailable. That’s why native Windows works but WSL doesn’t.

Try these in order:

  • Reload Window Cmd+Shift+P then Developer: Reload Window
  • Run wsl --shutdown in PowerShell, then run cursor . again
  • If that doesn’t help, delete ~/.cursor-server inside WSL. Cursor will reinstall the server

Since it broke after 3.7.27, if you roll back to the previous version and test, let me know what you find.

We’re tracking the issue, but there’s no exact ETA for a fix yet. The main discussion and updates are here: Execution backend unavailable. I’d suggest subscribing. Let me know if any of the workarounds helped.