Clarify approval limits for finish automation#543
Merged
Conversation
Guardex owns the repo-side finish flow, but Codex host policy still controls external remote side effects. The managed AGENTS block now tells agents to request one narrow finish-flow approval instead of retrying raw push or PR commands. Constraint: Codex host approval policy cannot be bypassed from repo code Rejected: Add a push bypass in gx | host-side policy intercepts commands before repo code can run Confidence: high Scope-risk: narrow Directive: Keep publish guidance routed through gx branch finish; do not teach raw git push retries as the workaround Tested: node --test test/setup.test.js Tested: openspec validate --specs Co-authored-by: OmX <omx@oh-my-codex.dev>
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.
Automated by gx branch finish (PR flow).