Show warning/hint if you have a project `.codex/config.toml` but project does not have a trust setting

Resolved 💬 2 comments Opened Feb 2, 2026 by lgo Closed Feb 3, 2026

What version of Codex is running?

codex-cli 0.93.0

What subscription do you have?

Pro

Which model were you using?

_No response_

What platform is your computer?

Darwin 24.6.0 x86_64 i386

What terminal emulator and version are you using (if applicable)?

_No response_

What issue are you seeing?

While working on a project, I found that I had added .codex/config.toml (alongside rules and other items), and it confusingly wasn't working. It took a few reads of the config documentation to realize this was because the project wasn't a trusted project. (As an aside: I believe I observed .codex/rules were being used still, which I'm not sure is inconsistent with the project trust)

While I may have been prompted for it initially on the project, there was no entry in my ~/.codex/config.toml for the directory.

This would have been far less confusing if there was a warning on start when there was no trust setting (untrusted or trusted) for the directory when there was a configuration there that would otherwise not be respected.

What steps can reproduce the bug?

  • Add .codex/config.toml to project directory
  • Start project w/o trust setting

I wasn't sure why I was not getting a prompt re: trust.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗