GitHub OAuth callback fails with "Unable to find Electron app" on Windows

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• #25188
• #25157
• #25197

Powered by Codex Action

I can confirm this is the same issue.

Environment:

• Windows 11 x64
• Codex 26.527.3686.0
• ChatGPT Plus

Affected flow:

• GitHub OAuth

I reproduced the same behavior:

• GitHub authentication succeeds in browser
• codex://oauth_callback fails
• "Unable to find Electron app"
• "Cannot find module"

I also confirmed that running:

codex://test

produces the same error.

I can confirm this is the same root cause, with an action-style Codex deep link rather than only toast/OAuth.

Environment:

• Windows x64
• Codex package: OpenAI.Codex_26.527.3686.0_x64__2p2nqsd0c76g0

Repro:

Start-Process 'codex:?type=action&action=0&tag=test'

Also reproduces with:

Start-Process 'codex://?type=action&action=0&tag=test'

Actual result:
Electron shows "Error launching app" and tries to load the deep-link query string as part of the app path, e.g.:

C:\Program Files\WindowsApps\OpenAI.Codex_...\?type=action&action=0&tag=test

Troubleshooting tried:

• Windows app repair
• Windows app reset
• MSIX re-registration attempt
• Uninstall/reinstall Codex
• Reboot

Still reproduces. This looks like the same Windows external activation/protocol handling issue as this thread and related notification/OAuth reports.

I can reproduce the same issue on Windows 11 with Codex 26.527.3686.0.

Affected connectors:

• GitHub
• Slack

OAuth completes in the browser, but the codex://oauth_callback deep link opens an Electron error:
"Error launching app"
"Unable to find Electron app at C:\Program ... \oauth_callback?code=..."
"Cannot find module ..."

Reinstalling Codex did not resolve it.

Also encountered this behavior when trying to give access to gmail/netlify plugins via chrome.

Codex Version: 26.527.31326
OS: Windows 10 Pro 22H2 19045.6466

<img width="556" height="211" alt="Image" src="https://github.com/user-attachments/assets/cb3d50b9-8cdf-4418-8c5d-1e745c4276ab" />

I get the error random and it is not OAUTH.

<img width="554" height="204" alt="Image" src="https://github.com/user-attachments/assets/84b08f11-39f8-4206-91a4-c2ac49de314f" />

<img width="672" height="170" alt="Image" src="https://github.com/user-attachments/assets/4ec9e9ac-11c1-4f09-81b7-e7d5231bb62a" />

same issue when trying to pair my github account to windows codex.

Same error

<img width="584" height="234" alt="Image" src="https://github.com/user-attachments/assets/3d98cbda-3b2a-4bc5-832a-20e941631472" />

Same error
<img width="418" height="166" alt="Image" src="https://github.com/user-attachments/assets/e4c65ff7-4b24-4c4a-9aac-d6dc80bb8a30" />

<img width="558" height="221" alt="Image" src="https://github.com/user-attachments/assets/ee89c2b1-eff0-434a-a636-0fadc5d7b63b" />

I reproduced the same result on Windows 11, but so far I haven't noticed any functional impact.

<img width="938" height="388" alt="Image" src="https://github.com/user-attachments/assets/398771c3-1b9d-4fe9-955f-7ba029f9c6c6" />

I’m also seeing this on Windows 10, Codex 26.5

<img width="695" height="236" alt="Image" src="https://github.com/user-attachments/assets/5e6661fd-b78d-4d97-8fa2-a2889744a451" />

27.3686.0.

Clicking desktop notifications opens the same type=click&tag=... Electron error dialog.

Dealing with the same issue, have followed all noted steps as everyone above and receive the same identical errors. Windows 11 25H2 26200.8457

Follow-up diagnostics from my Windows 10 machine after reproducing the Gmail connector OAuth failure.

Environment observed locally:

• Windows 10 Pro 22H2, build 19045
• Installed MSIX package: OpenAI.Codex_26.527.3686.0_x64__2p2nqsd0c76g0
• Installed package status: Ok

The packaged codex: protocol registration appears to exist and be internally consistent:

AppxManifest.xml:
<uap:Extension Category="windows.protocol">
  <uap:Protocol Name="codex" />
</uap:Extension>

Package URL association:
codex -> AppXybfp6cjpb1wf0pftw0fd4bz59gzn1401

ProgID open registration:
AppUserModelID             OpenAI.Codex_2p2nqsd0c76g0!App
PackageRelativeExecutable  app\\Codex.exe
ContractId                 Windows.Protocol
PackageId                  OpenAI.Codex_26.527.3686.0_x64__2p2nqsd0c76g0
command DelegateExecute    {A56A841F-E974-45C1-8001-7E3F8A085917}

I also found HKCU\\Software\\Classes\\codex containing only the URL Protocol value. I tried both of these paths:

1. Backed up and removed that loose per-user key so Windows could use the packaged AppX handler. The callback still failed after restarting Codex, and the loose key was recreated.
2. Added an explicit per-user codex\\shell\\open\\command handler pointing to the installed Codex.exe with "%1". The callback still failed with the same Electron module-path error. I removed the manual override afterward.

Since both the packaged AppX handler and an explicit executable-plus-URL handler produce the same result, this does not look like a browser-specific problem or a simple missing Windows URL association. It appears to fail after external activation reaches Codex, likely in the Windows/Electron startup or deep-link argument handling path.

Practical impact: Gmail connector authorization cannot complete on this machine.

I added a small evidence packer for this deeplink/OAuth/notification activation class in trace-to-skill@0.1.62:

npx trace-to-skill@0.1.62 demo deeplink-launch
npx trace-to-skill@0.1.62 codex-report ./runs --output openai-codex-deeplink-launch.md

It is not a fix; it just helps reports include the fields that seem useful here: exact redacted codex://... URI, connector/plugin, browser, error dialog text, whether Codex was already running, AppX/MSIX protocol registration (AppUserModelID, DelegateExecute, HKCU/HKCR codex keys), package path, command-line args, Start-Process "codex://test" repro, notification type=click&tag repro, and repair/reinstall/re-register attempts.

Release: https://github.com/grnbtqdbyx-create/trace-to-skill/releases/tag/v0.1.62

<img width="547" height="198" alt="Image" src="https://github.com/user-attachments/assets/36aa640f-c452-47fe-8b1a-6eecb7fa5c4e" />

I’m also seeing this on Windows 11

<img width="696" height="274" alt="Image" src="https://github.com/user-attachments/assets/852d8360-860f-4453-b8ba-f39e8d3e154a" />

<img width="560" height="214" alt="Image" src="https://github.com/user-attachments/assets/100f5c22-4305-41d5-907e-947d1f667c98" />

I can confirm the same issue on Windows with the Microsoft Store/MSIX Codex app.

Environment:

• Windows PowerShell on Windows
• Codex Desktop / MSIX package path: C:\Program Files\WindowsApps\OpenAI.Codex_26.527.3686.0_x64__2p2nqsd0c76g0\...
• Codex version shown in the failing path: 26.527.3686.0

Independent repro without GitHub/OAuth:

Start-Process "codex://test"

Actual result:

Error launching app

Unable to find Electron app at:
C:\Program Files\WindowsApps\OpenAI.Codex_26.527.3686.0_x64__2p2nqsd0c76g0\app\c...\test

Cannot find module:
C:\Program Files\WindowsApps\OpenAI.Codex_26.527.3686.0_x64__2p2nqsd0c76g0\app\c...\test

This confirms the failure is not specific to GitHub, Supabase, Figma, browser choice, or any individual plugin. The bare codex://test protocol URL is being interpreted as an Electron app/module path instead of being passed to the running Codex app as a protocol/deep-link event.

So any connector flow that returns through codex://oauth_callback?code=... fails at the final callback step, even though the browser-side authorization succeeds.

Additional diagnostic information to rule out a custom/non-default install path issue:

Get-AppxPackage OpenAI.Codex | Format-List Name, PackageFullName, InstallLocation

Output:

Name            : OpenAI.Codex
PackageFullName : OpenAI.Codex_26.527.3686.0_x64__2p2nqsd0c76g0
InstallLocation : C:\Program Files\WindowsApps\OpenAI.Codex_26.527.3686.0_x64__2p2nqsd0c76g0

This shows Codex is installed in the normal Microsoft Store/MSIX WindowsApps location, not a custom install path.

I also checked the traditional Win32-style protocol handler registry keys:

Get-ItemProperty -Path "Registry::HKEY_CLASSES_ROOT\codex\shell\open\command" -ErrorAction SilentlyContinue
Get-ItemProperty -Path "Registry::HKEY_CURRENT_USER\Software\Classes\codex\shell\open\command" -ErrorAction SilentlyContinue

These did not return output, which may be expected for an MSIX/AppX protocol registration. However, Start-Process "codex://test" does launch Codex/Electron and then fails by treating the deep-link segment as a module/app path. So the protocol is reaching the Codex app, but the deep-link argument is being handled incorrectly.

<img width="551" height="206" alt="Image" src="https://github.com/user-attachments/assets/be6013d8-b70b-4ec4-af8f-e0efe8b21030" />

I can reproduce this on Windows with Codex Desktop 26.527.3686.0.

Additional diagnostics:

• Package: OpenAI.Codex_26.527.3686.0_x64__2p2nqsd0c76g0
• Get-AppxPackage -Name OpenAI.Codex reports Status: Ok
• Start-Process "codex://test" still opens an Electron error dialog:
• Error launching app
• Unable to find Electron app at ...\app\c...\test
• Cannot find module ...\app\c...\test
• Clicking Codex Windows toast notifications also fails similarly with:
• type=click&tag=... being interpreted as an Electron app path
• However, direct invocation works without error:

& 'C:\Program Files\WindowsApps\OpenAI.Codex_26.527.3686.0_x64__2p2nqsd0c76g0\app\Codex.exe' `
  'C:\Program Files\WindowsApps\OpenAI.Codex_26.527.3686.0_x64__2p2nqsd0c76g0\app\resources\app.asar' `
  'codex://test'

This suggests the app can handle the codex:// argument when app.asar is supplied explicitly, but the Windows MSIX/AppX protocol activation path launches Codex.exe without the correct Electron app entrypoint, causing Electron to treat the protocol payload as the app path.

Already tried:

• Repair Codex
• Reset Codex
• Reinstall Codex
• Add-AppxPackage -Register ...AppxManifest.xml
• Add-AppxPackage -RegisterByFamilyName -MainPackage "OpenAI.Codex_2p2nqsd0c76g0" -ForceApplicationShutdown
• Reboot
• Attempted current-user HKCU\Software\Classes\codex override

The issue persists after reboot.

same

<img width="834" height="329" alt="Image" src="https://github.com/user-attachments/assets/35e04c07-6655-40b2-a0d8-ee5c02dc1683" />

🛠️ Current Workarounds & Suggestions
Since this is a bug in the core startup logic of the application, standard system-level troubleshooting will not resolve it.

1. Avoid Unnecessary Troubleshooting (Confirmed Ineffective Methods):

Other users in this thread have already tested these, so you can save yourself some time and effort. The following actions DO NOT fix the issue:

Uninstalling and reinstalling the Codex app.

"Repairing" or "Resetting" the app via Windows Settings.

Restarting the computer.

Changing the default browser (the failure occurs with both Chrome and Edge).

Modifying the Windows Registry (URL protocol associations).

1. Temporary Workaround:

Use the Web Version: Until an official fix is released, it is highly recommended to temporarily use the web version in your browser. The web version's OAuth authorization flow does not rely on the local client's deep-link wakeup mechanism, allowing you to successfully connect and use third-party plugins like GitHub without issues.

1. Next Steps:

Wait for a Microsoft Store Update: This is a packaging issue that can only be resolved by an official update. Keep an eye on the Microsoft Store for a new version of the Codex (or OpenAI) client (specifically, a version higher than the current 26.527.3686.0).

Monitor this Issue: You can click the "Subscribe" button on the right side of this GitHub page. This way, you'll be notified immediately if official maintainers intervene or if someone provides a viable temporary script.

=======================================

My solution → 2. Temporary Workaround:

On the application page of the web version of ChatGPT (which is the link to the LLM chat interface and has launched the application), I successfully performed the authorization operation for my ChatGPT account and Gmail. Then, as long as I install the plugin on Codex, I can use it normally.

Codex Windows Store version: 26.527.3686.0
OS: Windows 10 10.0.19045.6456 x64
Package: OpenAI.Codex_26.527.3686.0_x64__2p2nqsd0c76g0

Issue:
GitHub and Gmail plugin OAuth both fail after browser authorization.
Windows protocol settings show CODEX / URL:codex -> Codex.
But Win + R -> codex://test opens an Electron error dialog:

Unable to find Electron app at:
C:\Program Files\WindowsApps\OpenAI.Codex_26.527.3686.0_x64__2p2nqsd0c76g0\app\c...\test

Cannot find module:
C:\Program Files\WindowsApps\OpenAI.Codex_26.527.3686.0_x64__2p2nqsd0c76g0\app\c...\test

Registry:
reg query HKEY_CLASSES_ROOT\codex /s

Output:
HKEY_CLASSES_ROOT\codex
URL Protocol REG_SZ
(默认) REG_SZ URL:codex

Repro steps:

1. Open Codex Desktop on Windows.
2. Go to Plugins.
3. Try to connect GitHub or Gmail.
4. Complete browser authorization.
5. Codex shows Electron "Error launching app" instead of completing OAuth.

Will the beta version released today solve the problem?

Not sure yet. The issue still reproduces on Windows Store version 26.527.3686.0.

If today’s beta contains a fix for Windows protocol activation / codex:// OAuth callbacks, it should be easy to verify:

1. Install the beta.
2. Run Win + R -> codex://test
3. Expected: Codex handles the URL without showing the Electron “Unable to find Electron app” dialog.
4. Then retry GitHub or Gmail OAuth.

Could you share the beta version number or confirm whether codex://test works on it?

Has anyone tried it with the beta version yet? I'm too lazy to install it and then have to delete it.

I am experiencing this exact issue when I try to connect plugins

I can also reproduce this on Codex 26.527.60818, Windows 11 24H2 build 26100.8457, ChatGPT Plus.

Same behavior:

• GitHub OAuth succeeds in browser
• Browser launches codex://oauth_callback
• Codex shows "Unable to find Electron app"
• Manual protocol test via codex://test also fails

Repair/reset/reinstall and manually adding HKEY_CLASSES_ROOT\codex\shell\open\command did not resolve it.

codex-oauth-callback-bug-redacted.zip

I’m seeing the same issue on Windows while connecting Microsoft Teams / Outlook connectors, not GitHub.

Codex Desktop package:

OpenAI.Codex_26.527.7698.0_x64__2p2nqsd0c76g0
Status: Ok
InstallLocation: C:\Program Files\WindowsApps\OpenAI.Codex_26.527.7698.0_x64__2p2nqsd0c76g0

Protocol association:

```HKCU\Software\Microsoft\Windows\Shell\Associations\UrlAssociations\codex\UserChoice
ProgId REG_SZ AppXybfp6cjpb1wf0pftw0fd4bz59gzn1401

The OAuth callback is launched correctly by Windows:

"C:\Program Files\WindowsApps\OpenAI.Codex_26.527.7698.0_x64__2p2nqsd0c76g0\app\Codex.exe" codex://connector/oauth_callback?code=REDACTED&state=REDACTED

But Codex shows:

Error launching app

Unable to find Electron app at:
...\oauth_callback?code=...

Cannot find module:
...\oauth_callback?code=...

This reproduces after:

Get-AppxPackage -Name OpenAI.Codex | Reset-AppxPackage
Add-AppxPackage -DisableDevelopmentMode -Register "C:\Program Files\WindowsApps\OpenAI.Codex_26.527.7698.0_x64__2p2nqsd0c76g0\AppxManifest.xml"

It looks like the Windows protocol handler invokes the right executable, but the Codex/Electron bootstrap treats the codex://connector/oauth_callback?... argument as an Electron app/module path instead of routing it as an OAuth callback.

I’m seeing the same Windows GitHub OAuth callback failure on a newer Codex build, so this appears to still be reproducible after May 30, 2026.

Environment:

• Codex app version: 26.601.2237.0
• Platform: Windows
• Install type: Microsoft Store package
• Workspace/projects on D:\, but Codex package is installed under C:\Program Files\WindowsApps

Observed behavior:

• GitHub auth completes in the browser
• Redirect to codex://oauth_callback?... triggers the Electron error dialog
• Error matches the existing reports: Unable to find Electron app / Cannot find module

Local diagnostics:

• AppxManifest.xml registers the codex protocol to app/Codex.exe
• Codex runtime metadata also points to separate binaries under %LOCALAPPDATA%\OpenAI\Codex\bin\...
• This makes it look like a Windows deep-link routing/dispatch problem rather than a D:\ workspace/install-location issue
• Still reproducible on 26.601.2237.0 as of 2026-06-03

Has anyone tried it with the beta version yet? I'm too lazy to install it and then have to delete it.

Hi everyone, I've updated to the new version, and this issue seems to have been resolved!

Yeah I'm discontinuing my subscription, I'm done subsidizing OpenAI while they give zero effort into their bug tracker. The users come together, provide info on these bugs and there's zero collaboration from OpenAI. Get fucked, lick my balls and suck my dick--bitch.

I’m seeing the same OAuth callback failure on Windows with the Gmail plugin.

Environment:

• Codex Desktop Windows version: 26.527.7698.0
• Platform: Windows x64
• Installed from Microsoft Store / WindowsApps package path
• Browser used for OAuth: Chrome
• Plugin: Gmail

Repro steps:

1. Open Codex Desktop on Windows.
2. Go to Plugins and connect Gmail.
3. Complete the Google OAuth consent flow in Chrome.
4. When Google redirects back to codex://oauth_callback?..., Codex shows an Electron launch error instead of completing the connector authorization.

Observed error:

Error launching app
Unable to find Electron app at C:\Program ...\oauth_callback?state=codex_scheme_oauth_s_...
Cannot find module 'C:\Program ...\oauth_callback?state=codex_scheme_oauth_s_...'

Additional diagnostics / attempted fixes:

• Reinstalled Codex.
• Re-registered the MSIX manifest with Add-AppxPackage -Register -DisableDevelopmentMode ...\AppxManifest.xml after fully closing Codex.
• Confirmed the package manifest declares the codex protocol.
• Tried manually registering codex: under HKCU\Software\Classes\codex, but launching the callback still caused Electron to treat oauth_callback?... as an app path, so the manual association was removed.
• The failure still happens after restarting Codex and repeating a fresh Gmail authorization flow.

This seems to match the existing codex://oauth_callback handling issue, but in this case it is blocking Gmail connector authorization rather than GitHub.

I'm able to use codex:// on Codex 26.601.21317 now.