[macOS Desktop] Blocking final question is marked completed and triggers completion hooks

Codex app version

26.820.60940 (7119)

Subscription

Not confirmed / unknown

Environment

• macOS (Darwin 25.0.0)
• Apple Silicon (arm64)
• Codex Desktop app

Actual behavior

When the assistant's final response asks the user for a required confirmation before work can continue, the task is shown as successfully completed:

• The task indicator turns green instead of showing an awaiting-input / needs-attention state.
• The completion hook fires.
• No separate user-input-required or needs-attention signal is emitted.
• A local controller that consumes Codex task/hook state therefore also reports the task as completed.

This makes the required confirmation effectively invisible unless the user manually opens and reads the task.

Steps to reproduce

1. Start a task that includes an external write, such as saving a private diary entry.
2. Reach a point where the write cannot proceed without explicit user confirmation.
3. Have the assistant end its turn with a blocking question asking the user to confirm.
4. Observe the task in the Codex Desktop UI.
5. Observe any configured task lifecycle hooks.

In the observed case, the assistant correctly asked for confirmation, but the UI turned green and only the completion hook ran.

Expected behavior

If the assistant's final response requires a user reply before the requested work can continue:

• The task should be classified as awaiting user input / needs attention, not completed.
• The UI should use the attention-required state rather than the green success state.
• A completion hook should not fire until the requested work is actually finished.
• Hook consumers should receive an explicit input-required/attention-required state or event.

Impact

Users can miss blocking confirmation requests because every visible and machine-readable status says that the task has finished. External controllers and automations cannot distinguish a successful completion from a task that is waiting for the user.

Related issues

• #35947 — blocking approval events are not surfaced with consistent actionable notifications
• #27352 — a turn is marked complete while follow-up work is still needed
• #20817 — distinction between awaiting user input and recently completed tasks

This appears related, but the specific failure here is that a blocking question in the assistant's final response produces a green completed state and completion hook. No private diary content or account data is included in this report.