# WSL workspace context lost when switching to Agents Window (still present in 3.1)

**URL:** <https://forum.cursor.com/t/wsl-workspace-context-lost-when-switching-to-agents-window-still-present-in-3-1/157640>\
**Category:** Bug Reports\
**Tags:** agents-window, wsl, windows\
**Created:** [April 14, 2026, 2:46pm UTC](https://forum.cursor.com/t/wsl-workspace-context-lost-when-switching-to-agents-window-still-present-in-3-1/157640 "2026-04-14T14:46:26Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![Rudolf\_Horvath](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/rudolf_horvath/32/79377_2.png) [@Rudolf\_Horvath](https://forum.cursor.com/u/Rudolf_Horvath)\
**Post date:** [May 13, 2026, 1:56pm UTC](https://forum.cursor.com/t/wsl-workspace-context-lost-when-switching-to-agents-window-still-present-in-3-1/157640/17 "2026-05-13T13:56:03Z")

</div>

Hi,  
The version of Cursor:  
Version: 3.3.16 (user setup)  
VSCode Version: 1.105.1  
Commit: 7f0f522221d0ba220e4edb766bb3c47c08c14ab0  
Date: 2026-05-06T20:40:56.501Z  
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  
OS: Windows\_NT x64 10.0.26200

Request ID:  
Request ID: 45d99a6a-b057-4685-9746-b430a27a56ca  
{“error”:“ERROR\_EXTENSION\_HOST\_TIMEOUT”,“details”:{“title”:“Agent Execution Timed Out”,“detail”:“The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive.”,“isRetryable”:false,“shouldShowImmediateError”:true,“additionalInfo”:{},“buttons”:[{“label”:“Reload Window”,“reloadWindow”:{}}],“planChoices”:}}  
The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive.  
Agent Execution Timed Out [deadline\_exceeded]  
ConnectError: [deadline\_exceeded] Agent Execution Timed Out  
at oHv (vscode-file://vscode-app/c:/Users/horvrud/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:38624:25077)  
at Pmh.waitForProviderRegistration (vscode-file://vscode-app/c:/Users/horvrud/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:38624:29583)  
at async jCh.\_waitForPushRequestContextProviderRegistration (vscode-file://vscode-app/c:/Users/horvrud/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41628:4049)  
at async jCh.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/horvrud/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41628:7635)  
at async jCh.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/horvrud/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41628:19379)  
at async Qbt.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/horvrud/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29342:17002)

I have another issue opened, maybe they are related to each other:

> [@WSL startup still requires "Reinstall Cursor Server" — daily friction for multiple devs](https://forum.cursor.com/t/wsl-startup-still-requires-reinstall-cursor-server-daily-friction-for-multiple-devs/160300/7):
>
> Thanks for the detailed follow-up. The warm-vs-cold WSL comparison is useful, and this does sound distinct from a missing home mount or resource exhaustion issue. Could you share the Remote - WSL output from one failed cold start and one successful warm start? Run wsl --shutdown Start Cursor directly, without opening a WSL shell first When the “Reinstall Cursor Server” prompt appears, open View \> Output and select Remote - WSL Copy the output from that failed attempt Repeat after…

I was not able to open Developer tools, I have only these options under help:

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/8/2/823b198c0a2a0b3c0adf29696d4affef38812c00.png)

---

_[View the full topic](https://forum.cursor.com/t/wsl-workspace-context-lost-when-switching-to-agents-window-still-present-in-3-1/157640)._
