Repository navigation
Guard oversized semantic planner requests - #8
Merged
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.
A large semantic manifest can produce a planner prompt above the Codex input limit. The planner now stops before dispatch, records a bounded local planning packet, and preserves the full prompt for manual change-file planning. Oversized initial requests skip run-record validation and record that it did not run; normal requests keep the existing validation path.
Validation: the reported large module produced a 4,307,790-byte request and stopped locally without starting the provider. The native suite passed 900 unit tests and 11 CLI tests; 6 tests were ignored. Formatting and whitespace checks passed.