codex - 💡(How to fix) Fix Codex Desktop on Windows: notification Approve button dismisses toast but does not accept approval

What variant of Codex are you using?

Codex Desktop from the Microsoft Store / WindowsApps install.

What version of the Codex App are you using?

Observed on Codex Desktop 26.506.3741.0 with bundled CLI / command runner 0.130.0-alpha.5.

What platform is your computer?

Windows 11 x64.

What issue are you seeing?

When Codex Desktop shows a Windows desktop notification for a permission/approval request, clicking the notification's Approve button only dismisses the toast. The approval is not actually accepted in Codex, and the user still has to return to the Codex UI and click Approve there.

This makes the notification action look like it worked, but the blocked tool call remains blocked until the in-app approval button is clicked.

Steps to reproduce

1. Open Codex Desktop on Windows.
2. Trigger any command/tool action that requires approval.
3. Wait for the Windows desktop notification/toast with approval actions to appear.
4. Click Approve in the Windows notification.
5. Return to Codex Desktop.

Expected behavior

Clicking Approve in the Windows notification should accept the pending approval, exactly as clicking Approve in the Codex UI does.

Actual behavior

The Windows notification disappears, but the approval is not accepted. Codex remains waiting for the user to approve in the UI.

Local evidence

Desktop logs show the permission notification being displayed with actions, for example:

[desktop-notifications] show notification actionCount=3 kind=permission notificationId=approval-local-59

However, after clicking Approve in the Windows notification, there is no corresponding log entry like:

[desktop-notifications] notification action ...

By contrast, normal notification body clicks do log notification click open, so the desktop notification plumbing is partially working. It looks like the Windows toast action callback is not being delivered or handled for approval actions.

Additional context

I inspected the packaged app code path and found the desktop notification handler maps Electron notification action events to the approval callback by action index. The observed logs suggest that the action event is never reaching the app for the Windows toast button click, even though the toast is dismissed by Windows.

A possible fix would be to ensure Windows notification action callbacks are registered/handled correctly for packaged Codex Desktop notifications, or to make the notification action open/focus Codex and execute the corresponding in-app approval as a fallback.