CLI: queued async questions do not emit notifications; only turn completion alerts appear

Version

Codex CLI 0.154.0.

Problem

Asynchronous questions appear in Queued follow-up inputs, but no desktop notification appears when the question arrives. A notification appears when the agent finishes its turn and contains the final response instead.

That completion notification can be mistaken for a delayed question notification. Users may miss pending questions while working elsewhere.

Steps to reproduce

1. Enable TUI notifications, including notifications regardless of terminal focus, and restart Codex.
2. In a session with asynchronous questions available, have the agent call request_user_input_async and keep its turn running without sending a final reply.
3. Switch away from the session and observe whether a notification appears when the question is queued.
4. Let the agent finish its turn and compare the notification timing and contents.

Observed behavior

In manual testing, no question-arrival notification appeared during a two-minute observation window. The subsequent notification contained the agent’s final reply, not the pending question.

Expected behavior

A newly queued asynchronous question should request a notification when it arrives, even if the agent continues working. The notification should identify the pending question and respect the configured notification and terminal/OS policies.

Source investigation

The matching public release source suggests a missing notification call:

• add_async_questions adds the questions and refreshes the preview without calling the notification handler.
• The foreground user-input handler explicitly calls notify(Notification::PlanModePrompt { title }).
• Turn-completion notification rendering uses the final response, matching the observed notification contents.

This is source inspection and manual reproduction, not a tested patch. The scope across terminals and operating systems has not been established.

Related: #42433 reports missing notifications for inline questions in the desktop app. This report concerns the CLI/TUI path.

Start in codex-rs/tui/src/chatwidget/questions.rs at add_async_questions and compare its notification behavior with the foreground user-input handler in tool_requests.rs. Read notifications.rs to understand the existing completion notification, then reproduce the queued-question flow with TUI notifications enabled. Done means a newly queued async question produces the intended notification under the configured terminal and OS policies without confusing it with turn completion.