Skip to content

fix(cli): use full GPT-5.6 OAuth context - #13165

Merged
marius-kilocode merged 1 commit into
mainfrom
research-kilo-openai-1m-context-support
Aug 17, 2026
Merged

fix(cli): use full GPT-5.6 OAuth context#13165
marius-kilocode merged 1 commit into
mainfrom
research-kilo-openai-1m-context-support

Conversation

@marius-kilocode

@marius-kilocode marius-kilocode commented Aug 17, 2026

Copy link
Copy Markdown
Collaborator

Kilo currently reports a 500k context limit for ChatGPT OAuth GPT-5.6 models, even though the current Codex limits support a 1.05M-token context window and 922k input window. This causes Kilo to compact or reject conversations earlier than necessary.

Use the current Codex context and input limits for every GPT-5.6 OAuth model while preserving the existing GPT-5.5 behavior. The release metadata documents the user-facing limit increase.

@kilo-code-bot

kilo-code-bot Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (3 files)
  • .changeset/gpt-56-oauth-context.md
  • packages/opencode/src/plugin/openai/codex.ts
  • packages/opencode/test/plugin/codex.test.ts

The change is a minimal, well-scoped value update: GPT-5.6 OAuth models now use the current Codex limits (1.05M context / 922k input), the kilocode_change markers are consistent with the existing inline pattern in this shared file, the updated test assertions match the new plugin values, and the changeset is user-facing and correctly scoped as a patch. No stale references to the old 500k/372k limits exist elsewhere in the repo, and no resource-lifecycle or memory-leak concerns are introduced.


Reviewed by kimi-k3 · Input: 65K · Output: 4.5K · Cached: 200.7K

Review guidance: REVIEW.md from base branch main

@marius-kilocode
marius-kilocode merged commit 3a426dd into main Aug 17, 2026
33 checks passed
@marius-kilocode
marius-kilocode deleted the research-kilo-openai-1m-context-support branch August 17, 2026 10:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants