OpenAI expands the 1M token context window to ChatGPT subscribers for GPT-5.6 Sol

iconMetaEra
Share
AI summary iconSummary
OpenAI has launched new token listings for GPT-5.6 Sol, expanding the 1 million token context window to ChatGPT subscribers. Previously available only via API, this update now enables Plus, Pro, and similar users to access the full 1.05 million token context in Codex. This enhancement supports larger codebases and improved debugging. However, the token launch announcement highlights increased usage costs, as higher token consumption is likely to deplete weekly quotas more quickly.
OpenAI engineer Tibo recently announced that the 1 million-token context window for the GPT-5.6 Sol model has been expanded from API-only access to ChatGPT subscribers.

Article author, source: chinaz.com

Engineer Tibo from OpenAI, responsible for Codex and ChatGPT, recently announced on X that the 1 million token context window for the GPT-5.6 Sol model in Codex has been extended from API key access only to ChatGPT accounts. This means the previous limitation forcing subscribed users to truncate their history when handling large projects has finally been lifted.

image.png

Subscribed users can manually enable the million window.

Tibo explicitly wrote that GPT-5.6 Sol supports a 1 million context length in Codex; previously, this feature was only available via API keys, but now the “switch has just been flipped,” and it is also active for ChatGPT accounts. Users with Plus, Pro, or other subscription plans can manually enable the full context window of nearly 1.05 million tokens when using the Codex programming agent.

A larger context window allows Codex to retain more code, tool outputs, and conversation history before automatically compressing it, making it especially suitable for professional scenarios such as large-scale codebase refactoring, complex debugging, and extended sessions. For developers maintaining production-grade repositories, this adjustment directly alleviates the previous pain point of frequently insufficient context.

Default length matters; enable with caution.

Tibo also emphasized that Codex’s current default context length is the result of optimized trade-offs between performance and cost, not arbitrarily set, and reminded users, “You can decide for yourself.” Several developers also noted that, combined with Codex’s server-side compression mechanism, the default configuration is sufficiently efficient for most everyday tasks.

However, some users have reported that enabling the million-token context significantly accelerates subscription quota consumption, with a single high-intensity use potentially exhausting a large portion of the weekly quota. We recommend enabling it only when absolutely necessary, rather than setting it as a default daily setting, to avoid reaching your usage limit prematurely on critical projects.

Source:Show original
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.