Sandboxie Plus compatibility issues with UNC paths and terminal-IDE communication

Environment

• OS: Baremetal Windows 10
• Sandbox: Sandboxie Plus (running VSCode sandboxed)
• Claude Code: Latest claude.exe version
• Note: Sandboxie Plus allows selective folder R/W/RO permissions for Claude Code, acting as an alternative to dev containers for isolation.

Issues

1. UNC Path Problem

• When VSCode's CWD is a drive letter (e.g., C:\): Both Claude Code CLI and sidebar work fine.
• When VSCode's CWD is a UNC path (from NAS):
• Terminal starts in C:\ (not the UNC path)
• CLI works fine
• Sidebar exits with error1
• Attempted fix: Editing startup location in sidebar config didn't work.

2. Sandboxie Isolation Issue

• Terminal-to-IDE connection: Highlight text in VSCode should be noticed in CC CLI, but this doesn't work due to Sandboxie isolation.
• Workaround status: This feature works in the sidebar, but not in CLI.

3. Network Drive Workaround Failure

• Suggested workaround: Map NAS to network drive using net use Z:\
• Result: Works for unsandboxed setup, but not for sandboxed setup (Sandboxie Plus).

Additional Context

Sandboxie Plus provides fine-grained folder permission controls (Read/Write/Read-Only) for Claude Code, making it a potential alternative to dev containers for isolation. However, the current issues prevent full functionality when working with UNC paths and inter-process communication between sandboxed VSCode and Claude Code CLI.