›_ Codex Issues
Codex Issues / #26509

PendingMigrationError again in latest codex plugin in vscode.

Open 💬 4 comments Opened Jun 5, 2026 by Draudnaut
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the IDE extension are you using?

26.602.30954

What subscription do you have?

chatgpt pro

Which IDE are you using?

VS Code

What platform is your computer?

linux

What issue are you seeing?

When using VS Code Remote SSH, installing the Codex extension causes VS Code extension-host errors.

The problem disappears after uninstalling the Codex extension. If I reinstall the extension, the problem returns.

Observed 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 (.../extensionHostProcess.js:833:7243)
at /home/zzz/.vscode-server/extensions/openai.chatgpt-26.602.30954-linux-x64/out/extension.js:1:10389
at get value (/home/zzz/.vscode-server/extensions/openai.chatgpt-26.602.30954-linux-x64/out/extension.js:1:3497)
...

Steps to reproduce:

  1. Open VS Code connected to a remote machine via Remote SSH.
  2. Install the Codex / openai.chatgpt extension on the remote side.
  3. Reload VS Code.
  4. Open the Codex panel or wait for extension activation.
  5. Observe the PendingMigrationError in VS Code logs.
  6. Uninstall the Codex extension.
  7. The error disappears.
  8. Reinstall the Codex extension.
  9. The error returns.

Expected behavior:
The Codex extension should activate and the Codex panel should load normally in VS Code Remote SSH.

Actual behavior:
The extension host reports PendingMigrationError related to Node.js global navigator, with the stack pointing into openai.chatgpt-26.602.30954-linux-x64/out/extension.js.

Additional logs:
[CodexMcpConnection] Spawning codex app-server
[CodexMcpConnection] cli: Codex could not find bubblewrap on PATH...
[IpcClient] Received broadcast but no handler is configured method=client-status-changed

The bubblewrap warning may be separate; the main regression is that uninstalling/reinstalling the Codex extension directly toggles the navigator error.

What steps can reproduce the bug?

Steps to reproduce:

  1. Open VS Code connected to a remote machine via Remote SSH.
  2. Install the Codex / openai.chatgpt extension on the remote side.
  3. Reload VS Code.
  4. Open the Codex panel or wait for extension activation.
  5. Observe the PendingMigrationError in VS Code logs.
  6. Uninstall the Codex extension.
  7. The error disappears.
  8. Reinstall the Codex extension.
  9. The error returns.

What is the expected behavior?

Expected behavior:
The Codex extension should activate and the Codex panel should load normally in VS Code Remote SSH.

Actual behavior:
The extension host reports PendingMigrationError related to Node.js global navigator, with the stack pointing into openai.chatgpt-26.602.30954-linux-x64/out/extension.js.

Additional information

_No response_

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 2 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #25716

Powered by Codex Action

kanh888ok · 1 month ago

I can reproduce the same failure on a newer Remote-SSH setup, so this still appears present beyond 26.602.30954.

Environment:

  • VS Code Remote Server: 1.127.0, commit 4fe60c8b1cdac1c4c174f2fb180d0d758272d713
  • Remote Extension Host Node: v24.15.0
  • Codex VS Code extension: openai.chatgpt 26.623.101652 (linux-x64)
  • Remote OS: Linux x86_64, kernel 5.4.241-1-tlinux4-0023.7
  • Scenario: VS Code Remote-SSH, opening/using the Codex sidebar; the panel appears to crash/freeze after interaction.

Remote extension host log:

ExtensionService#_doActivateExtension openai.chatgpt, startup: false, activationEvent: 'onView:chatgpt.sidebarSecondaryView'
PendingMigrationError: navigator is now a global in nodejs, please see https://aka.ms/vscode-extensions/navigator for additional info on this error.
    at /root/.vscode-server/extensions/openai.chatgpt-26.623.101652-linux-x64/out/extension.js:1:10389
    at get value (/root/.vscode-server/extensions/openai.chatgpt-26.623.101652-linux-x64/out/extension.js:1:3497)
    ...
    at Object.<anonymous> (/root/.vscode-server/extensions/openai.chatgpt-26.623.101652-linux-x64/out/extension.js:576:39242)

Codex extension log after activation also repeatedly emits:

[IpcClient] Received broadcast but no handler is configured method=thread-stream-state-changed

I also checked for local wrapper/config conflicts: a separate tcodex CLI process on this machine uses CODEX_HOME=/root/.tcodex, while the VS Code extension app-server is the bundled openai.chatgpt-26.623.101652-linux-x64/bin/linux-x86_64/codex app-server with CODEX_INTERNAL_ORIGINATOR_OVERRIDE=codex_vscode and no CODEX_HOME=/root/.tcodex. So in this repro the failure does not look caused by a local tcodex/CodeBuddy config collision; the stack points directly at the extension bundle under the Remote Extension Host.

nckirik · 1 month ago

i also have the same problem with my remote connections:

  • Codex VS Code Extension : openai.chatgpt-26.707.41301-linux-arm64
  • VS Code : 1.128.0
vu2lid · 1 month ago

Confirming this also reproduces on an arm64 remote host over VS Code Remote-SSH — adding the environment details and full stack trace in case it's useful.

Environment:

  • VS Code: 1.129.0 (commit 125df4672b8a6a34975303c6b0baa124e560a4f7, built 2026-07-15T00:08:44Z)
  • Electron: 42.6.0 / Node.js: 24.18.0
  • Client OS: Linux x64
  • Remote extension host: Linux aarch64, Ubuntu 24.04 (Jetson AGX Thor, kernel 6.8.12-tegra), connected via Remote-SSH
  • Extension: Codex – OpenAI's coding agent (openai.chatgpt), v26.707.91948, linux-arm64 build

Steps to reproduce:

  1. Connect to an aarch64 Linux remote host via VS Code Remote-SSH
  2. Install the Codex extension on the remote (auto-installs the linux-arm64 build)
  3. Open the Codex/ChatGPT sidebar view (onView:chatgpt.sidebarSecondaryView)
  4. Extension host throws immediately on activation

Same pattern reported here: disappears when the extension is removed, returns identically on a fresh reinstall (ruled out a corrupted/partial install on our end).

Error (remoteexthost.log):

PendingMigrationError: navigator is now a global in nodejs, please see https://aka.ms/vscode-extensions/navigator for additional info on this error.
    at get (.../extensionHostProcess.js:852:7297)
    at /.../openai.chatgpt-26.707.91948-linux-arm64/out/extension.js:1:10389
    at get value (.../extension.js:1:3497)
    at /.../extension.js:21:145
    at $ZodObjectJIT.n (.../extension.js:1:904)
    at new ZodObject (.../extension.js:1:1146)
    ... (continues through Zod schema construction in the extension's bundled code)

Since the client here is x64 and the crash only occurs on the remote (arm64) extension host, this looks like the linux-arm64 build specifically may be bundling a dependency version that wasn't updated for this Node.js navigator global change — might be worth checking whether the linux-x64/darwin-arm64 builds pin a different (unaffected) version of the same dependency.