Built-in sound notification for interactive turn completion
Resolved 💬 3 comments Opened Feb 22, 2026 by mark0011astra Closed Apr 3, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
What variant of Codex are you using?
CLI
What feature would you like to see?
Summary
Please add a first-class, built-in sound notification for interactive mode when an assistant turn is completed.
Motivation
In interactive Codex sessions, users often switch to other windows while waiting for responses.
A completion sound improves workflow and reduces idle checking.
Current workaround
I currently use config-based command notifications:
notify = ["sh", "-lc", "afplay /System/Library/Sounds/Glass.aiff >/dev/null 2>&1 || printf '\\a'"]
[tui]
notifications = ["agent-turn-complete"]
This works, but it is not ideal.
Problems with the workaround
- Platform-specific (
afplayis macOS-specific). - Requires shell command knowledge.
- Easy to misconfigure.
- Not obvious to discover for new users.
- No unified built-in UX across macOS/Linux/Windows.
Proposed solution
Add a native option for sound-on-completion in interactive mode, for example:
- CLI flag:
--sound-on-turn-complete - Config option:
[tui] sound_on_turn_complete = true
Optional extension:
- configurable sound profile/path
- fallback to terminal bell when native sound is unavailable
Expected behavior
When agent-turn-complete occurs in interactive mode, Codex plays one notification sound.
Environment
- Codex CLI:
0.104.0 - Platform: macOS (arm64)
Additional information
_No response_
3 Comments
The TUI already provides a couple of notification mechanism here.
You can use the
tui.notificationmechanism to configure either anosc9orbeloutput. If your terminal supports anosc9escape character, that will map to an OS-level toast, which you can typically configure to play any sound you'd like. If your terminal doesn't supportosc9, then you can still use a genericbelsound.If you are running the cli locally, you can also use the
notifyhook to play a sound, as you noted in the "workaround" section above. This will not work if you're running remotely.Any notification mechanism we use needs to work cross platform, with local and remote, and with a wide variety of terminal emulators. That limits our choices here.
This feature request hasn't received enough upvotes, so closing.