fix(core): honor Codex input limits - #39545
Conversation
|
Thanks for your contribution! This PR doesn't have a linked issue. All PRs must reference an existing issue. Please:
See CONTRIBUTING.md for details. |
|
The following comment was made by an LLM, it may be inaccurate: Based on the search results, I found a related PR: PR #38987: fix(core): honor Codex input limits This is the PR that the current PR (39545) explicitly supersedes. According to the description: "Supersedes #38987: same Kit-authored patch, conflict-resolved onto current PR #39082: fix(opencode): correct Codex OAuth GPT-5.6 context window This PR appears related as it also addresses GPT-5.6 context/input window handling in the Codex OAuth flow, which is directly relevant to the current PR's focus on honoring input limits for ChatGPT OAuth. These are the closest related PRs; PR #38987 is the direct predecessor that was superseded by this current work. |
|
Thanks for updating your PR! It now meets our contributing guidelines. 👍 |
|
Issue link note: the template now contains |
Issue for this PR
Closes #38851
Type of change
What does this PR do?
Preserves models.dev's separate input limit through LLM routes. For ChatGPT OAuth, it overlays canonical
openai-codexlimits onto matching OpenAI models; API-key limits stay unchanged. Compaction usesinput - buffer, and the TUI reports usage against that effective input window.This makes GPT-5.6 Sol compact at 252K (272K input minus the existing 20K buffer), before the Codex backend ceiling. Depends on anomalyco/models.dev#3754.
Supersedes conflicting #38987 with the same Kit-authored patch rebased onto current
v2.How did you verify your code works?
Screenshots / recordings
N/A; no visual layout change.
Checklist