codex v0.38.0 Error loading configuration: missing field `notifications` in `tui`

Resolved 💬 7 comments Opened Sep 17, 2025 by arthurlongue Closed Sep 18, 2025
💡 Likely answer: A maintainer (dylan-hurd-oai, contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

v0.38.0

Which model were you using?

gpt-5-codex

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What steps can reproduce the bug?

Update the codex to the new recently launched version and try to execute codex.

What is the expected behavior?

Codex cli to "open" and work correctly.

What do you see instead?

$ codex
Error loading configuration: missing field notifications
in tui

Additional information

Apparently this is causing the issue, removing it from the config.toml fixed the problem:

tui = { theme = { name = "dark-carbon-night" } }

View original on GitHub ↗

7 Comments

slonce70 · 10 months ago

Yee have too - can not start codex

arthurlongue · 10 months ago
Yee have too - can not start codex

I fixed it by completly removing the tui config from the config.toml, go inside your .codex/config.toml and see if it works too.

slonce70 · 10 months ago
> Yee have too - can not start codex I fixed it by completly removing the tui config from the config.toml, go inside your .codex/config.toml and see if it works too.

yes all good thanks for help

jiuyaopinyin · 10 months ago
> Yee have too - can not start codex I fixed it by completly removing the tui config from the config.toml, go inside your .codex/config.toml and see if it works too.

Hello, what is the file path?

jiuyaopinyin · 10 months ago
> > Yee have too - can not start codex > > > I fixed it by completly removing the tui config from the config.toml, go inside your .codex/config.toml and see if it works too. Hello, what is the file path?

found it
~/.codex/config.toml

iSevenDays · 10 months ago

Here is how I fixed the issue:
tui = { theme = { name = "dark-amber-terminal" } , notifications = true}

dylan-hurd-oai contributor · 10 months ago

This should be fixed in 0.39.0!