codex - 💡(How to fix) Fix Codex Desktop Windows: connector OAuth "Open in Codex" opens Electron error instead of completing callback

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

OpenAI.Codex_26.527.3378.0_x64__2p2nqsd0c76g0

What subscription do you have?

ChatGPT Pro ($200/month)

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64 (Windows 11 Pro)

What issue are you seeing?

Codex Desktop on Windows fails to complete connector OAuth after browser login. When authenticating Codex connectors and clicking "Open in Codex" in the browser, Windows opens an Electron error dialog instead of returning the OAuth callback to the running Codex app.

This is a Codex Desktop/App protocol callback issue, not a Codex CLI issue.

Observed with:

• OpenAI Developer plugin connection
• Supabase connector connection
• Browser used for the login flow: Brave

Actual error dialog:

Error launching app

Unable to find Electron app at C:\Program
...\oauth_callback?code=[REDACTED]

Cannot find module 'C:\Program
...\oauth_callback?code=[REDACTED]'

Local investigation:

• The installed MSIX package is OpenAI.Codex_26.527.3378.0_x64__2p2nqsd0c76g0.
• AppxManifest.xml registers the codex protocol with executable app/Codex.exe.
• The Electron error text matches Electron's default app loader path for "Unable to find Electron app", suggesting the codex://...oauth_callback?... activation URL is being interpreted as an Electron app path / first positional argument before the packaged Codex app handles it.

What steps can reproduce the bug?

1. Open Codex Desktop on Windows.
2. Start connecting a connector or plugin that uses browser OAuth, such as the OpenAI Developer plugin or Supabase connector.
3. Complete the browser login flow.
4. Click "Open in Codex" in the browser.
5. Observe that an Electron "Error launching app" dialog opens instead of Codex completing the connector authentication.

What is the expected behavior?

Codex Desktop should receive the codex://...oauth_callback... protocol activation URL, route it to the running app, and complete connector authentication.

The OAuth callback URL should not be interpreted as an Electron application path.

Additional information

A redacted screenshot is attached showing the Electron dialog. The OAuth code= value has been fully redacted before sharing.

I searched existing openai/codex issues for the exact error text and related terms, including:

• Unable to find Electron app
• Error launching app
• oauth_callback
• Open in Codex

• codex://
• protocol handler
• Supabase connector OAuth
• OpenAI Developer connector OAuth

I found related Codex Desktop OAuth reports, but not this specific Windows protocol callback failure where the OAuth callback is treated as an Electron app path.