What version of Codex is running?
codex-cli 0.77.0
What subscription do you have?
Plus
Which model were you using?
No response
What platform is your computer?
Windows/WSL
What issue are you seeing?
I noticed that Windows notifications were no longer popping up when codex was done thinking. I then went into WSL's ~/.codex/config.toml, and added notify = ["bash", "-c", "echo $(date) >> /tmp/codex-notify.log"]. The file was never written to, so it seems like codex is no longer triggering notify. The terminal was not in focus for these tests. The behavior began midway through today, an hour into my session. I was using codex-cli 0.77.0, then ran npm update -g @openai/codex for the latest update, and the behavior persisted.
What steps can reproduce the bug?
- Install codex in WSL2 - Ubuntu
- Ask codex anything which takes some time to think about (I asked it: "parameterize the vectors in the tangent bundle of the torus")
- Immediately navigate away from the terminal
- Add
notify = ["bash", "-c", "echo $(date) >> /tmp/codex-notify.log"] to config.toml
- Repeat steps 2 & 3. Observe that /tmp/codex-notify.log is still empty.
What is the expected behavior?
No response
Additional information
No response
What version of Codex is running?
codex-cli 0.77.0
What subscription do you have?
Plus
Which model were you using?
No response
What platform is your computer?
Windows/WSL
What issue are you seeing?
I noticed that Windows notifications were no longer popping up when codex was done thinking. I then went into WSL's ~/.codex/config.toml, and added
notify = ["bash", "-c", "echo $(date) >> /tmp/codex-notify.log"]. The file was never written to, so it seems like codex is no longer triggering notify. The terminal was not in focus for these tests. The behavior began midway through today, an hour into my session. I was using codex-cli 0.77.0, then rannpm update -g @openai/codexfor the latest update, and the behavior persisted.What steps can reproduce the bug?
notify = ["bash", "-c", "echo $(date) >> /tmp/codex-notify.log"]to config.tomlWhat is the expected behavior?
No response
Additional information
No response