Elwin
July 1, 2026, 8:21am
1
Cursor IDE
Since yesterday, the agent can’t make any successful tool calls anymore to my code.
The CLI agent inside of WSL works fine.
Connect to WSL from cursor
Open a project that has a dev container
Choose ‘Reopen in contianer’ when asked to
Ask the agent to make a code change
All tool calls fail after a timeout
Connect to WSL from cursor
Open a project that has a dev container
Choose ‘Reopen in contianer’ when asked to
Ask the agent to make a code change
Agent successfully makes tool calls
Windows 10/11
Version: 3.9.16 (user setup)
Yes - Cursor is unusable
deanrie
July 1, 2026, 8:36am
5
Hey, thanks for the detailed report. The environment and steps really helped.
This looks like a known issue on our side, not something wrong with your Dev Container config. In a nested setup like WSL → Reopen in Container, the agent execution provider doesn’t start in the remote extension host, so tool calls wait for a timeout and then fail with ERROR_EXTENSION_HOST_TIMEOUT. Chat keeps working, which is why only file reads, commands, and edits break. We’re also tracking the same symptom in a related thread: [WSL Remote] anysphere.cursor-agent-exec never registers — every agent prompt times out (ERROR_EXTENSION_HOST_TIMEOUT) in remote-WSL windows only; works locally and via cursor-agent CLI
There’s no fix yet, and I can’t share an ETA. The working workarounds for now, which it sounds like you already found:
Use the cursor-agent CLI directly inside WSL.
Work in WSL directly without Reopen in Container until we fix this.
I’ve reported this internally as a separate case for nested WSL → Dev Container. I’ll post an update in the thread when I have one.
Just FYI in my case there is no nesting at all. I’m just trying to connect to WSL from Agent UI
tarun
July 2, 2026, 5:15pm
9
Hey @Marcin_Ceglarek ! Tarun here from the engineering team.
Can you please share your logs, I am unable to reproduce from my end.
ctrl + shift + p > Export logs > select Remote - WSL and main and share it here please!
Hi Tarun, thanks for reaching out… Problem is there is no ‘export logs’ in agentic UI
I did some more testing and when i created workspace in WSL in IDE (gemini one) the ubuntu starts with small letter, when create workspace from Agent Window, it appear with capital Ubuntu and this one is not working … maybe this is something to check
Connected to broken workspace via IDE and collected logs:
remote-wsl-cursor.log (11.8 KB)
