GPT-5.6 Sol effective context repeatedly flips between 828.4K and 258.4K in the same Codex App task

Open 💬 2 comments Opened Aug 24, 2026 by jinwukong
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

<!-- Proposed title: GPT-5.6 Sol effective context repeatedly flips between 828.4K and 258.4K in the same Codex App task -->

What version of the Codex App are you using (From “About Codex” dialog)?

26.818.41509

Codex CLI bundled/available on the same machine: 0.149.0.

What subscription do you have?

ChatGPT subscription (tier omitted)

What platform is your computer?

Darwin 25.6.0 arm64 arm

What issue are you seeing?

In the same long-lived Codex App task, using the same model and local configuration, GPT-5.6 Sol's effective context window repeatedly changes between 828400 and 258400 tokens at turn boundaries.

This is not only a stale UI value. Across multiple days, the task's local rollout records contain token_count events whose model_context_window field repeatedly follows this pattern:

258400 -> 828400 -> 258400 -> 828400 -> 258400 -> 828400 -> 258400

A transition was also observed between adjacent turns without any model, client-version, or configuration change.

A fresh server-delivered model catalog currently returns:

gpt-5.6-sol:   context_window = 272000, max_context_window = 272000
gpt-5.6-terra: context_window = 272000, max_context_window = 872000
gpt-5.6-luna:  context_window = 272000, max_context_window = 872000
effective_context_window_percent = 95

The local configuration remains:

model = "gpt-5.6-sol"
model_context_window = 1000000
model_auto_compact_token_limit = 900000

There is no model_catalog_json override, and I have not manually edited models_cache.json.

What steps can reproduce the bug?

The behavior is intermittent rather than deterministically triggered on every refresh:

  1. Sign in to Codex App with ChatGPT authentication.
  2. Configure GPT-5.6 Sol with:

``toml
model = "gpt-5.6-sol"
model_context_window = 1000000
model_auto_compact_token_limit = 900000
``

  1. Start or continue a GPT-5.6 Sol task.
  2. Across turns and normal remote model-catalog refreshes, inspect the effective window shown by the App or the task's token_count.info.model_context_window events.
  3. Observe the same task alternating between 828400 and 258400 without a local configuration or model change.

What is the expected behavior?

The server-delivered GPT-5.6 Sol context profile should remain stable for the same supported Codex App surface, model, client version, and configuration.

If the expanded context profile is controlled by a staged rollout, experiment, capacity mitigation, or product policy, a catalog refresh should not silently switch an active workflow between 872000 and 272000 maximum context profiles. The applicable eligibility and routing behavior should also be documented.

Additional information

The observations above were reproduced through the normal Codex App path without a custom model catalog.

Related reports:

  • #39144 — Sol receives a 272K maximum while Terra and Luna receive 872K.
  • #40106 — Sol remains capped at 272K despite the documented long-context configuration.
  • #39102 — The bundled GPT-5.6 catalog was changed to allow context overrides up to 872K.

The distinguishing observation in this report is that the same task switched profiles repeatedly over time without any local model or configuration change. This suggests a time-varying rollout/routing component or inconsistent catalog propagation; that interpretation is an inference from the observed transitions.

The official GPT-5.6 Sol model page advertises a 1,050,000-token model context window. This issue concerns the Codex product's server-delivered catalog ceiling and its instability, not the underlying API model specification.

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 4 days ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #39144

Powered by Codex Action

MaksOrigin · 17 hours ago

I can reproduce the same issue on Windows with a ChatGPT-authenticated paid Codex account.

Environment

  • Platform: Windows 11 x64
  • Codex CLI bundled/available: 0.150.0-alpha.8
  • Model: gpt-5.6-sol
  • Authentication: ChatGPT
  • Account profile reported by runtime metadata: Pro Lite

Global configuration remained unchanged throughout the reproduction:

model = "gpt-5.6-sol"
model_context_window = 872000
model_auto_compact_token_limit = 780000

There is no project-level model, model_context_window, model_auto_compact_token_limit, or profile override in the comparison project.

Exact same-task transition

The rollout for one task contains these adjacent turn-start events:

2026-08-27T17:57:46.052Z  task_started  model_context_window=828400
2026-08-27T18:07:03.935Z  task_started  model_context_window=258400

The selected model and local configuration did not change between them.

A freshly refreshed server model catalog then reported:

gpt-5.6-sol:
  context_window = 272000
  max_context_window = 272000
  effective_context_window_percent = 95

This gives exactly:

272000 × 0.95 = 258400

At the same time, the bundled catalog supports max_context_window = 872000, matching the earlier effective value:

872000 × 0.95 = 828400

A separate brand-new Codex App task also started directly at 258400, so this is not limited to stale state in an old task.

Severe user impact

At 2026-08-27T18:09:23.537Z, the affected task recorded an automatic compacted event after only two visible user messages. The visible conversation was still at the beginning, but the reduced effective limit plus diagnostic/tool context was already enough to force compaction. This makes long-running repository work impractical and causes avoidable memory degradation.

Questions for OpenAI

Please provide a concrete answer on the following:

  1. Why does the authenticated server catalog override the supported 872000 maximum with 272000 specifically for Sol?
  2. Why can the same active task switch from 828400 to 258400 at a turn boundary without any model or configuration change?
  3. Is this an account-entitlement error, a staged rollout, capacity mitigation, or an unintended backend regression?
  4. Is model_context_window = 872000 currently supposed to work for ChatGPT-authenticated Codex accounts?
  5. When will the expanded Sol context profile become stable, and is there an ETA for restoring it on affected accounts?
  6. Can active tasks be protected from a silent context-contract downgrade during catalog refresh?

Please do not close this as a configuration issue: the local configuration was verified, a separate fresh task reproduced the lower limit, and the effective value follows the server-delivered 272000 × 95% profile exactly.

I can provide additional sanitized timestamps and catalog metadata if needed.