[BUG] VSCode extension: session history lost on every restart when workspace is on SSHFS/network mapped drive (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?

Session history is completely lost every time VSCode is restarted, even though the workspace path remains unchanged. The workspace is located on an SSHFS-mapped network drive (Z:\ → \sshfs\<user>@<local-ip> pointing to a macOS host).

Symptoms:

1. All conversation history disappears from the sidebar on every VSCode restart
2. Installed plugins (e.g. superpowers) repeatedly get orphaned — all cached versions are marked with .orphaned_at, and the plugin disappears from installed_plugins.json despite being listed in enabledPlugins in settings.json
3. ~/.claude/sessions/ on the local C: drive has almost no session files (only 1 file found), suggesting sessions are never persisted properly for this workspace

Additional context:

• The workspace is mounted via SSHFS (WinFsp/SSHFS-Win), not traditional SMB, but exhibits the same behavior as #37923 (SMB network drive)
• Plugin auto-update attempts repeatedly fail and orphan cache entries (observed 4 orphaned versions of superpowers over 4 days, plus 3 leftover temp_git_* directories from failed installs)
• Manually reinstalling plugins via claude plugins install works, but they may get orphaned again on next session

What Should Happen?

• Session history should persist and be restored when reopening the same workspace
• Plugin installations should remain stable across VSCode restarts
• Network/mapped drives should be handled the same as local drives for session storage

Environment

• Claude Code: v2.1.81
• Platform: Windows 11 Home (10.0.26200)
• VSCode: Latest
• Node.js: v24.13.1
• Shell: Git Bash (MINGW64)
• Drive mapping: SSHFS mapped drive (Z:\) via WinFsp/SSHFS-Win to a macOS host
• Workspace path: Z:\ (consistent, never changes)

Related Issues

• #37923 — Session history lost on network drive (SMB)
• #35367 — VSCode auto-update deletes CLI session history files
• #29017 — Conversation history lost in VSCode extension
• #31787 — Sessions disappearing when using VSCode + Desktop simultaneously