Hello Codex developers and community,
I would like to suggest adding an optional sonic identity to Codex: a small set of original electronic sounds associated with important workflow events.
Before describing the idea, I would be interested to hear from other users:
Would a distinctive completion sound be useful when you leave Codex working in the background and switch to another tab, application, or project? Which Codex events would you personally want to receive an audio notification for?
The most important event, in my opinion, is task completion. Codex may work on a task for quite some time, while the user continues working elsewhere. It is easy to miss the moment when the task has already been completed or when Codex is waiting for further input.
A short, recognizable completion sound would solve this problem. Ideally, it should not be a generic browser notification or system beep, but an original Codex sound that gradually becomes associated with successful task completion.
Other useful sound events could include:
- a message or instruction was sent to the AI;
- a task was completed successfully;
- user input or approval is required;
- generation failed or the task stopped;
- the available token budget is running low;
- the token limit has been reached.
I implemented a similar system in my own AI project, using short and slightly playful electronic sounds for sending a message, generation errors, low token balance, and exhausted tokens.
In practice, this turned out to be both enjoyable and genuinely useful. The interface feels more responsive, while the user can understand what is happening without constantly returning to the active tab.
The feature could include:
- a global mute switch;
- separate controls for each event type;
- adjustable volume;
- an option to enable only important notifications;
- short and unobtrusive sounds suitable for prolonged work;
- browser notifications as an optional complement to audio.
This would not be sound decoration alone. It would combine a practical notification system with a recognizable Codex sonic identity.
I would be interested to know whether other users would find this useful and which events should have their own sounds.
Evgeny Monakhov
ceo
voscom.online