Same issue on:
W11 Pro 25H2
WSL2
Ubuntu 24.04.4 LTS
(And working perfectly on my Fedora Workstation 44 so maybe problem with WSL?)
I have tried to remove the agent at ~/.local/bin/agent and reinstalled, and it is working now.
I tried the same but it’s not working for me unfortunately. I have tried completely reinstalling cursor and nuking all related workspace settings etc. Opening a new project also doesnt work. cursor-agent-worker stays on “Reload Window”.
Removed all agent, cursor, cursor-agent on wsl, then restart wsl. After that, start the Cursor. cursor-agent-worker still on “Reload Window” but it worked
That does not work for me unfortunately. A few weeks ago I solved this issue by uninstalling cursor on windows and reinstalling it but this time it does not work at all. Really frustrating, hope Cursor resolves this quickly.
Reverting to 3.5.38 fixed my issue, so its a recent regression. 3.6.31 is broken for me (did not test the other 3.6.x version)
Reverting to 3.5.38 is indeed working, tried latest 3.7 who’s not working,
3.5.38 working for me too. I found I could just install 3.5.38 over the existing install and seems to be okay doing that.
Wish I had thought of it earlier. Not a very productive week since this started.
…sort of. It’s working for one project but not another. Both on the same WSL. Deleted .cursor-server but still no go.
Make sure you disable auto updates:
“update.enableWindowsBackgroundUpdates”: false,
“update.mode”: “none”
I have same problem after switch to agent window and switch back ide on wsl ubuntu project
you have to delete cache folder on windows too.
Same problem here.
Just updated to 3.7.12 and it works for me.
I also have same issue, even with 3.7.12
Version: 3.7.12 (user setup)
VS Code Extension API: 1.105.1
Commit: b887a26c4f70bd8136bfffeda812b24194ec9ce0
Date: 2026-06-05T01:45:12.918Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200
I am experiencing the same thing. ls, pwd, and using an MCP server to access the browser also fail.
Then, I clicked the Agent Windows button in the top right corner and asked Cursor to try those three tools. It said it worked. I went back to the Editor and asked the same thing, and it worked there too.
My suspicion is that it might be because I opened the Agent Windows. I closed everything, then opened only the Editor and asked Cursor to check again—the result was “Execution backend unavailable.” Then I opened the Agent Windows, and it worked.
For now, that is the workaround I am using.
To be honest, for browser agent interactions, VS Code is much better. It works flawlessly without any setup. I can instruct the agent to run UAT or debugging, and it accesses the browser without any issues.
This is something that needs to be resolved by Cursor immediately. Or perhaps using WSL isn’t a priority for them?
i also have the same problem, when i connected to wsl2, cursor can not see the files in agents. in primary sidebar my files are visible. cursor is unusable.
update 1: i downgraded cursor to 3.3.30, it works rn. (downgrading is not supported but if you want to save the day.)
update log for wsl2 in June for cursor developers:
| Date | Result | Packages / versions |
|---|---|---|
| June 1 | No auto-update record found in available logs | None recorded |
| June 2 | Auto-update check ran, no package upgrade recorded | None |
| June 3 | Auto-update check ran, no package upgrade recorded | None |
| June 4 | Packages upgraded | linux-libc-dev 6.8.0-117.117 → 6.8.0-124.124 |
| June 4 | Packages upgraded | liblzma5 5.6.1+really5.4.5-1ubuntu0.2 → 5.6.1+really5.4.5-1ubuntu0.3 |
| June 4 | Packages upgraded | xz-utils 5.6.1+really5.4.5-1ubuntu0.2 → 5.6.1+really5.4.5-1ubuntu0.3 |
| June 5 | Packages upgraded | libwww-perl 6.76-1 → 6.76-1ubuntu0.1 |
| June 5 | Packages upgraded | python3-urllib3 2.0.7-1ubuntu0.6 → 2.0.7-1ubuntu0.7 |
| June 5 | Packages upgraded | python3-twisted 24.3.0-1ubuntu0.1 → 24.3.0-1ubuntu0.2 |
| June 6 | Package upgraded | nano 7.2-2ubuntu0.1 → 7.2-2ubuntu0.2 |
| June 7 | Auto-update check ran, no packages available | None |
It worked yesterday, but it’s not working today! 
For me it does not work as well:
Win11
WSL Ubuntu 22.04
Error: Execution backend unavailable. Do not retry tool calls — the execution environment is down.
Also it seems to be, that only Composer 2.5 has this issue, other models works fine for me.
same issue on Windows 11 + WSL2/Alma8 + Cursor, it makes me exhausted