Add prompt hooks#24174
Draft
abhinav-oai wants to merge 1 commit into
Draft
Conversation
da02343 to
1a3f644
Compare
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
Prompt hooks let hook authors express review criteria as model-evaluated prompts while preserving Codex hook semantics. Codex should default these checks to the active thread model instead of a fixed hook model.
What
type = "prompt"hook handler config, app-server API, generated schemas, and hook list support with optionalmodel,timeout, andcontinueOnBlock.{ "ok": boolean, "reason": string }.ok: falseto Codex event-specific outcomes: deny pre-tool-use, block/continue post-tool-use according tocontinueOnBlock, block user prompt and stop hooks, and no-op permission requests.