Windows Codex app deep link / OAuth callback fails: "Unable to find Electron app"

[dnl2052]

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

26.527.3686.0

What subscription do you have?

Pro

What platform is your computer?

Windows

What issue are you seeing?

Description:
On Windows, Codex desktop app opens and Codex CLI works, but browser OAuth callbacks fail when signing in or connecting the Figma MCP plugin.

What happens:

• Browser login succeeds and shows localhost:1455/success
• Browser/Windows tries to open Codex
• Error appears: "Unable to find Electron app"
• Error path references:
  C:\Program Files\WindowsApps\OpenAI.Codex_26.527.3686.0_x64__2p2nqsd0c76g0\app\codex...\new
• Same issue happens when connecting Figma MCP in Codex Plugins.

Environment:

• Windows
• Codex App version: 26.527.3686.0
• Codex CLI version: 0.135.0
• Browser: Microsoft Edge
• Package:
  OpenAI.Codex_26.527.3686.0_x64__2p2nqsd0c76g0

Already tried:

• Reset Codex app from Windows settings
• Restarted Windows
• Get-AppxPackage OpenAI.Codex | Reset-AppxPackage
• Logged out/in
• Installed Codex CLI
• Figma plugin authorization reaches browser but callback back to Codex fails

Expected:
Browser OAuth/deep link should return to the Codex desktop app and finish login/plugin setup.

What steps can reproduce the bug?

Feedback ID: no-active-thread-019e764f-97a0-7920-86ba-64c17e9675cb

What is the expected behavior?

No response

Additional information

No response

[github-actions]

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

• Codex Desktop Windows: connector OAuth "Open in Codex" opens Electron error instead of completing callback #25157

Powered by Codex Action

[sined-rahkuk]

I'm seeing the same Windows/AppX deep-link failure on Codex App 26.527.3686.0, with a separate reproduction path from Linear's "Open in -> Codex desktop" integration.

Environment:

• Windows 11
• Codex App: 26.527.3686.0
• Package: OpenAI.Codex_26.527.3686.0_x64__2p2nqsd0c76g0
• Codex CLI: 0.130.0-alpha.5
• Workspace path: C:\Users\kukha\Desktop\saiden.ai
• Linear desktop app is installed and its own protocol association looks normal: "C:\Users\kukha\AppData\Local\Programs\Linear\Linear.exe" "%1"

Repro from Linear:

1. In Linear desktop, right click an issue.
2. Choose Open in -> Codex desktop.
3. Windows/Electron shows an error dialog:
   • Error launching app
   • Unable to find Electron app at C:\Program ...?prompt=Work%20on%20Linear%20issue...
   • Cannot find module 'C:\Program ...?prompt=Work%20on%20Linear%20issue...'

Additional local checks:

• codex://new?prompt=...&path=C%3A%5CUsers%5Ckukha%5CDesktop%5Csaiden.ai also fails the same way.
• Directly starting the packaged app with a project path / --open-project produced the same class of error, where Electron treated C:\Users\kukha\Desktop\saiden.ai as the Electron app path/module.
• Extracting the app bundle showed code paths that appear to parse codex://new?... and path, so this looks like the Windows/AppX/Electron activation path is passing the URL/path to Electron before the app's own deep-link parser can handle it.

Impact:
Linear's Codex Desktop integration can't create/open a desktop thread on Windows. We had to fall back to a workaround that opens Codex Desktop without args and copies the Linear prompt to the clipboard.

This is especially relevant for teams running the desktop app on Windows now and migrating agent execution into WSL later: the failure happens before workspace runtime choice matters, so WSL doesn't avoid it.