Conversation
Avoid inheriting public OpenAI API input limits for OAuth model metadata, including refreshed and fallback entries. Preserve explicit limit validation. Generated-by: OpenAI Codex
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
Codex OAuth turns failed before sending a request because public OpenAI API metadata supplied a 922,000-token input limit alongside a smaller OAuth window (272,000 or 372,000). Exclude that API input limit from Codex OAuth metadata, including refreshed catalogs and shipped fallbacks, so pinned and discovered windows remain usable. Public API metadata and explicit inventory/user input limits retain their existing behavior and conflict validation.
Fixes #5285
Verification
AI use
Tool(s) and scope: OpenAI Codex and native Codex subagents reproduced the issue, implemented and reviewed the fix, added regression tests, and ran local validation on behalf of hbw00111. This automated draft is awaiting independent human review and a human decision to advance it; AI review does not replace that review.
Checklist
Does this PR entail a change in behavior?