Hi Codex team,
I’d like to suggest an optional feature for the macOS Codex app: audio cues that reflect the current state of a task.
I know there are already related requests about completion notifications and sounds when user input is needed. What I’m suggesting here is a broader idea: not just a single alert at the end, but a lightweight audio state system that helps users understand what Codex is doing without having to keep watching the screen.
The idea
Codex could optionally use sound in three distinct ways:
-
While Codex is actively working, play a subtle, neutral ambient background sound.
-
As soon as Codex pauses and is waiting for user input (for example, clarification, confirmation, approval, or any other action), stop the sound.
-
When the task is fully completed, optionally play a short completion sound, such as a soft gong or chime.
Why this would be useful
One of the main friction points with long-running agent tasks is that the user still has to keep checking the app to understand what state the task is in.
This feature could reduce that friction in a very practical way.
It would help users:
-
stay focused while Codex is working;
-
avoid repeatedly glancing back at the app;
-
switch to other work more comfortably;
-
step away from the computer without worrying about missing the moment when Codex pauses or finishes.
So this is not mainly about adding “music” for aesthetic reasons. It is more about passive awareness of agent state.
Why ambient sound may be better than a simple notification
A single notification at the end is useful, but it only solves one moment in the workflow.
An ambient working sound would communicate something more continuous:
Codex is still actively doing the job.
The moment the sound stops, the user immediately understands that something changed — most likely Codex is now waiting for input or can no longer proceed.
That makes the interaction feel more natural and less dependent on constant visual monitoring.
Important detail: this should be fully optional
This would only make sense as a configurable feature.
For example:
-
ambient audio: on/off
-
completion sound: on/off
-
separate sound for “waiting for input”: on/off
-
volume control
-
possibly a choice between a few sound styles
Some users would love this, others would never enable it — so giving users control would be essential.
Why this feels especially relevant for Codex
Codex is particularly well suited for this kind of feature because many tasks are not instantaneous. They may take time, involve multiple steps, or require occasional input from the user.
That creates a real need for background status awareness.
A good audio layer could make Codex feel more usable during long sessions, especially for people who want to keep working on other things while the agent is running.
Thanks for considering this idea.
If other users feel the same, I’d be curious to know which audio cues would feel most useful in real workflows 