You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Codex: default vs selected variants show different effective context; support per-variant limits #12416
Even if internals normalize limits differently, allowing variant-level declaration (or rejecting unsupported keys with a clear error) would reduce confusion.
It looks like ChatGPT subscription-backed Codex models are already constrained (roughly 272k input / 128k output) regardless of selected variant, so the default-vs-variant interpretation here was likely mistaken.
Activity
github-actions commentedon Feb 6, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
HyunggyuJang commentedon Feb 7, 2026
Closing this as my report appears incorrect.
I traced this to model metadata in pi-mono:
https://github.com/badlogic/pi-mono/blob/f9161c4d4e0d001ebfbd3ba98f0b89adb253260a/packages/ai/src/models.generated.ts#L5099
It looks like ChatGPT subscription-backed Codex models are already constrained (roughly 272k input / 128k output) regardless of selected variant, so the default-vs-variant interpretation here was likely mistaken.
Sorry for the noise.