[BUG] VS Code extension doesn't restore sessions when project folder is opened via a mapped network drive letter (Windows)

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Description:

When opening a project folder using a mapped network drive letter (e.g. N:\), Claude Code sessions are not restored after closing and reopening the folder in VS Code. The session JSONL files are correctly saved in ~/.claude/projects/, but the extension shows "No sessions yet" when reopening.

However, when opening the exact same folder using its UNC path, sessions are correctly restored after closing and reopening — whether using the server's IP address (e.g. \\192.168.x.x\share\...) or its hostname (e.g. \\myserver\share\...).

What Should Happen?

Expected behavior: Sessions should be restored regardless of whether the folder is opened via a mapped drive letter or its UNC path.

Error Messages/Logs

Steps to Reproduce

Steps to reproduce:

Map a network share to a drive letter (e.g. N:\ → \\server\share\)

In VS Code, open a project folder using the mapped drive letter: N:\path\to\project

Start a Claude Code session, have a conversation

Close the folder in VS Code

Reopen the same folder (N:\path\to\project) → Session is NOT restored ("No sessions yet")

Now repeat steps 2-5 but using the UNC path instead (by IP or hostname):

\\192.168.x.x\share\path\to\project → Session IS restored
\\servername\share\path\to\project → Session IS restored

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

I use VS Code extension (No CLI).

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

Environment:

Windows 11 Pro
VS Code (latest)
Claude Code VS Code extension