Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
The chat disappears from the sidebar after moving. The transcript is still on disk, and the chat still runs. Chats that were not moved stay listed under folder1.
Steps to Reproduce
- A local agent chat is open on folder1.
- move_agent_to_root succeeds and opens a multi-root workspace with folder1 and folder Cursor creates %APPDATA%\Cursor\glassMultiRootWorkspaces\prj-2.code-workspace (workspace id 5923ec8c…).
- Look at the Agents Window sidebar.
Expected Behavior
The same chat stays in the sidebar, under the new workspace.
Operating System
Windows 10/11
Version Information
Version: 3.21.16 (user setup)
VS Code Extension API: 1.128.0
Commit: 8ae78e8eee1e63479c7e0504b664bc0a80c68000
Date: 2026-09-19T06:43:22.276Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.26200
Additional Information
Cause (by Agent)
The sidebar builds one section per row in glass.localAgentProjects.v1. A local chat is shown in a section only when composerHeaders.workspaceId is that workspace and the header projectId is that project.
The move wrote composerHeaders.workspaceId to 5923ec8c… and stopped. It did not add a project row for that workspace, did not add glass.localAgentProjectMembership.v1 for this agent, and did not set projectId on the header. The chat no longer matches folder1 (ac168e51…) either, so no section can list it.
Notes
- Agents Winow should have different section
Where does the bug appear (feature/product)? - Chat moving is awful: agent successfully moved (by script with closed Cursor to not break DB) all old chats in new agents workspace aka agent root, so it’s possible with better UX/UI
Should I fill another issue for this?
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor