Codex Desktop for macOS: allow disabling completion notifications for scheduled automations independently of normal turn notifications

Summary

Please add a way in Codex Desktop for macOS to suppress the app’s completion notification for scheduled automations without disabling normal desktop notifications for interactive turns.

Current behavior

Codex appears to use a global end-of-turn notification setting for the desktop app. In my local Codex config on macOS, this shows up as:

notify = ["/Users/.../SkyComputerUseClient", "turn-ended"]

That seems to cause a macOS notification when an automation thread finishes, even when the automation result is a no-op / no-change run.

Problem

For background monitors and recurring automations, this creates unnecessary notification noise:

• many automations complete successfully with nothing actionable
• users may still want notifications for interactive/manual Codex turns
• users may already have their own downstream alerting inside the automation itself (for example: iMessage, email, Slack, GitHub issue, etc.)

In other words, the current behavior makes "automation finished" look the same as "something needs my attention".

Requested behavior

Please provide one of these, in increasing order of flexibility:

1. A global desktop setting like:

• Notify on interactive turn completion
• Notify on scheduled automation completion

1. A per-automation setting or flag, for example:

• notify_on_completion = false
• suppress_desktop_completion_notification = true

1. A richer notification policy for automations, such as:

• notify only on failure
• notify only when blocked / needs approval
• notify only when the automation explicitly emits an inbox item or other user-facing result
• notify only on meaningful changes detected by the automation logic

Why this matters

Codex automations are especially useful for quiet background monitoring. A no-change hourly monitor should ideally stay silent unless:

• it found a meaningful change
• it failed
• it is blocked and needs user action

Right now, users have to choose between:

• keeping end-of-turn notifications enabled and getting noisy automation completion banners, or
• disabling notifications globally and losing useful notifications for normal interactive Codex work

Environment

• Product: Codex Desktop app
• Platform: macOS
• Use case: scheduled/recurring automations

Notes

I’m filing this as a feature request rather than a bug because the current behavior may be intentional, but the granularity is not sufficient for automation-heavy workflows.

If helpful, I can provide a concrete reproduction example using an hourly automation that intentionally sends its own iMessage alert only on meaningful changes, while the Codex desktop app still posts a macOS completion notification on every successful no-change run.