macOS: completion notification click is received but does not open its conversation (26.915.31029)

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

ChatGPT desktop with Codex: 26.915.31029, build 9771, bundle com.openai.codex.

The version was read from the installed application's bundle metadata. The problem was also reported on 26.908.70816, build 9275. Installing the newer official download and restarting the application did not resolve the user's notification-click test.

What subscription do you have?

Account and subscription details are intentionally omitted from this public report.

What platform is your computer?

• macOS 26.6.2, Apple Silicon.
• uname -mprs: Darwin 25.6.0 arm64 arm.

What issue are you seeing?

Clicking a native macOS task-completion notification does not open the conversation associated with that notification. The application receives the click, but the user reports that the expected conversation is not displayed.

This report concerns the native turn-complete notification, not a Pet activity item or an approval button. It is a navigation failure, not merely a missing notification.

What steps can reproduce the bug?

User-performed test workflow:

1. Start a Codex turn in conversation A.
2. While the turn runs, switch to another conversation and put the desktop app in the background.
3. Wait for A's native completion notification.
4. Click that notification.
5. Check whether the application opens conversation A.

The user reports that the last step fails, including after the official application update and restart. This is not claimed to be independently reproduced by UI automation: the available automation tool explicitly blocks controlling the ChatGPT application itself.

What is the expected behavior?

Clicking a completion notification should activate the application and open the exact conversation that produced the notification, even when another conversation was previously selected.

Additional information

The installed application's log confirms this event sequence for the same conversation and turn. Identifiers have been removed; these are selected excerpts, not a complete raw log:

[desktop-notifications] show turn-complete conversationId=<redacted> turnId=<redacted>
[desktop-notifications] forward show kind=turn-complete notificationId=<redacted>
[desktop-notifications] show notification actionCount=0 kind=turn-complete notificationId=<redacted>
[desktop-notifications] emit action actionId=none actionType=open notificationId=<redacted>
[desktop-notifications] notification click open notificationId=<redacted>

The click was logged approximately 1.5 seconds after the notification was shown. Subsequent log entries show the primary window focused. This establishes receipt of the click, but does not by itself prove that navigation succeeded; the failed navigation is the user's direct observation.

Two further observations are not established causes:

• Shortly after the click, the renderer logged ResizeObserver loop completed with undelivered notifications. The same message also occurs outside that click, so correlation is insufficient to establish causation. The term “notifications” in this message refers to ResizeObserver, not necessarily macOS notification delivery.
• At startup, a separate warning said Failed to register macOS push notifications, AbortError, Authenticated workspace changed. Its relationship to this local completion-notification navigation failure is unknown.

The installed application retains the official OpenAI signature, and codesign --verify --deep --strict passes. The process receiving the click runs from the installed application, not from the mounted installer. No application patch or permission reset was applied during this updated-build test.

actionCount=0 refers to additional action buttons; it is not evidence that a conversation identifier is missing. The root cause remains undetermined.

Related, but different-scope reports: #38932 (Pet activity navigation) and #44730 (ResizeObserver errors/input lag). Please advise whether the native completion-notification routing failure has a supported workaround or a fix.

No conversation contents, session IDs, account identifiers, private paths, screenshots, or full logs are attached.

Start by tracing the native turn-complete notification click path from the logged “notification click open” event through primary-window focus and conversation navigation. Reproduce with conversation A running while another conversation is selected, then verify that clicking the notification opens A; the issue is fixed when this works reliably on the reported macOS setup.