Bug Description
toasty --install codex adds the notify key under the [windows] TOML section in ~/.codex/config.toml, but according to the Codex configuration reference, notify must be a top-level key. Codex does not read notify from the [windows] section, so notifications never fire.
Current behavior (incorrect)
After running toasty --install codex, the generated config looks like:
[windows]
sandbox = "unelevated"
notify = ["MyPathToToasty", "Codex finished", "-t", "Codex", "--app", "codex"]
Codex ignores this notify entry entirely because it is nested under [windows].
Expected behavior
notify should be written at the top level:
notify = ["MyPathToToasty", "Codex finished", "-t", "Codex", "--app", "codex"]
[windows]
sandbox = "unelevated"
How to reproduce
- Install toasty on Windows
- Run
toasty --install codex
- Inspect
~/.codex/config.toml — notify is nested under [windows]
- Run a Codex task to completion — no toast notification appears
Environment
- Codex CLI 0.114.0
- Windows
Root cause
The Codex config installer in toasty is inserting notify into the wrong TOML section. The fix is to write notify as a top-level key, not under [windows].
Bug Description
toasty --install codexadds thenotifykey under the[windows]TOML section in~/.codex/config.toml, but according to the Codex configuration reference,notifymust be a top-level key. Codex does not readnotifyfrom the[windows]section, so notifications never fire.Current behavior (incorrect)
After running
toasty --install codex, the generated config looks like:Codex ignores this
notifyentry entirely because it is nested under[windows].Expected behavior
notifyshould be written at the top level:How to reproduce
toasty --install codex~/.codex/config.toml—notifyis nested under[windows]Environment
Root cause
The Codex config installer in toasty is inserting
notifyinto the wrong TOML section. The fix is to writenotifyas a top-level key, not under[windows].