fix(agent): avoid duplicate Codex custom prompt - #596
Merged
Conversation
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
Root cause and evidence
The retained EXP-0210
parser-core/spec_reviewpreview was 219,822 bytes against the closed 131,072-byte governed prompt limit because Probe forwarded the already-embedded custom prompt a second time. The zero-model localizer made one preview, zero initialize/answer/model/network calls, and preserved the checkpoint.Verification
node --test tests/unit/governed-answer-dispatch-preview.test.js tests/unit/governed-codex-runtime-binding.exp-0148.test.js(57 passed)git diff --checkNo prompt limits, Proof authority, Visor bindings, schema validation, retry, or fallback behavior are weakened.