Clarify Codex hook setup troubleshooting#205
Merged
Merged
Conversation
Co-authored-by: Codex <noreply@openai.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.
Summary
agent-strace setup --cli codexoutput.[features].hooks = false, and the reload/trust step.0.79.1for the setup-output improvement.Context
The generated hook schema is already valid for Codex, but users can end up with a valid-looking file that the Hooks UI does not list when it is in the wrong config layer/path, hooks are disabled in
config.toml, or the UI has not reloaded/reviewed the command hooks.Verification
python3 -m pytest tests/test_codex_hooks.py tests/test_cursor_hooks.py tests/test_gemini_hooks.py -q-> 21 passedpython3 -m compileall -q src/agent_trace && git diff --checkpython3 -m agent_trace.cli --version-> agent-strace 0.79.1