[BUG] Windows: VS Code extension hides sessions when drive-letter case in recorded cwd differs from current workspace cwd

Open 💬 9 comments Opened May 25, 2026 by xjhouska

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?

When I close, then reopen Visual Studio Code, previously existing sessions are not visible in the sidebar. "Developer: Reload Window" causes the current live session vanish from the sidebar and the Claude Code tab is empty. The sessions can then be resumed from the terminal only. I have never managed to get the sessions back to the VS Code UI.

What Should Happen?

The sessions should persist close/reopen of Visual Studio Code. Doing "Developer: Reload Window" should not cause the current live session to vanish and force the user to go to the terminal to resume the session.

Error Messages/Logs

Steps to Reproduce

The working folder of the sessions in question is on a network mapped drive U:. The probable cause, as identified by Claude itself, is Windows case insensitivity where Claude hashes the drive as u: but Windows reports is back randomly as U: or u:. I'm attaching a memory file from the debugging session.

vscode-extension-session-listing-bug.md

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.150 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

This issue has 9 comments on GitHub. Read the full discussion on GitHub ↗