macOS ChatGPT app Browser control fails: Cannot redefine property: process
Open 💬 6 comments Opened Jul 14, 2026 by adonis-cyril
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
App version
- ChatGPT desktop app: 26.707.71524
- App build: 5263
- Bundled Codex CLI: 0.144.2
- macOS: 26.4.1
- Mac: Apple Silicon, arm64
- Browser plugin: openai-bundled/browser 26.707.71524
What is broken?
The built-in Browser opens and works by hand. Settings shows Browser installed and enabled. The agent cannot connect to control it.
The official Browser setup fails before it can select the in-app browser:
Cannot redefine property: process
The failure happens while loading browser-client.mjs and calling setupBrowserRuntime({ globals: globalThis }).
Steps to reproduce
- Open the ChatGPT desktop app on macOS.
- Enable the bundled Browser plugin.
- Open any page in the built-in Browser.
- Start a Codex task and ask it to use
@Browser. - Codex loads the bundled Browser client through the Node-backed JavaScript tool.
- Setup fails with
Cannot redefine property: process. - Reset the JavaScript session and try again. The same error returns.
Troubleshooting already tried
- Fully quit and reopened ChatGPT.
- Reset these app UI/cache items:
~/Library/Application Support/Codex/Local Storage/leveldb~/Library/Application Support/Codex/Session Storage~/Library/Application Support/Codex/Preferences/private/tmp/codex-browser-use- The cache reset fixed the Settings page. Browser changed from unavailable to installed and enabled.
- Retried Browser setup twice, including a clean JavaScript session.
- Confirmed the Browser plugin exists in both the app bundle and the local plugin cache.
Expected result
Codex should connect to the open built-in Browser and then read its Browser documentation.
Actual result
The Browser page stays visible and usable by hand, but Codex cannot inspect, click, type, or verify anything because setup stops at Cannot redefine property: process.
This looks like the bundled Browser client is trying to redefine the Node tool's existing process property.
6 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Local workaround confirmed on macOS for app version 26.707.71524.
The cached file was:
~/.codex/plugins/cache/openai-bundled/browser/26.707.71524/scripts/browser-client.mjsAt the top of the file, the process shim setup was changed to:
The minified bundle's direct field reads were then changed from
global.process.<field>toglobal.processShim.<field>. In this build, the affected fields were:envexitin two placeslistenersonin two placesversionA plain
global.processcheck was left unchanged.After resetting the JavaScript tool session and loading the patched Browser client again, Browser control connected to the existing in-app Browser and returned its full documentation. It is now controlling Instagram successfully.
This is only a local workaround. Reloading bundled plugins or updating ChatGPT may overwrite it.
Local workaround worked - thanks
Independent macOS reproduction confirming this remains fully blocking.
Environment
26.707.71524(build5263)openai-bundled/browser 26.707.715240.144.126.3arm64Reproduction
~/.codex/plugins/cache/openai-bundled/browser/26.707.71524/scripts/browser-client.mjsTypeError: Cannot redefine property: processThe exact failing assignment is:
The failure happens before
setupBrowserRuntimecan exposeagent.browsers, before selecting the in-app Browser backend, and before any page or tab is inspected.As a control, the same target site was successfully navigated and verified through the separate Playwright plugin, so this is not a website, authentication, tab-state, or network failure.
Impact: the visible in-app Browser works manually, but Codex cannot inspect, click, type, or perform visual QA through it. Restarting and resetting the JavaScript session do not resolve the incompatibility.
No client data, credentials, or session transcript are included in this report.
Additional macOS reproduction affecting an unattended scheduled task.
Environment:
019f49f5-df91-76d1-afa2-80f77d343970Observed behavior:
@Browser.The local stack trace is the same failure reported here:
Impact: Browser-dependent local scheduled tasks are not reliable for unattended operation because the run cannot recover once Browser initialization fails.
Additional macOS reproduction affecting both the built-in Codex Browser and the Chrome/Browser plugin.
Environment:
Observed behavior:
Errors observed during bootstrap:
Module not found: ./node_modules/classic-level.mjsCannot redefine property: processThe failure occurs before tab discovery, navigation, authentication, or any target-site interaction. This appears consistent with the current bundled Browser/Chrome client and the protected
globalThis.processin the Codex Node runtime, rather than a Chrome profile, login, or target website problem.A clean reinstall of the same current plugin/app version did not change the behavior. The previous bundled version 26.707.62119 was reported by other users to work, while the 26.707.x update introduced this regression.