Preserve hook trust bypass in codex exec threads#26434
Merged
Merged
Conversation
eternal-openai
approved these changes
Jun 16, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Addresses #26383 and #26452
Summary
codex exec --dangerously-bypass-hook-trustprinted the bypass warning, but valid untrusted hooks still did not run.Exec applied the flag to its initial config, then lost it when app-server reloaded config for the new or resumed thread.
Fix
Forward
bypass_hook_trust: truethrough the existing thread request config override for both start and resume.The override is omitted when the flag is not enabled, preserving normal trust behavior.
Testing
Added:
SessionStarthook runs and creates a marker file.