vscode

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Claude VSCode extension cannot restore chat history after VSCode restart when the workspace is on a mapped network drive.

Environment:

• OS: Windows
• VSCode workspace path:

Z:\gitcode\x3588_android12_r10\x3588_android12_r10

• Z: is a mapped network drive:

Z: -> \\dl-67\Song

• Claude VSCode extension entrypoint: claude-vscode
• Version recorded in session metadata: 2.1.145

Issue:
When I use Claude inside VSCode extension in this workspace, conversations disappear from the extension UI after I close and reopen VSCode.

However, the history is not actually lost:

• Running Claude Code from the terminal in the same workspace works correctly.
• The /resume command can list and restore previous conversations.
• The history files exist under:

C:\Users\hhhh\.claude\projects\z--gitcode-x3588-android12-r10-x3588-android12-r10\

I also tried opening the workspace consistently through the same Z:\ path and using a fixed .code-workspace file, but the VSCode extension still does not restore the previous conversations after restart.

Expected behavior:
The Claude VSCode extension should show or restore the same project conversation history that Claude Code CLI can access with /resume.

Actual behavior:
Claude Code CLI can see the history, but the VSCode extension UI does not show previous conversations after VSCode is restarted.

This appears to be a VSCode extension history indexing/restoration issue, possibly related to mapped network drives or workspace path normalization.

Proposed Solution

no

Alternative Solutions

no

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_