Hi! This is a known issue on Windows + WSL — after recent updates, the agent can lose its connection to the WSL side, and when that happens file reads, search, and the terminal all stop responding at once (which matches your screenshots). It’s not something on your end, and it only affects WSL/remote setups, not native Windows.
A few things that have helped others, in order:
- Reload the window —
Ctrl+Shift+P→ Developer: Reload Window. - If that doesn’t stick, run
wsl --shutdownin PowerShell, then reopen your project withcursor .. - Still failing? Delete the
~/.cursor-serverfolder inside WSL and reconnect - Cursor reinstalls the server automatically (this just re-downloads it; your code and settings aren’t affected).
We’re actively working on a fix but don’t have an ETA to share yet. The best place to follow updates (and add your setup as a data point) is the main thread here: Execution backend unavailable.