Repository navigation
docs(codex): document hook-trust gate + how to approve - #74
Merged
Merged
Conversation
Codex gates non-managed hooks behind a per-hook trust review; until approved they are skipped silently (no error), so a freshly `init`-ed repo's notebook/navigation hooks never fire. `init` cannot pre-trust them (no supported non-interactive path — openai/codex#21615). Add a post-init note in setupCodex and a docs.html paragraph explaining: approve via the "Hooks need review → Trust all and continue" prompt (launch `codex` from a terminal if the GUI app doesn't surface it), or pass `--dangerously-bypass-hook-trust` for `codex exec` automation. Also clarifies project trust (trust_level) is a separate gate. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
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.
Why
Codex (0.144.x) gates non-managed hooks behind a per-hook trust review. Until approved, hooks are skipped silently — no error, no log. So after
coldstart initon a Codex repo, the notebook/navigation hooks appear wired but never fire, with nothing to explain why. This cost a full debugging session to diagnose.initcannot pre-trust them — there is no supported non-interactive path (openai/codex#21615).Verified end-to-end on Codex
0.144.0-alpha.4: once trusted via the terminalcodexstartup prompt ("Hooks need review → Trust all and continue"), recall (UserPromptSubmit) and capture (Stop, flushed at session exit) both fire and a note was written. The Desktop GUI never surfaced the trust prompt in this build; the terminal is the reliable surface.What
Documentation/UX only — no behavior change to the indexer:
src/init.ts—setupCodexprints a post-init note when hooks are wired: how to approve (the "Hooks need review" prompt / launchcodexfrom a terminal if the app doesn't surface it) or--dangerously-bypass-hook-trustforcodex execautomation.site/docs.html— a "Codex hook trust" paragraph in the setup section covering the same, plus that project trust (trust_level) is a separate gate from hook trust, and the#21615limitation.Surface-neutral wording (doesn't assume terminal CLI vs Desktop).
Test
npm run buildpasses.coldstart init --client codexin a scratch repo; note renders correctly.🤖 Generated with Claude Code