Desktop app: completion notification config appears ignored in app-server mode

Open 💬 2 comments Opened Feb 27, 2026 by flutterrausch
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Summary

In Codex Desktop (com.openai.codex), I cannot reliably get a single completion ding per finished request.

notify and [tui].notifications settings are accepted in config, but appear to have no effect in Desktop app sessions (app-server mode).

Environment

  • Date observed: 2026-02-27
  • codex-cli: 0.106.0
  • Codex Desktop: 26.226.940
  • macOS: 26.3 (Darwin 25.3.0)

Config

~/.codex/config.toml:

notify = ["zsh", "/Users/ingo/Developer/dotfiles/ai/notify_log_codex.zsh"]

[tui]
notification_method = "bel"
notifications = ["agent-turn-complete"]

Repro

  1. Set notify to a logging hook.
  2. Verify the script itself works manually (stdin and argv payloads log correctly).
  3. Run turns in Codex Desktop app.
  4. Check ~/.codex/notify-debug.log.

Expected

  • Completion notification once per finished request (or at least documented event behavior).
  • If notify is unsupported in Desktop/app-server mode, emit a warning.

Actual

  • No hook invocations from Desktop turns.
  • No audible completion ding.
  • Log file only changes during manual script tests.

Evidence

  • Desktop log shows notifications service startup, e.g.:
  • [desktop-notifications] service starting
  • But no matching hook payload delivery/notify execution.

Request

  1. Clarify supported notification settings for Desktop app-server mode.
  2. Add a supported “notify on turn complete” option in Desktop app.
  3. Add warning when unsupported config keys (e.g. CLI-only notification knobs) are set.

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 6 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #13020

Powered by Codex Action

etraut-openai contributor · 6 months ago

The tui.notifications setting is specific to the TUI (terminal user interface), so it doesn't apply to the desktop app or extension.

The desktop app has its own notification mechanism. You can enable it in the app's Settings panel.

The notify hook should run with the app, but the app's notification mechanisms are easier to configure, so I recommend using that if it meets your needs.