Repository navigation
Bound repeated generation input in long Codex rollouts - #107
Draft
johnbuccola wants to merge 1 commit into
Draft
johnbuccola wants to merge 1 commit into
johnbuccola wants to merge 1 commit into
Conversation
|
John Buccola seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
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.
Change
Bound the repeated generation input on long Codex rollouts. The turn and tool spans still carry their evidence. Ordinary rollouts keep the existing generation input. Compaction records, which the parser does not use, are no longer retained.
Check
Limit
This prevents the observed repetition failure. Very large rollouts still need a streaming parser with durable turn retry handling. The fallback marks omitted generation input in the trace.