GPT-5.5 needs opt-in 1M context in Codex Desktop; the current 258K effective limit is breaking long-running development workflows

Summary

Please prioritize shipping opt-in 1M-token context for GPT-5.5 in Codex Desktop.

This is not a cosmetic request, and it is not simply that "more context would be nice." The current effective limit in Codex Desktop is materially reducing the reliability of long-running engineering workflows. In practice, GPT-5.5 sessions begin recurring memory compaction around the current ~258K effective input budget, and those compactions are lossy enough to degrade complex tasks.

OpenAI has already acknowledged that GPT-5.5 supports 1M context at the model/API level, while Codex currently exposes a much smaller product limit. I understand capacity planning is required, and I am not asking for 1M to become the default for everyone. I am asking for an explicit opt-in path for power users, even if it consumes usage at a higher rate.

Why this is urgent

For real development work, the current limit is not enough for:

• multi-hour debugging sessions where exact failed attempts, logs, stack traces, environment constraints, and hypotheses need to remain available;
• large architectural refactors where the working plan itself becomes substantial and must remain stable across many tool calls;
• codebases with large AGENTS.md / project rules, generated plans, design docs, and multiple relevant source files;
• cross-module changes where the model must preserve invariants across many files and not rediscover them after every compaction;
• repeated build / test / fix loops where command quirks, prior errors, and partial fixes are critical context rather than disposable chat history.

When compaction runs repeatedly, the model often loses exact details that were necessary for later steps. The visible effect is not just inconvenience. It causes:

• re-reading and re-discovering the same repository facts;
• repeated failed commands and repeated debugging branches;
• drift from the original task objective after compaction;
• lower completion rate for complex tasks;
• more tokens and credits spent recovering state instead of progressing;
• user intervention to restate context that the tool previously had.

This directly harms developer productivity and makes GPT-5.5 feel worse suited for large tasks than it should be, even though the model itself is stronger.

Current behavior

Codex Desktop currently exposes an effective GPT-5.5 context around ~258K input tokens. This appears to come from the Codex product limit of 400K total context, with 272K input and 128K reserved output, plus the harness's effective usable budget.

model_context_window = 1000000 is not a viable workaround for GPT-5.5 today because the Codex model catalog caps GPT-5.5 at a 272K max context window, so local overrides are clamped or ignored. This differs from GPT-5.4, where Codex previously allowed a 1M max context option.

Request

Please ship one of the following as soon as possible:

1. an official model_context_window = 1000000 path for GPT-5.5 in Codex Desktop;
2. a tiered opt-in, e.g. 512K / 768K / 1M;
3. a UI-level advanced setting in Codex Desktop that makes the tradeoff explicit;
4. a higher usage multiplier for long-context GPT-5.5 if needed for capacity / cost reasons.

Keeping 400K as the default is completely reasonable. Hard-blocking power users from opting into the model's full long-context capability is not.

Expected behavior

A Pro / Business / Enterprise user should be able to opt into GPT-5.5 long context in Codex Desktop and verify the active input budget in /status or the status UI. Compaction should not repeatedly interrupt long-running tasks at ~258K when the user has explicitly selected a larger context window.

Related context

• GPT-5.5 launch materials distinguish Codex's 400K context from the API's 1M context: https://openai.com/index/introducing-gpt-5-5/
• #19185 documents user confusion and the 272K input / 128K output split: https://github.com/openai/codex/issues/19185
• #19464 already tracks the feature request, and an OpenAI collaborator stated that the team is working to make 1M-token context available for GPT-5.5 in Codex: https://github.com/openai/codex/issues/19464#issuecomment-4329299628

I am filing this separately to emphasize the practical product impact: the current context limit is already causing avoidable compaction churn and reducing task completion quality in real development workflows. Please treat this as a high-priority Codex Desktop reliability and productivity issue, not a minor enhancement.