Extension fails in virtual workspaces

“The bundled binary is fine; there is just no local working directory for it to run against.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/claude-code/issues/862/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Extension fails to start in virtual workspace folders. Spawn with a non-file: workspace folder as cwd fails with ENOENT, misreported as a binary libc mismatch.

Is this your bug?

File my report

Where: VS Code extension
Error text: [error] claude auth status spawn failed: Error: spawn c:\Users\...\native-binary\claude.exe ENOENT
Versions: 2.1.281 to 10.0.22631
Platforms: Windows

Part of: Panel won't load in remote workspaces3 bugs

Blank VS Code sidebar on WSL3 people
Blank panel in WSL15 people

Not quite your bug?

Drive-letter case breaks trust3 people

Original reports2, newest first

Sep 29, 2026VS Code extension: virtual workspace folder as spawn cwd causes ENOENT, misreported as libc/binary mismatch#98081
Sep 23, 2026VS Code extension activates in virtual workspaces and shows a misleading "native binary failed to launch (libc)" error#96525