Windows 10 Store Version: codex://new causes "Cannot find module ...\new" and breaks Chrome/Computer Use OAuth callback
What version of the Codex App are you using (From “About Codex” dialog)?
26.527.3686.0
What subscription do you have?
ChatGPT Plus
What platform is your computer?
_No response_
What issue are you seeing?
After completing Chrome integration authentication, the browser successfully reaches:
and displays an "Open Codex" button.
When clicking "Open Codex", Codex fails to handle the callback and shows the following Electron error:
Error launching app
Unable to find Electron app at:
C:\Program Files\WindowsApps\OpenAI.Codex_26.527.3686.0_x64__...\new
Cannot find module:
...\new
The same error can also be reproduced by executing:
codex://new
via Win + R.
<img width="560" height="222" alt="Image" src="https://github.com/user-attachments/assets/ddd04d1f-ce86-4a5a-81c1-b9d8d6384167" />
What steps can reproduce the bug?
- Install Codex 26.527.3686.0 from Microsoft Store.
- Install and authorize the Chrome integration.
- Complete authentication until the browser reaches:
- Click "Open Codex".
- An Electron error dialog appears.
Alternative reproduction:
- Press Win + R.
- Execute:
codex://new
- The same Electron error appears.
What is the expected behavior?
Clicking "Open Codex" should return to the installed Codex application and complete the Chrome integration setup.
Executing:
codex://new
should activate Codex normally instead of producing an Electron error.
Additional information
Environment:
- Windows 10 Home 22H2 (Build 19045.6466)
- AMD Ryzen 7 5800H
- NVIDIA RTX 3070 Laptop GPU
- Codex 26.527.3686.0
- Microsoft Store installation
- ChatGPT Plus subscription
Additional findings:
- OAuth authentication succeeds and reaches localhost:1455/success.
- Codex launches normally from the Start Menu.
- Reinstalling Codex from Microsoft Store does not resolve the issue.
- Deleting the .codex directory does not resolve the issue.
- The issue is reproducible every time.
Additional Windows 10 issue:
When the Codex window is maximized, parts of the left sidebar and top area become transparent or render incorrectly.
14 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
A similar issue happens when you just click a Codex notification.
<img width="573" height="234" alt="Image" src="https://github.com/user-attachments/assets/f1f56bd8-a28d-48be-8969-cab589441d6b" />
same
<img width="554" height="204" alt="Image" src="https://github.com/user-attachments/assets/49aff1c9-a799-4cfe-b81a-2c6e5eb64140" />
I am seeing a very similar Windows protocol/extension handoff failure, but triggered from the Codex Chrome extension gear icon rather than the "Open Codex" button.
Feedback ID:
no-active-thread-019e7a9b-199c-7b92-91b9-d61f2917d0bf
Environment:
Issue:
Clicking the gear icon in the Codex Chrome extension popup produces an Electron error instead of opening Codex/plugin settings.
Error:
Error launching app
Unable to find Electron app at:
C:\Program Files\WindowsApps\OpenAI.Codex_26.527.3366.0_x64__p2nqsd0c76g0\app\google-chrome
Cannot find module:
C:\Program Files\WindowsApps\OpenAI.Codex_26.527.3366.0_x64__p2nqsd0c76g0\app\google-chrome
Troubleshooting tried:
This looks related to the same protocol/app routing problem described here, where Codex interprets the route/activation target as an Electron app path instead of handling it inside the running app.
I can reproduce this exact issue as well.
Clicking the gear icon in the Codex Chrome extension produces:
<img width="836" height="337" alt="Image" src="https://github.com/user-attachments/assets/9f2bb08a-cfe1-4ad9-914b-fde7ce521cf2" />
I hit a similar Windows deep link bug once where the OAuth page succeeded but the custom protocol handoff mangled the route into an app path. Since itself repros it, I'd compare three things first: the raw protocol URL Windows hands to the Store app, authproxy.dev if you want to inspect the browser to app hop, or OAuth Redirect Doctor if you want the localhost success URL, deep link target, and callback path mapped side by side. imo the fact that works but dies points to protocol activation parsing, not the OAuth part.
解决了吗
I can reproduce a very similar issue on Windows 11, so this does not appear limited to Windows 10.
Environment:
In my case the path segment is
google-chromeinstead ofnew:Error launching app
Unable to find Electron app at:
C:\Program Files\WindowsApps\OpenAI.Codex_26.527.3686.0_x64__2p2nqsd0c76g0\google-chrome
Cannot find module:
...\google-chrome
The Chrome extension is installed and enabled, but the native host is not created:
Missing:
%LOCALAPPDATA%\OpenAI\extension\com.openai.codexextension.json
HKCU\Software\Google\Chrome\NativeMessagingHosts\com.openai.codexextension
Repair, uninstall/reinstall Codex, and reinstalling/reconnecting the Chrome extension did not resolve it.
I've also encountered the same problem, and all the methods mentioned above have failed. Seeking help.
:
Error launching app
Unable to find Electron app at C:/Program
Files\WindowsApps\OpenAl.Codex_26.527.3686.0_x64_2p2nqsd0c76g0\appc...\new
Cannot find module 'C:\'Program
Files\WindowsApps\OpenAl.Codex_26.527.3686.0_x64_2p2nqsd0c76g0\app\c...\new
Additional current reproducer on Windows Store Codex showing the same
codex://protocol-handler class of failure, but for Settings routes rather than onlycodex://new.Environment:
OpenAI.Codex_26.527.7698.0_x64__2p2nqsd0c76g0Connected1.1.5Repro A: Chrome extension gear
Actual result: Windows/Electron error dialog:
Repro B: direct Browser Use settings deep link
browser-use:Expected behavior:
codex://settings/computer-use/google-chromeshould open/focus Codex Settings at the Google Chrome integration page.codex://settings/browser-useshould open/focus Codex Settings at Browser Use.This appears to be the same protocol argument parsing/registration failure described here for
codex://new, still reproducing on26.527.7698.0.I can reproduce what looks like the same Windows Codex app protocol/deep-link handling issue, with two related paths from the Codex Chrome extension / Codex app handoff.
Feedback ID:
no-active-thread-019e8843-7153-7f23-b7db-7e892d14179cEnvironment / affected surfaces:
First observed error:
Clicking Open Codex from the Codex Chrome extension flow opens an Electron error dialog instead of returning to Codex.
The error says:
Important detail: the path ends with
google-chrome.A newer similar error also occurred with an OAuth callback path instead of
google-chrome:This makes it look like the Windows Codex app / Electron launcher is treating the deep-link route or OAuth callback URL as an Electron app/module path, instead of passing it to the running Codex app as a protocol/deep-link callback.
For safety, I will redact the actual OAuth
codeandstatevalues from any public screenshots.A fix has been implemented and will be released soon.
Thanks for reporting!
Module not found: /mnt/c/Users/admin/.codex/plugins/cache/openai-bundled/computer-use/26.601.21317/scripts/computer-use-client.mjs
@gshershov This doesn't seem like the same problem. I would suggest filing a separate issue so people can more easily track it. Thanks!