Codex release review

Explain what changed in Codex CLI and what it means for this repository's configuration and daily use. Give the full report in the final chat response. Treat upgrading Codex as the user's settled choice; do not recommend whether or when to upgrade. Focus recommendations on configuration and feature use. Edit configuration or install a version only when the user requests that action.

Establish the comparison

1. Read the repository instructions and its Codex setup in the README. Start the configuration audit at non-standard/codex/config.toml. Inspect related rules, agent instructions, hooks, or custom approval policies when a release change affects them.
2. Record the review date and the installed CLI version, if available. Identify the tracked configuration, any project overrides, and the active configuration used for local checks. A tracked template and an active user configuration may differ.
3. Honor a named target version or release channel. Otherwise, resolve the latest stable CLI release from the official upstream release list; check its tag, publication date, and prerelease status.
4. Honor a named baseline. For an upgrade analysis, use the installed version when it is known and older than the target. For a review of one release, use its previous release in the same channel. If the request leaves the baseline open, use the previous stable release and state that choice. Ask when the available evidence cannot resolve the intended range.
5. Verify both upstream tags or commit IDs. List every release after the baseline through the target, including intermediate releases in the requested channel. Keep the installed version separate when it differs from this comparison.

Research the complete release range

Use official OpenAI documentation and the openai/codex repository as primary sources. Open the actual pages or files. Search snippets and release titles are discovery aids.