Codex desk · usage policy · Codex · Policy
Codex and Work raise GPT-6.1 Sol’s default context to 500k
Tibo says the default grew from 272k to 500k, and subscription usage will not incur long-context fees for GPT-6.1 Sol. This is a usage-policy change, not a reset.
With this change, we are not charging long context fees for GPT-6.1 Sol when drawing usage from the subscription.
Also on file: 3 more posts
-
@thsottiaux · 11 Oct 2026 Day 7/
We have increased default context length for GPT-6.1 Sol to 500k when used through Codex & Work, up from 272k or an ~ 80% increase.
We will go higher in the future, but it helps reduce occurrence of compactions and with tasks that require keeping a lot of context and nuance over periods of time. It was carefully tested and is the new sweet spot for most of our users. You can still override it if you want to be higher our lower, with maximum context length of GPT-6.1 Sol of 1M. -
@thsottiaux · 12 Oct 2026 The results of this poll has gotten me confused. I definitely thought it would sway much more favorably in the 2X direction across Pro 100/200/500 at the cost of bringing back 5h limits in order to smoothen the demand curve. -
@thsottiaux · 11 Oct 2026 Pro users, would you rather have
“With this change, we are not charging long context fees for GPT-6.1 Sol when drawing usage from the subscription.”
Tibo says GPT-6.1 Sol now defaults to a 500k context window in Codex and ChatGPT Work, up from 272k. A follow-up says subscription usage for that model will not carry long-context fees.
The original Day 7 post, verified through X syndication, states the 500k default, the previous 272k value and Codex and Work scope in its primary text. Syndication truncates the rest of the long post, so this report does not rely on its unverified remainder.
Tibo's complete follow-up explicitly says there are no long-context fees for GPT-6.1 Sol when drawing usage from the subscription. That is a model- and payment-path-specific usage term; it does not establish an unlimited allowance or erase prior consumption.
A separate Pro-user poll asked whether subscribers would prefer twice the weekly allowance with five-hour limits or unchanged usage without five-hour limits. Tibo later said he expected stronger support for the first option across Pro 100, 200 and 500. The poll and reaction are research and commentary, not a decision, promise or reset.
The September 22 Tuesday/3am Codex signal still has no verified timezone or new delivery details. The Day 6 global reset remains separately provider-confirmed as propagated, with its reset mechanics and exact eligibility unstated.
What it means
- Tibo reports a 500k default context length for GPT-6.1 Sol in Codex and Work, up from 272k.
- The no-long-context-fee statement is specific to GPT-6.1 Sol when usage is drawn from a subscription. It does not establish terms for other models, API billing, or every account's consumption.
- The longer default may reduce compactions, but it does not clear a usage counter or promise extra quota. It stays outside reset history, calendars and subscriber reset alerts.
- Separately, Tibo discussed a poll comparing twice the weekly Pro allowance with five-hour limits against unchanged usage without five-hour limits. He did not announce a policy change or reset.