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

Resolved 💬 2 comments Opened Jun 2, 2026 by VincentVonk Closed Jun 2, 2026

What version of the Codex App are you using (From “About Codex” dialog)?

26.527.60818

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What issue are you seeing?

Connecting GitHub from the Windows Codex Desktop App fails after successful GitHub authentication.

The browser successfully launches the Codex application using the codex:// protocol, but Codex fails to process the OAuth callback and displays an Electron startup error.

Full error shown by Codex:

Error launching app

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

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

The browser prompt before the error is:

This site is trying to open Codex.
https://chatgpt.com wants to open this application.

### What steps can reproduce the bug?

1. Open Codex Desktop App on Windows.
2. Go to Plugins → GitHub.
3. Click "Connect GitHub".
4. Complete GitHub authentication in the browser.
5. Browser displays: "This site is trying to open Codex".
6. Click "Open".
7. Codex opens/focuses, but then shows the Electron error dialog.

Environment:

- Codex version: 26.527.60818
- Windows 11 24H2
- OS Build: 26100.8457
- Architecture: x64
- Subscription: ChatGPT Plus



### What is the expected behavior?

After clicking "Open" in the browser prompt, Codex should receive and process the `codex://oauth_callback?...` URL and complete the GitHub connection successfully.

### Additional information

Additional diagnostics:

Windows recognizes the application as:

OpenAI.Codex_2p2nqsd0c76g0!App

Registry check:

HKEY_CLASSES_ROOT\codex exists

However:

HKEY_CLASSES_ROOT\codex\shell\open\command does not exist

The browser successfully invokes the codex:// protocol and launches Codex. The failure appears to occur when Codex processes the OAuth callback URL:

codex://oauth_callback?code=...

This looks like a Windows-specific OAuth callback / protocol handler issue. The callback URL appears to be interpreted as an Electron application/module path instead of being handled as an OAuth redirect.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗