Windows Codex App: Google plugin OAuth callback fails with "Unable to find Electron app" #25901

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

Codex App for Windows v[26.527.60818] Installed via Microsoft Store

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

When I try to install/connect the Google plugin in the Codex Windows app, the OAuth login appears to start normally in the browser. After completing the Google OAuth login, Codex fails to handle the redirect callback and shows:

"Error launching app"

"Unable to find Electron app at C:\Program
...\oauth_callback?state=codex_scheme_oauth_s_[REDACTED]&iss=..."

"Cannot find module 'C:\Program
...\oauth_callback?state=codex_scheme_oauth_s_[REDACTED]&iss=...'"

I redacted the OAuth callback values because they may contain session/correlation data.

What actually happens:
The Google login/approval flow completes in the browser, but the redirect back to Codex fails with an Electron app error. The Google plugin is not installed/connected.

Troubleshooting already tried:

• Restarted Codex.
• Retried the Google plugin installation.
• Checked that the browser login itself works.
• The issue appears to happen at the redirect/callback step, not during Google authentication itself.

Notes:

• Please let me know if there is a safe way to provide logs without exposing OAuth tokens, code, state, or personal account information.

What steps can reproduce the bug?

Steps to reproduce:

1. Open Codex App on Windows.
2. Go to plugins/apps/connectors.
3. Select the Google plugin.
4. Start the OAuth login flow.
5. Approve/sign in with Google in the browser.
6. Browser redirects to a codex://...oauth_callback... URL.
7. Codex fails to handle the callback and shows an Electron error.

What is the expected behavior?

What I expected:
After approving the Google OAuth login, the Codex app should reopen and complete the Google plugin installation.

Additional information

No response