Repository navigation
1.5.1
install --scope projectfor Codex CLI now says that Codex loads a project's hooks only in a trusted project, and how to trust it: trust the folder when Codex asks, runcodex exec --trustonce in it (0.169.0 or later), or add[projects.'<folder>'] trust_level = "trusted"toconfig.tomlinCODEX_HOME. The README and the conformance note say the same.- Following Codex CLI 0.169.0 (openai/codex #60041): a project's hooks always ran only in a trusted project, but before 0.169.0 a danger-full-access
codex execrun trusted the folder by itself (seen on 0.168.0); on 0.169.0 and 0.170.0 no run does, so the hooks stay off until the person trusts the folder. A trust entry inconfig.toml(orcodex exec --trust, which writes it) makes them run again. The real-binary check of--scope projectfor Codex, red ine2e.ymlsince 16 November, trusts the project that way.
The next good first issue is still #11: list --theirs.