tui.notifications stops working randomly; iTerm2 notifications no longer triggered

What version of Codex is running?

0.63.0

What subscription do you have?

Pro

Which model were you using?

gpt-5.1-codex-max

What platform is your computer?

macOS using iTerm2

What issue are you seeing?

After setting TUI.notifications to an array containing agent_turn_complete and approval_request, notifications worked correctly for a long time. I run Codex CLI in iTerm2 on macOS, and the CLI would emit native iTerm2 notifications whenever an agent finished a term or requested approval. However, at some point the notifications suddenly stopped working. Codex no longer triggers any iTerm2 notifications. To verify that iTerm2 notifications still work, I ran the escape-sequence command echo -e "\033]9;Your message here\007" and saw a native notification. I also tested my custom notify script (a Python script) which calls iTerm2 notifications, and that still works. Therefore, the issue seems specific to Codex's TUI.notifications configuration – it no longer sends notifications.

What steps can reproduce the bug?

1. Set the [tui] -> notifications configuration in config.toml to [ "agent_term_complete", "approval_request" ] (or a similar array).
2. Start Codex CLI in iTerm2 on macOS and verify that native notifications appear for the configured events.
3. Continue using Codex CLI; after some random amount of time or several sessions, the notifications stop working.
4. Confirm that iTerm2 notifications still function by running echo -e "\033]9;Your message here\007" or executing a custom notify script that emits a native iTerm2 notification; these succeed.
5. Observe that Codex no longer triggers notifications despite the configuration.

What is the expected behavior?

Codex CLI should consistently send native iTerm2 notifications for events listed in the TUI.notifications configuration. Notifications should not randomly stop working; if iTerm2 and custom scripts can emit notifications, Codex should do the same.

Additional information

_No response_