Skip to content

1.5.1

Choose a tag to compare

@nrzz nrzz released this 19 Nov 10:10
· 3 commits to main since this release
27fc1c6
  • install --scope project for 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, run codex exec --trust once in it (0.169.0 or later), or add [projects.'<folder>'] trust_level = "trusted" to config.toml in CODEX_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 exec run 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 in config.toml (or codex exec --trust, which writes it) makes them run again. The real-binary check of --scope project for Codex, red in e2e.yml since 16 November, trusts the project that way.

The next good first issue is still #11: list --theirs.