Repository navigation
Token report: take the Codex hook engine from the stable hooks flag; drop the removed plugin_hooks step - #265
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
…265) Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
|
Independent review (separate Sonnet reviewer, read-only): ready. It hand-traced all 9 derivation cases, confirmed no remaining doc, template or test reference depends on the removed |
|
Counter semantics for the token-practice docs and reporter. This is evidence from #270 (merged), independently reviewed (agree ×4). I haven't edited this PR's files. Please fold in whatever fits at integration. Receipts, generation 2, on What each counter actually counts:
|
…265) Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
fa70702 to
834cdb6
Compare
codex-cli 0.155.1 lists `hooks` as stable and on by default and `plugin_hooks` as removed (always false). token_manifest.py required both flags, so a host following current Codex (no plugin_hooks key) was reported as having its hook engine off. The derivation now reads `hooks` (legacy alias `codex_hooks`), defaulting to on when absent. The dead `codex features enable plugin_hooks` step and template key are dropped from the recipe, handbook, token-stack JSON and Codex config template; codex_lane's isolation override is left as is (disabling a removed feature is harmless and still isolates older clients). Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
…265) Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
834cdb6 to
043b4e5
Compare
Scope
tools/token-report/token_manifest.pynow takes Codex's hook-engine state from the stable[features] hooksflag. Before, it required bothhooksand the removedplugin_hooks, so a host that follows current Codex reported its hook engine as off. The deadcodex features enable plugin_hooksstep and theplugin_hooks = truetemplate key are removed.6752ede5(origin/main)lane:foundationtools/token-report/token_manifest.pyandtest_token_manifest.pyrecipes/README.mddocs/token-session-handbook.mddocs/token-efficiency-stack.jsonadoption/templates/codex.config.template.tomlmanifests/evidence.jsonEvidence-class table
hooksis stable and on, andplugin_hooksis removed and offnative_proven(native CLI output on this host)codex features listreturnedhooks stable trueandplugin_hooks removed falsecodex features enable plugin_hooksstill exits 0 and writes the key, but the feature stays offnative_proven, in a throwawayCODEX_HOMECODEX_HOME=$(mktemp -d) codex features enable plugin_hooks, thencodex features listcodex_hooks, a non-boolean value and a non-tablefeaturessynthetictest_codex_hook_engine_follows_the_stable_hooks_flag_not_removed_plugin_hooksThe #264 builder found the same semantics in the codex-rs source:
hooksisStage::Stablewithdefault_enabledtrue,plugin_hooksisStage::Removed, andcodex_hooksis a legacy alias.tools/sota-convergence/codex_lane.pyand the historical blueprint probes keep-c features.plugin_hooks=false. Disabling a removed feature is harmless and still isolates older clients.Local commands run
Decision record
None. This corrects documentation and a reporter to match native client behaviour.
Host evidence
Not applicable. This host's
~/.codex/config.tomlstill carries the harmless dead key, and it was not edited.Checklist
🤖 Generated with Claude Code