Detect, surface, and recover orphaned Copilot Chat sessions from moved/renamed/deleted workspaces

[5a9awneh]

Problem

VS Code stores Copilot Chat sessions under workspaceStorage/<hash>/chatSessions/, where the hash is derived from the workspace folder URI. When a workspace folder is moved, renamed, or deleted, VS Code creates a new hash on next open — making all prior chat sessions permanently inaccessible through the UI. There is no mechanism to:

1. Discover orphaned chat data (workspace hashes whose folder no longer exists on disk)
2. Browse those sessions (they remain invisible in the Chat view)
3. Migrate sessions to the current workspace hash after a folder move/rename

Real-World Impact

Orphaning happens through routine project management: renaming a folder, moving a project to a different drive, reorganizing a workspace directory, or deleting a folder after archiving. Each of these silently severs the link between VS Code and its stored chat sessions. Over time, a significant percentage of a user's workspaceStorage entries can become orphaned — containing hours of valuable Copilot conversations that are completely invisible in the UI.

Proposed Solution

1. Orphan Detection: On startup or via a command, scan workspaceStorage for entries whose workspace.json folder URI points to a path that no longer exists. Surface these in the Chat history panel with a visual indicator (e.g., ⚠️ Workspace not found).

2. Orphaned Session Browser: Allow users to browse and read chat sessions from orphaned workspaces, even if the original folder is gone. The JSONL session files are fully self-contained and readable without the workspace context.

3. Session Migration / Re-linking: When a user opens a folder that appears to match an orphaned workspace (same folder name, similar path), offer to migrate or link the old chat sessions to the new workspace hash.

4. Global Chat History View: A centralized view showing all chat sessions across all workspaces (active and orphaned), similar to how "Recent Workspaces" shows all known workspaces. This directly supports the goal outlined in Unified management for persisted Copilot Chat history across different workspace contexts #285106.

Implementation Notes

• Each workspaceStorage/<hash>/workspace.json contains the original folder URI (e.g., {"folder":"file:///c%3A/Users/.../MyProject"}). Orphan detection is simply: decode the URI, check if the path exists on disk.
• Chat session JSONL files are fully self-contained: kind:0 records hold session metadata (creationDate, sessionId, requests), kind:1 records hold key-value pairs like customTitle, and kind:2 records hold incremental request/response data. No workspace context is needed to render them.
• A StreamReader-based approach reading only the first ~200 lines of each JSONL is sufficient to extract title and metadata without loading full conversation history — useful for building a lightweight index.
• Folder-name matching (comparing the last path segment of the orphaned URI against currently open folders) is a simple heuristic for suggesting re-linking candidates.
• The community has already built external tools to address parts of this gap — vscdb-fix repairs corrupted state.vscdb indices and detects cross-workspace orphans, and copilot-chat-history provides a browsing UI — but neither is integrated into VS Code itself, and neither fully addresses orphaned workspace recovery.

Related Issues

• Unified management for persisted Copilot Chat history across different workspace contexts #285106 — Unified management for persisted Copilot Chat history across different workspace contexts (Backlog, assigned to roblourens). Focuses on the management/audit/delete side; this issue focuses on the discovery and recovery of orphaned sessions specifically.
• Add #chatHistory tool vscode-copilot-chat so the agent can use, search, ground, get insights from prior chat sessions #301174 — #chatHistory tool proposal for agent-accessible chat history search. Complementary: a #chatHistory tool would be even more valuable if it could also surface orphaned sessions.

Environment

• VS Code Version: 1.101+
• OS: Windows 11

[vs-code-engineering]

Thanks for creating this issue! It looks like you may be using an old version of VS Code; the latest stable release is 1.113.0. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

[vs-code-engineering]

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[vs-code-engineering]

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[vs-code-engineering]

🙂 This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[sugix]

It happens even with most latest version in mac. Clicking existing chat sessions, opens up a new chat session and all chat history (context) is gone. Frustrating bug

[hj-82]

Please fix this soon

[riz0n8]

Preserve Copilot/Chat history when moving or renaming workspace folders (Adopt Visual Studio's local .vs approach)

If a user renames their project/workshop folder, moves it to another drive, or changes the directory structure, the absolute path changes. This breaks the connection, causing all previous chat histories to instantly vanish from the Chat view, even though the physical code files are exactly the same.

Solution

We should adopt a local, portable storage mechanism similar to Visual Studio (MSVC).
In Visual Studio, chat sessions are stored directly inside the solution's hidden metadata directory:
YourProjectFolder/.vs/YourSolutionName/CopilotSnapshots/
Because the history travels with the project folder, users can move or rename their directories without disconnecting their AI context.

Proposed Implementation for VS Code:

• Store workspace-specific chat history directly inside the project's hidden .vscode/ folder (e.g., .vscode/chat/sessions/).
• Ensure that this directory is added to standard, recommended .gitignore templates globally so local chat history is never accidentally committed to public repositories.
• Option to allow users to configure the storage location via settings (global or local), but default to the local .vscode/ path for ease of use and portability.

[Wolfybox]

bug still exists. update will lose all your session histories.

[dongshunyao]

Possible prior art for this feature request: I've built a standalone tool that detects and repairs one recoverable class of these — sessions whose .jsonl log lost its kind:0 initial record or gained a stray UTF-8 BOM (the corruption tracked in #308730), i.e. sessions that show in history but silently fail to open:

https://github.com/dongshunyao/vscode-copilot-chat-doctor

It only writes after the full op log parses and replays cleanly onto the repaired header (dry-run/backups/undo included). A built-in "detect and offer to repair" flow in VS Code would clearly be the better home for this.

[henrique-derlam]

yeah, I just lost all my chat history, very annoying.