Agents Window jumps back to previous WSL workspace after Connecting…

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

In the Agents Window, with several WSL (Ubuntu) workspaces in the sidebar, clicking an existing chat under another workspace selects it correctly, then after a short WSL reconnect the UI jumps back to the previous workspace’s chat.

This is related to Agents randomly switching workspace but different: it happens when clicking an existing chat (not only on New Agent / while typing), and only with WSL-mounted workspaces. @deanrie asked me to open a separate thread.

Recorded on 2026-08-25 ~17:00 CEST:

  • Started on vault-assistant chat 4c81fc5d-08ce-420f-a5a6-4c97de7b9e0a (“Workspace switching issue”).
  • Clicked agent-skills chat a50b3ca6-52b4-4149-adaf-ddbdc5d0c662 (“TYPO3 v14 Review”).
  • Sidebar and header correctly showed agent-skills / TYPO3 v14 Review. Chat body was a spinner. Top right showed “Connecting…”, right pane “Loading changes”.
  • After about 2–3 seconds the window switched back by itself to the vault-assistant chat.
  • Around the jump I also saw “Disconnected” / Reconnect and a toast “Setting up WSL Distro: Ubuntu” (Remote WSL).

A second click on the target chat usually stays there. Work is still possible, but it is easy to type into the wrong project.

Request ID (vault-assistant, this chat / after the jump): 4c81fc5d-08ce-420f-a5a6-4c97de7b9e0a
Request ID (agent-skills, “TYPO3 v14 Review”, the click that did not stick): a50b3ca6-52b4-4149-adaf-ddbdc5d0c662

Steps to Reproduce

  1. Windows 11 + WSL2 Ubuntu. Open the Agents Window (Glass), not the editor.
  2. Keep several WSL workspaces in the sidebar
  3. Click an existing chat under workspace A.
  4. Click an existing chat under workspace B.
  5. Watch top-right “Connecting…” for ~2–3 seconds. The UI then jumps back to workspace A’s chat.

Expected Behavior

Clicking a chat under workspace B should keep that chat and workspace selected. A WSL reconnect should not restore the previous workspace.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.9.8 (system setup)
VS Code Extension API: 1.105.1
Commit: 4aa8ff1b7877ed7bd01bcba308698f71a6735380
Date: 2026-06-25T01:39:30.490Z
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

Additional Information

The square in the recording over the chat during the transition is to hide non-public information, it is not related to the bug, the chat is shown normally and everything is readable until it switches away.

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hey @Karsten_Beyer
Thanks for the recording, that made this easy to spot. What you’re seeing matches something we addressed in a newer release, and you’re on 3.9.8 from late June which predates it (your “second click sticks” observation fits exactly).

Could you update and check if it still happens? Since you’re on the system-setup build, grab the latest from Cursor · Download and run it over your current install (settings and chats are preserved), or use Ctrl+Shift+P → “Attempt Update”.

If it still jumps back after updating, reply with the new version number and we’ll dig into the WSL side.

7

Unfortunately that update breaks it completely. Chats disappear, models just don’t answer. running agents not shown. It now switches to completely different windows on different desktops. Completely unusable.

Is there a way to downgrade again?