codex - 💡(How to fix) Fix VS Code Codex extension blank sidebar in Remote SSH on 26.519.32039; rollback fixes it

Summary

After updating the VS Code Codex extension (openai.chatgpt) to 26.519.32039, the Codex sidebar shows a blank panel when used in a VS Code Remote SSH window. Rolling back one extension version fixes the issue.

The desired workflow is for Codex to run in the remote SSH extension host so it can execute in the server-side repository, shell, dependency environment, and filesystem. Forcing the extension to run locally with remote.extensionKind: { "openai.chatgpt": ["ui"] } is not an acceptable workaround for this use case.

Environment

• VS Code: 1.121.0
• VS Code commit: f6cfa2ea2403534de03f069bdf160d06451ed282
• Local OS: macOS arm64
• Remote: Linux x64 via VS Code Remote SSH
• Extension id: openai.chatgpt
• Broken extension version observed: 26.519.32039
• Workaround that fixes it: roll back one extension version

Steps to reproduce

1. Open a project using VS Code Remote SSH.
2. Install or update the Codex VS Code extension to 26.519.32039 on the remote SSH side.
3. Open the Codex sidebar.
4. Observe that the sidebar is blank.

Expected behavior

The Codex sidebar should load normally, and Codex should run in the remote SSH extension host so that commands and file operations happen in the server-side repo/environment.

Actual behavior

The Codex sidebar is blank in the Remote SSH window.

The VS Code renderer / extension host logs include errors like:

PendingMigrationError: navigator is now a global in nodejs
navigator is now a global in nodejs, please see https://aka.ms/vscode-extensions/navigator

The stack points into the remote extension installation, e.g.:

~/.vscode-server/extensions/openai.chatgpt-26.519.32039-linux-x64/out/extension.js

Workarounds tried

• remote.extensionKind: { "openai.chatgpt": ["ui"] } makes the UI usable, but this moves Codex out of the remote extension host and is not acceptable for server-side execution.
• extensions.supportNodeGlobalNavigator: false was tried.
• Rolling back one extension version fixed the Remote SSH sidebar issue.

Impact

This blocks using Codex in the intended Remote SSH workflow, where execution must happen on the server-side repository/environment rather than locally.