Set beeping OFF by default

Resolved 💬 4 comments Opened Feb 2, 2026 by sator-imaging Closed Feb 2, 2026

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What feature would you like to see?

In latest update (v0.93.0), Codex beeps when a work finished. It is so annoying me. Please set it to OFF by default. Thanks.

(OR beep only when the task takes 10 mins or more)

Additional information

WSL on windows.

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 6 months ago

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

#8399
#9672
#9093

Powered by Codex Action

etraut-openai contributor · 6 months ago

Beeping is off by default. You must have it enabled in your config.toml file. Look for a line that looks like notifications = [<events>] and delete it.

sator-imaging · 6 months ago

@etraut-openai

Thank you for reply.
I have reviewed file but no notifications = ... line.

Here is snippet from my config.toml containing 'notice'. something went wrong?

windows_wsl_setup_acknowledged = true

[notice]
hide_gpt5_1_migration_prompt = true
"hide_gpt-5.1-codex-max_migration_prompt" = true

[notice.model_migrations]
"gpt-5.1-codex-max" = "gpt-5.2-codex"

# (reference taken from web; commented out)
##notify = ["bash", "-lc", "afplay /System/Library/Sounds/Glass.aiff"]

etraut-openai contributor · 6 months ago

I misspoke above. Notifications are on by default. They are delivered when the terminal us not focused.

If you want to disable notifications for specific events, you can do so with the tui.notifications config setting.

[tui]
notifications = ["agent-turn-complete", "approval-requested"]

If you want to disable notifications for all events, use:

[tui]
notifications = []

Notifications have been enabled by default for a long time. Most users prefer receiving notifications, so this is a reasonable default. There was previously some special-case code for WSL that we removed, so it now works consistently with non-WSL environments and platforms. That's why you observed a change in 0.93.