Codex Head Tibo: Usage Limits for ChatGPT Work and Codex Have Been Reset
Codex Head Tibo stated that the usage limits for all ChatGPT Work and Codex users have been reset, and an update regarding the usage of GPT-5.6 Sol has been provided.
He noted that Sol consumes Codex quotas faster than expected, but the company has not reduced any subscription plan limits; multiple improvements have been implemented, and under typical usage, the expected consumption can last about 18% longer. Some users have already seen a more significant increase today, and the previously suspended five-hour limit will be restored tomorrow.
Sol is more inclined towards long-duration work, increasing tool calls and coordinating complex processes across sub-agents, consuming more tokens under the same reasoning intensity. Parallel code modes and continuous work also increase response and cache tokens; the median user efficiency is acceptable, but heavy users of high-difficulty tasks have significantly accelerated consumption, with capability improvements and efficiency enhancements not being synchronized.
Source: Public Information
ABAB AI Insight
OpenAI quickly faced the issue of exceeding expected quota consumption after launching GPT-5.6 Sol. Codex Head publicly acknowledged that during the pre-release phase, there was excessive focus on average and median consumption, underestimating the long-tail heavy scenarios, and immediately reset quotas, optimizing tool calls and waiting logic.
In terms of capital and product pathways, stronger autonomy (long-duration work, parallel tools, sub-agent coordination) directly translates to higher token consumption, forcing the platform to quickly address efficiency shortcomings after a leap in capability; resources are tilted towards runtime optimization, cache management, and differentiated quota design to balance cutting-edge capabilities with sustainable usage costs.
A similar path can be seen in the consumption curve corrections of previous generations of models from laboratory to large-scale deployment: capability leads, and efficiency follows is a common rhythm. The current agent workflow is still in the "parallel iteration of capability release and cost control" stage.
Essentially, this is a technological substitution: as models shift from single-round generation to multi-step autonomous tool usage, billing and limitation mechanisms must transition from static quotas to dynamic efficiency perception, with pricing power shifting to platforms that can simultaneously enhance capabilities and control consumption.
ABAB News · Cognitive Laws
Capability leaps often first appear in the form of exceeding expected consumption.
Median efficiency cannot mask the true costs of long-tail heavy users.
The stronger the autonomous workflow, the more critical runtime optimization becomes.