Environment:
- VS Code version: 1.140.0 (commit 07f806f), x64
- OS: Windows
- Feature area: Chat / Agent Sessions view
Steps to reproduce:
- Open the Chat/Agent Sessions view in VS Code.
- Manually organize chat sessions into custom folders/groups.
- Update VS Code and/or restart it after some time.
- Reopen the Chat/Agent Sessions view.
Expected behavior:
Previously created groups/folders persist across restarts and updates.
Actual behavior:
All manually created groupings are gone; sessions revert to a flat, ungrouped list.
Additional notes:
Inspected %APPDATA%\Code\User\globalStorage\state.vscdb and the matching workspace-storage DB directly (keys: chat.ChatSessionStore.index, localAgentHost.cachedSessions.v2, agentSessions.*) and found no key that stores a group/folder association for chat or agent sessions - only flat session metadata (id, title, timestamps, working directory). This suggests the grouping UI state either isn't persisted at all, or is stored somewhere that doesn't survive update/restart. A .vscdb.backup snapshot taken a few minutes earlier already showed the same flat, groupless data, so the loss predates that backup.
Environment:
Steps to reproduce:
Expected behavior:
Previously created groups/folders persist across restarts and updates.
Actual behavior:
All manually created groupings are gone; sessions revert to a flat, ungrouped list.
Additional notes:
Inspected
%APPDATA%\Code\User\globalStorage\state.vscdband the matching workspace-storage DB directly (keys:chat.ChatSessionStore.index,localAgentHost.cachedSessions.v2,agentSessions.*) and found no key that stores a group/folder association for chat or agent sessions - only flat session metadata (id, title, timestamps, working directory). This suggests the grouping UI state either isn't persisted at all, or is stored somewhere that doesn't survive update/restart. A.vscdb.backupsnapshot taken a few minutes earlier already showed the same flat, groupless data, so the loss predates that backup.