fix: update Codex hooks feature flag#708
Merged
backnotprop merged 1 commit intoMay 12, 2026
Merged
Conversation
leoreisdias
changed the title
Owner
|
thanks! |
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
2 participants
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.
Problem
Codex no longer wants users or installers to enable hooks with
[features].codex_hooks. The current CLI reports that flag as deprecated and asks users to use[features].hooksinstead.Plannotator still wrote and documented the old flag in a few places: the Unix installer, Windows manual guidance, Codex setup docs, troubleshooting docs, local E2E harnesses, and the release smoke test. That means new installs could produce deprecation warnings, and the project documentation pointed users at a stale Codex configuration shape.
Solution
Update Plannotator’s Codex setup path to use the current
[features].hooks = trueflag everywhere user-facing or test-facing.The Unix installer now writes
hooks = truefor new Codex configs and also migrates an existing managedcodex_hooks = ...entry tohooks = truewhen it updates the[features]table. Inlinefeatures = ...configs are still left untouched, with the manual guidance updated to show the new flag.This also updates the docs, Windows installer guidance, manual Codex harness commands, and the release workflow assertion so they all agree on the same current Codex feature flag.
Validation
bun test scripts/install.test.ts