Windows approval/action callback launches Codex.exe with raw type=action argument and triggers Electron "Unable to find Electron app" error

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

• #25616
• #25756
• #25734
• #25822
• #25786

Powered by Codex Action

Additional repro/details from another affected Windows user.

This is affecting more than one connector/app, not just the original report:

• ClickUp connector OAuth fails in Codex Desktop on Windows.
• HubSpot connector OAuth also failed on another device.
• The failure mode is the same Electron dialog: Error launching app, Unable to find Electron app, and Cannot find module under the Codex WindowsApps package path.

Environment from the ClickUp repro:

Codex app package: OpenAI.Codex_26.527.7698.0_x64__2p2nqsd0c76g0
Codex app version: 26.527.7698.0
Package family: OpenAI.Codex_2p2nqsd0c76g0
Install location: C:\Program Files\WindowsApps\OpenAI.Codex_26.527.7698.0_x64__2p2nqsd0c76g0
Windows product: Windows 10 Pro
OS architecture: 64-bit
OS HAL/build shown locally: 10.0.26100.1

ClickUp plugin was installed and enabled locally:

[plugins."clickup@openai-curated"]
enabled = true

ClickUp plugin manifest maps to a Codex app connector:

{
  "apps": {
    "clickup": {
      "id": "asdk_app_69431e6d26b88191b4029488aeb42f5b"
    }
  }
}

Local protocol state after reverting experiments:

HKEY_CURRENT_USER\Software\Classes\codex
    (Default)    REG_SZ    URL:codex
    URL Protocol    REG_SZ

AppX package URL association exists:

HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\Repository\Packages\OpenAI.Codex_26.527.7698.0_x64__2p2nqsd0c76g0\App\Capabilities\URLAssociations
    codex    REG_SZ    AppXybfp6cjpb1wf0pftw0fd4bz59gzn1401

AppxManifest.xml registers:

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

The installed app bundle contains the app-connect OAuth callback URL:

codex://connector/oauth_callback

What was tried locally:

1. Confirmed clickup@openai-curated is enabled in C:\Users\User\.codex\config.toml.
2. Confirmed ClickUp plugin files exist under C:\Users\User\.codex\plugins\cache\openai-curated\clickup\90718987.
3. Confirmed no ClickUp tools were exposed through Codex tool discovery after the OAuth attempt, consistent with auth never completing.
4. Checked registry protocol state for codex:.
5. Tried AppX re-registration with Add-AppxPackage -DisableDevelopmentMode -Register <Codex AppxManifest.xml>, but it failed while Codex was running with HRESULT: 0x80073D02 / resources in use.
6. Tried adding a direct HKCU\Software\Classes\codex\shell\open AppX delegate handler copied from the package AppX protocol ProgID. Result: still produced the Electron Unable to find Electron app / Cannot find module dialog.
7. Tried a PowerShell protocol shim registered as the codex: handler that receives %1 and relaunches Codex.exe with the full codex://... URL. Result: still produced the Electron dialog.
8. Tried updating the shim to launch Electron with the app bundle path first: Codex.exe <install>\app\resources\app.asar <codex://...deep-link>. Result: still did not complete the connector connection, and more Electron launch errors appeared.
9. Reverted the registry override and removed the shim. No local workaround remains active.

Current conclusion: this appears to be an upstream Codex Desktop Windows/MSIX protocol activation bug. The callback URL or callback query is being placed where Electron expects an app/module path, before Codex app JavaScript can route it as a deep link. Local registry changes were not sufficient and can make the error appear more often.

Potential fix directions:

• Ensure Windows protocol activation launches the packaged app with the actual app bundle/path first, never the callback URL/query in Electron's app-path slot.
• Normalize Windows second-instance/protocol args so codex://connector/oauth_callback?... reaches the existing connectorOAuthCallback handler.
• Consider an HTTPS localhost callback fallback for connector OAuth on Windows while codex:// activation is broken.

Not getting this error anymore. Maybe fixed.