22 people reported
All time, since Sep 23, including 16 thumbs-up on GitHub.
Panel won't load in remote 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/themes/247/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
3 bugs in this theme
- Blank panel in WSLNo workaround yet15 people
- Extension fails in virtual workspacesNo workaround yet4 people
- Blank VS Code sidebar on WSLNo workaround yet3 people
What's included
- Sidebar renders blank in a WSL remote window with PendingMigrationError: navigator is now a global
- Panel blank in WSL after a VS Code update, webview index.js and index.css return 401
- Panel shows a 'native binary failed to launch' libc error when the first workspace folder is a virtual (non-file) folder
- Startup spawn fails with ENOENT because the virtual folder path does not exist on disk
Not included
- Chat file links with non-ASCII paths that do nothing when clicked
- Settings and session history failures from a reversed Hebrew profile path
- Extension panel problems on local Windows workspaces
Original reports6, newest first
- #102047
- VS Code extension panel is blank on stable + WSL (401 on webview/index.js); works on Insiders and local Windows#101966
- Claude Code webview blank in WSL after VS Code update, 401 on webview resources#101865
- VS Code extension: virtual workspace folder as spawn cwd causes ENOENT, misreported as libc/binary mismatch#98081
- vs code extension 2.1.283 does not work on Windows+WSL#97663
- VS Code extension activates in virtual workspaces and shows a misleading "native binary failed to launch (libc)" error#96525