VS Code extension panel is blank on stable + WSL (401 on webview/index.js); works on Insiders and local 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?
Description
The Claude Code panel (sidebar and "Open in New Tab") is completely empty when VS Code stable is connected to WSL. No input box, no session history. The extension activates and authenticates fine, but the webview never renders.
Environment
- OS: Windows + WSL2 (Ubuntu-24.04)
- VS Code stable: 1.141.1
- Remote - WSL extension: 0.104.3
- Claude Code extension: 2.1.299 (linux-x64, installed in WSL)
- Claude Code CLI: 2.1.296 (native install)
Expected
Chat panel with input box and session history.
Actual
Blank panel. Extension log shows it is active and healthy:
- "Claude code extension is now active"
- "OAuth tokens found in secure storage"
- "MCP Server running on port ..." and the WS connection succeeds
Developer Tools console shows the webview assets failing:
vscode-remote+wsl-002bubuntu-002d24-002e04.vscode-resource.vscode-cdn.net/home/hugo/.vscode-server/extensions/anthropic.claude-code-2.1.299-linux-x64/webview/index.js: Failed to load resource: the server responded with a status of 401
index.css: Failed to load resource: the server responded with a status of 401
The Codex extension (openai.chatgpt) fails the same way on its webview assets ("Codex could not start its user interface"), so this looks like a VS Code remote webview resource problem rather than an extension-specific one.
What works
- VS Code stable opening a local Windows folder (no WSL): the panel works.
- VS Code Insiders connected to the same WSL distro and project: the panel works.
What I tried (no effect on stable + WSL)
- Reinstalled the extension (several times)
- Reinstalled VS Code stable on Windows
wsl --shutdown,wsl --update, andrm -rf ~/.vscode-server- Removed a duplicate npm-global CLI install
- No
.wslconfigpresent
What Should Happen?
The Claude Code panel should render normally in VS Code stable when connected to WSL: the chat input box and the session history (clock icon) should be visible, the same as it already works in VS Code Insiders connected to the same WSL distro and in VS Code stable on a local Windows folder.
Error Messages/Logs
Steps to Reproduce
- On Windows, install VS Code stable 1.141.1 and the "WSL" extension (v0.104.3).
- Have a WSL2 distro available (Ubuntu-24.04). Install the Claude Code CLI inside it (native install).
- From the Ubuntu terminal, open any project folder in VS Code:
cd ~/apps/<any-project>
code .
- In the VS Code window (title shows "[WSL: Ubuntu-24.04]"), install "Claude Code for VS Code" in WSL (extension 2.1.299). Reload the window.
- Click the Claude icon in the sidebar, or run "Claude Code: Open in New Tab" from the Command Palette.
- Result: the panel is completely empty (no input box, no session history).
- Open Help > Toggle Developer Tools > Console. Errors appear:
.../anthropic.claude-code-2.1.299-linux-x64/webview/index.js: Failed to load resource: the server responded with a status of 401
index.css: Failed to load resource: the server responded with a status of 401
Control cases (the panel renders correctly):
- VS Code stable opening a local Windows folder (no WSL).
- VS Code Insiders connected to the same WSL distro and project.
No project code is needed: the problem reproduces with any empty folder opened through WSL.
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
Claude Code v2.1.299
Platform
Other
Operating System
Windows
Terminal/Shell
WSL (Windows Subsystem for Linux)
Additional Information
_No response_
3 Comments
having same issue on myside with WSL, no issue with local window
This issue has been introduced by VS Code update to 1.141.1. Rolling back to 1.140.0 temporarily solves the issue until they release fix.
@hugodev502 @timeworkcoder
This issue is fixed with the new update of VS Code version 1.141.2, you can check here