Additional Windows 11 repro for #25157: OpenAI Platform connector OAuth callback opens Electron error

Open 💬 3 comments Opened May 30, 2026 by hiqimazi-art

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Summary

Additional reproduction for #25157 on Windows: Codex Desktop connector OAuth callback fails when connecting the OpenAI Developers plugin's OpenAI Platform connector. The same user reports that adding any new OAuth-based Codex plugin/connector currently hits this callback failure, even after reinstalling.

This appears to be the same Windows codex://oauth_callback protocol handling issue where the OAuth callback URL is interpreted as an Electron app path instead of being delivered to the running Codex app.

Environment

Codex Desktop: OpenAI.Codex version 26.527.3686.0
Install type: Microsoft Store / MSIX package (OpenAI.Codex_2p2nqsd0c76g0)
OS: Windows 11 Pro, version 10.0.22631, x64
Plugin: openai-developers version 1.1.0
Connector/app: OpenAI Platform (connector_2de447f3f15448ebab48783d7e4f5d81)
Locale/UI observed in Chinese Windows/Codex environment

Steps to reproduce

Open Codex Desktop on Windows.
Go to Plugins > OpenAI Developers.
Click the OpenAI Platform action to create/connect an OpenAI API key for a project.
Complete the browser authorization flow.
Browser redirects back to Codex via the OAuth callback.
Codex shows a Windows/Electron error dialog instead of completing the connector connection.

Actual behavior

The callback fails with an Electron dialog. The OAuth code is redacted below:

Error launching app

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

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

The connector tool is then not exposed in the Codex thread. For example, after attempting to connect OpenAI Platform, tool discovery still does not expose the expected encrypted API key creation tool, so the OpenAI API key flow remains blocked.

Expected behavior

Codex Desktop should receive the OAuth callback through the codex:// protocol handler, route it to the running app, complete connector authentication, and expose the OpenAI Platform connector tools to the thread.

Additional observations

The OpenAI Developers plugin itself is installed and its skill files are present locally.
The plugin manifest maps openai-platform to connector ID connector_2de447f3f15448ebab48783d7e4f5d81.
Reinstalling does not appear to resolve the callback failure.
The user reports this is affecting all newly added Codex plugins/connectors that require the same OAuth callback flow.

Related existing issue: #25157

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 3 months ago

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

#25157
#25203
#25188
#25248

Powered by Codex Action

Servietrix · 2 months ago

Additional reproduction from another Windows Codex Desktop user.

Observed behavior:

In Codex Desktop, launching the OpenAI Developers app's OpenAI Platform connector fails during the OAuth/app launch flow.
Error dialog says:

Error launching app

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

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

Environment details observed locally:

Codex Desktop package path includes C:\Program Files\WindowsApps\OpenAI.Codex_26.527.3686.0_x64__2p2nqsd0c76g0
OpenAI Developers plugin version: 1.1.0
OpenAI Platform connector ID in plugin manifest: connector_2de447f3f15448ebab48783d7e4f5d81
The user tried updating/relaunching/repair-style troubleshooting and still cannot use the embedded OpenAI Platform app from Codex.

Impact: user specifically wants to use the OpenAI Platform connector inside Codex, not just open platform.openai.com externally, so the current workaround does not satisfy the workflow.

justinburgess · 2 months ago

Workaround found - use chatgpt windows app or browser app to add plugin