›_ Codex Issues
Codex Issues / #37359

Edge extension 1.2.30000.30 fails to create chat on macOS due to undefined path delimiter

Open 💬 3 comments Opened Aug 7, 2026 by IwannabeRealnerD

What version of the app are you using?

ChatGPT desktop app 26.803.41515 (build 6321)

Environment

  • macOS 26.5.2, arm64
  • Microsoft Edge 151.0.4129.59
  • ChatGPT for Edge extension 1.2.30000.30
  • ChatGPT for Chrome extension 1.2.27236.6274 (works correctly)

What issue are you seeing?

The ChatGPT side panel loads normally in Microsoft Edge, but attempting to create a chat fails with:

Error creating chat
Cannot read properties of undefined (reading 'delimiter')

Reinstalling the Edge extension through Settings → Computer use → More browsers → Microsoft Edge → Install does not resolve the problem. The Chrome extension works on the same machine and account.

The native messaging installation appears healthy:

  • The Edge extension ID is present in the com.openai.codexextension manifest's allowed_origins.
  • The native host registration includes both the Chrome and Edge extension IDs.
  • Separate native-host processes are running for both extensions.
  • The Edge side panel and sample-work page render normally.

Apparent root cause

In the Edge extension's bundled codex-sidepanel/assets/index.browser-B3UmvmtY.js, the path separator helper is equivalent to:

function joinNodeModuleDirs(entries, platform) {
  const delimiter =
    platform === "win32"
      ? pathModule.default.win32.delimiter
      : pathModule.default.posix.delimiter;
  return entries.filter((entry) => entry.length > 0).join(delimiter);
}

However, the same bundle initializes that imported module from an empty export object, equivalent to:

pathModule = interop({ exports: {} });

On macOS, reading pathModule.default.posix.delimiter therefore throws the exact reported TypeError while constructing the runtime configuration for a new chat.

The working Chrome extension 1.2.27236.6274 does not use this module. Its corresponding bundle joins directly:

nodeModuleDirs.join(platform === "win32" ? ";" : ":")

This looks like a packaging/bundling regression in Edge extension 1.2.30000.30 rather than a native-host installation or account issue.

Steps to reproduce

  1. On macOS, install the Edge integration from ChatGPT Settings → Computer use → More browsers → Microsoft Edge.
  2. Open the ChatGPT side panel in Edge.
  3. Enter any prompt that starts a new chat.
  4. Observe the delimiter TypeError.

Expected behavior

A new chat should be created, as it is with the Chrome extension on the same machine.

Related issues

Possibly related to the Edge/backend registration class of issues in #23805 and #24720, but this report has a distinct deterministic JavaScript failure in the Edge side-panel bundle.

View original on GitHub ↗

3 Comments

YourF4u1t · 17 days ago

Confirming the same issue on Windows.

Environment

  • OS: Windows 11 Home, version 25H2 (OS Build 26200.8875)
  • Microsoft Edge: 151.0.4129.72 (64-bit)
  • ChatGPT for Edge extension: 1.2.30000.30
  • ChatGPT plan: Plus

Reproduction

  1. Open Microsoft Edge.
  2. Open the ChatGPT extension in the Edge sidebar.
  3. The ChatGPT sidebar loads normally, including the model selector.
  4. Enter any prompt and try to create a new chat.

The chat immediately fails to be created with the following error:

Error creating chat
Cannot read properties of undefined (reading 'delimiter')
hezhao040108 · 17 days ago

Confirmed on Windows 11 with the same Edge extension release.

Environment

  • Windows build: 10.0.26100
  • Microsoft Edge: 151.0.4129.78
  • ChatGPT Edge extension: 1.2.30000.30
  • Edge extension ID: odlomjlbamekndcpllcnffbgeohgkmjh
  • ChatGPT/Codex Microsoft Store package: 26.803.5235.0
  • Bundled desktop release reported in logs: 26.803.41515
  • Installed Chrome extension: 1.2.27236.6274

Reproduction

The Edge side panel loads and authenticates normally, and current-page context can be added successfully. Creating a chat fails consistently with both a plain hello prompt and page context:

Error creating chat
Cannot read properties of undefined (reading 'delimiter')

Restarting Edge, toggling the extension, and reinstalling it through the official chatgpt.com/work/extension/installed setup flow did not resolve the failure.

Windows-specific bundle evidence

In Edge extension 1.2.30000.30, codex-sidepanel/assets/index.browser-B3UmvmtY.js contains a browser path implementation whose exported object sets:

sep: /,
delimiter: :,
win32: null,
posix: null

Later, the runtime configuration helper selects:

platform === win32
  ? pathModule.default.win32.delimiter
  : pathModule.default.posix.delimiter

On Windows, pathModule.default.win32 is therefore null/undefined and accessing .delimiter produces the exact observed exception. The locally installed Chrome extension 1.2.27236.6274 contains the same POSIX-only browser path shim but does not contain the win32.delimiter call.

This confirms that the regression is cross-platform and deterministic in the Edge 1.2.30000.30 side-panel bundle, rather than an account, permission, native-host, or page-context problem.

michaeledi · 14 days ago

Confirming this is still reproducible on a newer Windows desktop package, with additional native-host and bundle-level verification.

Environment

  • Windows 11, x64
  • ChatGPT/Codex Microsoft Store package: 26.810.4967.0
  • Bundled desktop release/plugin version: 26.810.41047
  • ChatGPT for Edge extension: 1.2.30000.30
  • Edge extension ID: odlomjlbamekndcpllcnffbgeohgkmjh

Observed behavior

The Edge side panel connects to the desktop app, but submitting any prompt fails with:

Error creating chat
Cannot read properties of undefined (reading 'delimiter')

This persists after restarting the desktop app and Edge.

Native-host verification

This reproduction is downstream of native messaging setup:

  • codexRuntime/hello succeeds and returns schema version 2 / native protocol version 2.
  • codexRuntime/ensure succeeds and returns a local runtime endpoint/configuration.
  • No endpoint URL, token, or user-specific path is included here.

Therefore the failure occurs after the extension has successfully connected to the desktop runtime.

Bundle-level root cause

The shipped Edge side-panel bundle initializes the imported path module from an empty export object (minified form):

var Sy=n(i(((e,t)=>{t.exports={}}))())

The new-chat configuration path then executes:

function Fy(e,t){
  let n=t==="win32"
    ? Sy.default.win32.delimiter
    : Sy.default.posix.delimiter;
  return e.filter(e=>e.length>0).join(n)
}

Since Sy.default is undefined, reading either platform delimiter throws before chat creation.

For verification, changing only this helper in a local unpacked copy to use platform literals prevents this specific exception:

function Fy(entries, platform) {
  const delimiter = platform === "win32" ? ";" : ":";
  return entries.filter(entry => entry.length > 0).join(delimiter);
}

The Microsoft Edge Store copy cannot retain this modification because extension integrity verification restores the signed bundle.

Suggested fix

Either bundle a functional node:path / path polyfill, or avoid the dependency here and join with platform === "win32" ? ";" : ":". A packaged Edge-extension test that creates a chat while nodeModuleDirs is populated would catch the regression.