Codex VS Code extension hangs in WSL while stuck on “Installing”

Open 💬 2 comments Opened Jul 14, 2026 by zlkzlk123

What version of the IDE extension are you using?

26.707.41301 (WSL/Ubuntu remote extension); 26.707.71524 (Windows local extension)

What subscription do you have?

ChatGPT Plus

Which IDE are you using?

Visual Studio Code 1.128.0, connected to WSL: Ubuntu

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

The Codex VS Code extension hangs in a WSL: Ubuntu remote window.

The Windows-local extension updated to 26.707.71524, but the WSL remote extension remained on 26.707.41301 and the Extensions view showed it as “Installing”. Opening the Codex panel caused it to stay loading, and after a short time the entire VS Code window became unresponsive.

Git functionality in VS Code continued to work normally; the issue was isolated to the Codex extension/panel.

Relevant log excerpts (user path redacted):

PendingMigrationError: navigator is now a global in nodejs
.../.vscode-server/extensions/openai.chatgpt-26.707.41301-linux-x64/out/extension.js

CodeWindow: detected unresponsive
CodeWindow unresponsive samples: ...

What steps can reproduce the bug?

  1. On Windows x64, open Visual Studio Code 1.128.0 connected to a WSL: Ubuntu workspace.
  2. Have the local Codex extension update to 26.707.71524 while the WSL remote extension remains on 26.707.41301.
  3. Open the Codex panel or open the Codex extension details page.
  4. The WSL extension remains in an “Installing” state.
  5. Wait briefly; the Codex panel keeps loading and then the entire VS Code window becomes unresponsive.

Retrying the installation did not resolve the problem.

What is the expected behavior?

The WSL remote extension should update successfully, or show a recoverable installation error. Opening the Codex panel should not block the VS Code renderer or make the entire editor window unresponsive.

Additional information

The issue appears related to a stale WSL remote extension version and compatibility with the current VS Code runtime. No project source code or personal data is needed to reproduce the symptom.

View original on GitHub ↗

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