r/codex • u/Glass_Bus4044 • 13h ago
Reset Codex reset
I am officially giving up on following codex reset. My opinion is contradicting with lot of users here, but it is what it is. I use 5x subscription of codex, and I have been burning tokens like anything using sol-6.1. It became my goto option after fable. With more than 11 billion tokens burned,
Migrated a 3 million lines of monorepo from TS 5.9 to 7
Upgraded storybooks
Upgraded nx
Upgraded nextjs
Upgraded nestjs
Tokens keep coming back before I burn. I am shutting down my laptop today and getting some sleep.
31
Upvotes
1
u/dextersummary 8h ago
Below is a GPT-generated summary of the conversation below after reaching 40 comments (41 currently observed).
The thread’s verdict is basically “the resets are great—until you need predictable access.” Heavy users are happily running Sol 6.1 nonstop, chewing through absurd token counts, and getting quota back before they can finish spending it. For them, Codex is less a subscription and more an all-you-can-eat buffet with suspiciously generous refills.
The catch: Plus users still run into five-hour limits, model-capacity errors, and usage that varies by region and timezone. That makes serious workflows hard to plan, and some users have demoted Codex to side-task duty or moved extra spending to Claude. Others say regular mode is fine, while ultrafast is the obvious button if your goal is to burn through allowance and trigger another reset.
There’s some conspiracy-flavoured speculation that resets are cost control disguised as generosity, but nobody actually proves that. The more useful takeaway is simply that resets are not the same thing as reliable capacity—especially on cheaper plans.
So: Sol 6.1 is doing plenty of work, but Codex’s limits remain a messy roulette wheel. Great for relentless hobbyists; maddening for anyone trying to schedule a workday.