Linux: bundled Chrome plugin bootstrap fails because node_repl blocks node:process import

What version of Codex are you using?

• Codex CLI: 0.146.0
• Bundled Chrome plugin: reproduced with 26.721.41059 and 26.721.81911

Platform

Linux 7.1.4-200.nobara.fc44.x86_64 x86_64 GNU/Linux
Google Chrome 150.0.7871.186

This is native Linux, not Windows/WSL.

What issue are you seeing?

The bundled Chrome-control skill cannot bootstrap on Linux. The ChatGPT Chrome Extension is installed, enabled, connected to the intended authenticated tab, and Chrome is running, but the failure occurs before browser discovery or extension communication.

Following the bundled skill's prescribed bootstrap exactly:

if (globalThis.agent?.browsers == null) {
  const { setupBrowserRuntime } = await import(
    "/home/<user>/.codex/plugins/cache/openai-bundled/chrome/26.721.81911/scripts/browser-client.mjs"
  );
  await setupBrowserRuntime({ globals: globalThis });
}
globalThis.browser = await agent.browsers.get("extension");
nodeRepl.write(await browser.documentation());

immediately returns:

Importing module "node:process" is not allowed in node_repl

The installed browser-client.mjs contains a static import equivalent to:

import { env as ... } from "node:process";

The node_repl runtime blocks node:process, so the module fails before setupBrowserRuntime() executes. globalThis.agent remains undefined afterward. Resetting the JS kernel, restarting/reconnecting Chrome, reconnecting the extension tab, and updating/reinstalling the bundled Chrome plugin do not change the result.

The same behavior was observed with bundled Chrome plugin versions 26.721.41059 and 26.721.81911.

Steps to reproduce

1. Run Codex Desktop/agent natively on Linux.
2. Install/enable the bundled Chrome plugin and ChatGPT Chrome Extension.
3. Open Chrome and connect a tab through the extension.
4. Start the Chrome-control skill.
5. Import the plugin's absolute scripts/browser-client.mjs path using the exact bootstrap shown in its SKILL.md.
6. Observe that the import fails immediately with Importing module "node:process" is not allowed in node_repl.

Expected behavior

The trusted bundled Chrome browser client should be importable in the supported Node REPL environment on Linux, and the Chrome extension browser instance should become discoverable.

Possible resolutions include removing the static node:process dependency from the bundled browser client, using its existing process shim consistently, or permitting the trusted bundled client to import only the required safe node:process export.

Additional context

This is distinct from the existing Windows/WSL reports involving sandboxCwd, Windows paths, native-host manifests, or unavailable Node REPL tools. Here, node_repl/js is available and executes ordinary JavaScript; only the prescribed bundled browser-client import is rejected. No browser credentials, cookies, or private tab contents are needed to reproduce the failure.