When Usage Limits Become a Product Feature: Codex, Tibo, and Claude
Recently, the Codex conversation has been less about a new model and more about one recurring action: resetting usage limits.
Sometimes the reset follows an incident. Sometimes it follows a cache or accounting problem, a product launch, or a user milestone. The five-hour limit has also disappeared from some interfaces, leaving only the weekly balance. Meanwhile, paid users have repeatedly seen their weekly allowance restored. Claude reset five-hour and weekly limits for all users on the same day GPT-5.6 launched.
Then Codex leader Tibo Sottiaux replied to Claude's announcement with three words: “I smell fear.”
It was an excellent screenshot. But beneath the joke is a more important shift: in the agent era, quotas, resets, and rate limits have moved from backend infrastructure into the product experience itself.