[BUG] Claude Code extension crashes VS Code extension host on WSL2 — PendingMigrationError: navigator

Open 💬 4 comments Opened Apr 2, 2026 by mgamgamga

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?

Installing the Claude Code VS Code extension on a WSL2 Remote session crashes the extension host repeatedly. This breaks source control (infinite loading) and search (infinite loop) across the entire VS Code instance. Disabling the extension immediately resolves all issues.

The extension accesses navigator at load time, triggering PendingMigrationError before any user interaction. The crash occurs 3 times during extension initialization.

  • Host OS: Windows 11 (Build 10.0.26200)
  • WSL2: Ubuntu 22.04.4 LTS, kernel 6.6.87.2-microsoft-standard-WSL2
  • VS Code: 1.114.0 (also reproduced on 1.113.x)
  • Claude Code extension: 2.1.90 (also reproduced on prior versions)
  • Node.js (WSL): v22.21.1
  • Claude Code CLI: 2.1.90 — works perfectly in the same environment

Troubleshooting attempted (none helped):

  • Tested multiple VS Code versions (1.113.x, 1.114.0)
  • Tested multiple extension versions
  • Increased fs.inotify.max_user_watches to 524288
  • Added files.watcherExclude for node_modules, .git, build, tmp
  • Full rm -rf ~/.vscode-server + fresh reinstall — works until extension is re-enabled

What Should Happen?

The extension should load without crashing the extension host. Source control and search should continue working normally alongside the Claude Code extension

Error Messages/Logs

From Developer Tools Console (Help → Toggle Developer Tools):

ERR navigator is now a global in nodejs, please see https://aka.ms/vscode-extensions/navigator for additional info on this error.:PendingMigrationError: navigator is now a global in nodejs, please see https://aka.ms/vscode-extensions/navigator for additional info on this error.
      at get (file:///~/.vscode-server/bin/<commit-hash>/out/vs/workbench/api/node/extensionHostProcess.js:801:7210)
      at Object.<anonymous> (~/.vscode-server/extensions/anthropic.claude-code-2.1.90-linux-x64/extension.js:78:12003)
      at Module._compile (node:internal/modules/cjs/loader:1705:14)
      at Object..js (node:internal/modules/cjs/loader:1838:10)
      at Module.load (node:internal/modules/cjs/loader:1441:32)

This error repeats 3 times from different locations in extension.js (lines 78, 159, 268). A similar navigator error also appears from the remote-wsl extension, suggesting the VS Code Server's Node.js runtime is enforcing the navigator migration broadly.

Steps to Reproduce

  1. Open VS Code on Windows, connected to WSL2 (Ubuntu 22.04)
  2. Confirm source control and search work normally without Claude Code extension
  3. Install the Claude Code extension (installs into WSL via .vscode-server)
  4. Reload window (Ctrl+Shift+P → "Reload Window")
  5. Observe: extension host crashes, source control shows infinite spinner, search hangs indefinitely

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.90 (Claude Code)

Platform

Other

Operating System

Windows

Terminal/Shell

WSL (Windows Subsystem for Linux)

Additional Information

_No response_

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗