Feature request
Please make the current temporary removal of Codex's 5-hour usage restriction permanent for Plus, Pro, and Business plans, while retaining the existing weekly usage allowance.
Context
On July 12, 2026, Tibo Sottiaux announced that OpenAI was temporarily removing the 5-hour usage-limit restriction while rolling out GPT-5.6 efficiency improvements:
https://x.com/thsottiaux/status/2076365965915467978
After using Codex under this weekly-only system, I believe it is a substantially better way to manage included usage and one of the most meaningful improvements to the product since the release of GPT-5.6.
Why the weekly-only model is better
The 5-hour window requires users to continually monitor a short-term meter and organize their work around rolling reset periods. That creates friction precisely when Codex is most valuable: long-running development, debugging, refactoring, research, and other tasks whose natural duration is difficult to predict.
With a weekly allowance as the governing limit:
- Users can focus on completing work instead of micromanaging consumption within the 5-hour usage window.
- Longer and more ambitious tasks are less likely to be interrupted at arbitrary points.
- Users can distribute their included usage according to their own schedules and workloads.
- The overall weekly allowance still provides a clear, finite usage budget.
- Codex feels more predictable and suitable for serious project work.
This is not a request for unlimited usage. It is a request to let customers decide how to allocate the usage already included in their weekly allowance, without an additional short-window restriction determining when that allowance may be used.
Requested behavior
- Permanently retire the 5-hour usage window for Plus, Pro, and Business plans.
- Retain the weekly included-usage allowance.
- Continue applying reasonable fair-use, abuse-prevention, and infrastructure protections where necessary.
- Clearly document the weekly allowance and how usage is calculated.
- If capacity protection still requires a shorter safeguard during exceptional demand, use a transparent temporary mechanism rather than restoring the 5-hour window as the normal customer experience.
Why this experiment matters
The temporary removal has demonstrated an important product benefit that usage statistics alone may not capture: reduced cognitive overhead. Not having to repeatedly check a meter makes Codex feel calmer, more trustworthy, and easier to integrate into real work.
Please evaluate the experiment not only by aggregate consumption and infrastructure load, but also by task completion, interruption rates, sustained project workflows, and user satisfaction. The weekly-only experience is a major improvement. Please make it permanent.
Feature request
Please make the current temporary removal of Codex's 5-hour usage restriction permanent for Plus, Pro, and Business plans, while retaining the existing weekly usage allowance.
Context
On July 12, 2026, Tibo Sottiaux announced that OpenAI was temporarily removing the 5-hour usage-limit restriction while rolling out GPT-5.6 efficiency improvements:
https://x.com/thsottiaux/status/2076365965915467978
After using Codex under this weekly-only system, I believe it is a substantially better way to manage included usage and one of the most meaningful improvements to the product since the release of GPT-5.6.
Why the weekly-only model is better
The 5-hour window requires users to continually monitor a short-term meter and organize their work around rolling reset periods. That creates friction precisely when Codex is most valuable: long-running development, debugging, refactoring, research, and other tasks whose natural duration is difficult to predict.
With a weekly allowance as the governing limit:
This is not a request for unlimited usage. It is a request to let customers decide how to allocate the usage already included in their weekly allowance, without an additional short-window restriction determining when that allowance may be used.
Requested behavior
Why this experiment matters
The temporary removal has demonstrated an important product benefit that usage statistics alone may not capture: reduced cognitive overhead. Not having to repeatedly check a meter makes Codex feel calmer, more trustworthy, and easier to integrate into real work.
Please evaluate the experiment not only by aggregate consumption and infrastructure load, but also by task completion, interruption rates, sustained project workflows, and user satisfaction. The weekly-only experience is a major improvement. Please make it permanent.