Windows Codex app fails to handle codex:// protocol links

Open 💬 1 comment Opened Jun 2, 2026 by eturo47

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

  • OS: Windows - Codex package: OpenAI.Codex_26.527.7698.0_x64__2p2nqsd0c76g0 - Codex version: 26.527.7698.0 - Install source/signature: Microsoft Store / Store-signed MSIX

What subscription do you have?

Free

What platform is your computer?

OS: Microsoft Windows 11 Enterprise, version 10.0.26200, build 26200, x64 CPU: AMD Ryzen 7 9800X3D 8-Core Processor

What issue are you seeing?

Issue:
The Windows Codex desktop app fails when launched via the codex:// protocol. This breaks GitHub authorization callback and local wake/deep-link flows.

What steps can reproduce the bug?

Steps to reproduce:

  1. Install/open Codex on Windows.
  2. Open PowerShell.
  3. Run:

Start-Process "codex://test"

What is the expected behavior?

Expected behavior:
Codex should open or focus the existing Codex window and handle the codex:// URL internally.

Additional information

Actual behavior:
An Electron error dialog appears:

Error launching app
Unable to find Electron app at C:\Program Files\WindowsApps\OpenAI.Codex_26.527.7698.0_x64__2p2nqsd0c76g0\app\c...\test

Cannot find module 'C:\Program Files\WindowsApps\OpenAI.Codex_26.527.7698.0_x64__2p2nqsd0c76g0\app\c...\test'

Impact:

  • GitHub authorization cannot complete because the browser callback to Codex fails.
  • Local wake/deep-link actions fail for the same reason.

Troubleshooting already attempted:

  • Verified installed package is current user package:

OpenAI.Codex_26.527.7698.0_x64__2p2nqsd0c76g0

  • Re-registered AppX manifest with Add-AppxPackage -DisableDevelopmentMode -Register.
  • Confirmed codex:// is registered as a Windows.Protocol AppX association.
  • Confirmed the old stale package path issue is gone; the current failure now points to the installed 26.527.7698.0 package.
  • The error suggests Electron is treating the codex:// URL as an application path instead of passing it to the Codex app protocol handler.

Request:
Please investigate the Windows MSIX/AppX protocol activation behavior for codex:// links. It appears the app is launched through Electron’s default app loader rather than the packaged Codex app entry, causing the deep link URL to be interpreted as an app path

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗