[codex] Update Codex hooks feature flag docs - #31
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Update the Codex CLI setup instructions to use the current hooks feature flag name,
hooks, instead of the deprecatedcodex_hookskey.Also document the equivalent one-off CLI flag,
codex --enable hooks, and add a small README regression test so the deprecated flag does not get reintroduced.Root Cause
The plugin docs still told users to add
[features].codex_hooks = trueto~/.codex/config.toml. Current Codex CLI releases warn that[features].codex_hooksis deprecated and should be replaced by[features].hooksor--enable hooks.Validation
bash tests/readme-codex-feature-flag.shfor test_script in tests/*.sh; do bash "$test_script"; done