That’s honestly the part that stings the most.
So, Enterprise customers and large companies get to keep the older, more usable system for longer, while normal Plus users, students, hobby developers, indie developers, and smaller creators get thrown straight into the stricter token-based system?
That feels backwards.
The people most affected by these aggressive limits are the smaller users who can’t casually jump to $100+ plans every month just to continue working normally. A lot of us are using Codex for learning, personal projects, open-source work, side projects, studying, or trying to build something real without corporate-level budgets behind us.
And the frustrating thing is that the product itself is genuinely incredible. That’s why people are upset. People WANT to use it. But the current experience makes many paying users feel like they’re being punished for actually using the tool heavily.
At the very least, there should be some kind of fallback mode after the high-end allowance runs out: Slower responses, Lower priority, Weaker model, Reduced tool access, and daily cooldowns
Anything is better than:
“Weekly limit hit. Come back in 4 days.”
Because for real project work, that basically kills momentum completely. Whoever came up with this, I hate you, man. I hope both sides of your pillow stay warm for the rest of your life.
EDIT:
I can accept limits existing. I can accept pricing changes. I can even accept stricter quotas for heavy users.
What I can’t accept is a UI that says “5h remaining” while the actual product response is:
“Weekly limit reached. Come back next week.”
That’s not transparency. That’s contradictory UX, and honestly it feels like this flow was pushed out without anyone seriously checking whether the messaging even made sense from a user perspetive. If the UI says “5h remaining” and the real answer is “locked out for 4 days,” then what exactly was the point of showing the timer at all?
And now I can’t even properly reply in this thread because apprently new users get rate-limited on responses too, so I have to edit an existing comment just to add clarification. Which honestly makes this whole experience even more absurd.
The issue was never “give me infinite usage.”
The issue is that many of us are using Codex for real project momentum, debugging sessions, architecture planning, and long development flows. A hard weekly shutdown mid-workflow doesn’t just reduce usage — it destroys continuity.
And judging by this thread, I’m clearly not the only person confused by it.
Anyway, I said what I needed to say. Hope the feedback reaches the people designing this stuff.