Task notification opens Codex app without showing the originating ChatGPT conversation

Reported behavior

A user reports receiving a desktop notification for a ChatGPT scheduled task. Clicking the notification opens the Codex desktop app, but the task result / originating conversation is not visible there. The user cannot locate the notified message in the app.

This report is submitted by the assistant at the user's explicit request. The notification click behavior is user-reported; the assistant has not independently reproduced it or inspected desktop routing logs.

Reported steps

1. Have an existing ChatGPT scheduled task associated with a web conversation.
2. Receive a desktop notification for the task.
3. Click the notification.
4. The Codex app opens, but the corresponding conversation and notified message are not displayed.

Expected behavior

The notification should open the exact originating conversation and task result in a surface that can display them. If the desktop app cannot display that conversation type, it should open the corresponding web conversation or offer an explicit browser fallback rather than leaving the user at an unrelated app view.

Verified task-side information

The task-management interface returns an existing conversation_id for the affected task. This confirms a configured conversation destination, but does not prove successful delivery of this particular notification's message. No private conversation IDs, task instructions, account details, or logs are included in this public report.

Possible investigation area

Cross-surface notification deep-link routing and conversation availability between ChatGPT web and the Codex desktop app. This is a hypothesis, not an established root cause. Please route to the appropriate ChatGPT / desktop notifications team if this tracker does not own it.

Environment limitations

Reported on September 19, 2026. Exact desktop app version, notification payload, and installed OS version have not been collected. No claim is made that changing a task prompt can repair this client-level behavior.

Start with the desktop notification click path, the notification payload, and the task-management interface's conversation_id; collect the missing app version, OS, and routing logs before narrowing ownership. Done means the notification opens the originating conversation and task result, or provides an explicit web fallback when the Codex app cannot display that conversation type.