codex - 💡(How to fix) Fix Windows Codex Desktop notification click launches Electron with type=click&tag as app path

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Clicking a Windows toast notification from Codex opens an Electron error dialog instead of focusing/opening the Codex app. The Codex app itself can run normally; the failure is specific to clicking the Windows notification. The error dialog says: Error launching app 4. Observe the Electron "Error launching app" dialog.

  • New notifications can still reproduce the same type=click&tag=... error.

Code Example

Error launching app
Unable to find Electron app at C:\Program Files\WindowsApps\OpenAI.Codex_26.52...\type=click&tag=<notification-tag>

Cannot find module 'C:\Program Files\WindowsApps\OpenAI.Codex_26.52...\type=click&tag=<notification-tag>'
RAW_BUFFERClick to expand / collapse

What version of Codex App are you using?

26.527.3686.0

What platform is your computer?

Windows x64

What issue are you seeing?

Clicking a Windows toast notification from Codex opens an Electron error dialog instead of focusing/opening the Codex app. The Codex app itself can run normally; the failure is specific to clicking the Windows notification.

The error dialog says:

Error launching app
Unable to find Electron app at C:\Program Files\WindowsApps\OpenAI.Codex_26.52...\type=click&tag=<notification-tag>

Cannot find module 'C:\Program Files\WindowsApps\OpenAI.Codex_26.52...\type=click&tag=<notification-tag>'

This looks like the toast activation payload (type=click&tag=...) is being appended/interpreted as an Electron app path rather than being handled as notification activation data.

Steps to reproduce

  1. Install/run Codex Desktop for Windows from the Microsoft Store package.
  2. Wait for a Codex Windows toast notification.
  3. Click the notification in the bottom-right toast/notification center.
  4. Observe the Electron "Error launching app" dialog.

Expected behavior

Clicking a Codex notification should focus/open Codex and route to the relevant conversation/message, or at minimum do nothing gracefully. It should not launch Electron with the notification click payload as an app path.

Troubleshooting already attempted

  • Verified the AppX package is installed and Codex launches normally.
  • Verified the AppUserModelID is OpenAI.Codex_2p2nqsd0c76g0!App.
  • Cleared Codex notification history.
  • Attempted AppX re-registration, but it was blocked while Codex background processes were still running.
  • New notifications can still reproduce the same type=click&tag=... error.

Additional information

This report intentionally omits local usernames, local file paths outside the standard WindowsApps package path, notification tag values, screenshots, and machine-specific identifiers.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Clicking a Codex notification should focus/open Codex and route to the relevant conversation/message, or at minimum do nothing gracefully. It should not launch Electron with the notification click payload as an app path.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING