Why business owners hit the wall, what the caps actually are, and when it's time to upgrade
If you have ever been in the middle of a task in Codex and gotten a message telling you to try again at a specific time — say, 9 PM — you have hit the 5-hour usage limit. It causes more confusion than it should, and the confusion almost always points at the wrong culprit.
This post explains exactly how usage limits work in Codex and Claude Code, what the different plan tiers mean in practice, and how to tell whether the limits are a temporary inconvenience or a structural mismatch between your plan and what you are trying to build.
For the complete framework on setting up Codex as an operational system, read the full guide.
What the Usage Limits Actually Are
Both Codex and Claude Code operate under two distinct caps:
The 5-hour usage limit is a rolling window. When you hit it, Codex stops and tells you when the window resets — something like "try again at 9 PM." The clock starts from when you began using it, not from midnight.
The weekly usage limit is a broader ceiling tied to your monthly subscription plan. It sits above the 5-hour limit. You may never encounter it on a higher plan, but it governs how much total usage your plan can sustain across a full week.
These two caps work together. The 5-hour limit is the one you encounter first. The weekly limit determines whether your plan can support the kind of work you want to do across a full month.
What the Plans Actually Look Like in Practice
| Plan | Monthly Cost | Usage Reality | Who It Suits |
|---|---|---|---|
| Basic | $20/month | Hits the 5-hour cap frequently; weekly limit is tight | Casual or exploratory use only |
| Pro | $100/month | Most business owners do not hit their monthly limit | The real entry point for agentic use |
| Advanced | $200/month | Even sustained heavy use rarely exhausts this tier | High-volume operators |
The $20 plan is where most business owners start. Run Codex as anything close to an operational employee — pulling emails, organizing files, running research, building automations — and you will hit the limit within days, not weeks. You walk away thinking Codex failed. What actually happened: you ran out of runway before the tool had a chance to prove itself.
The $100/month plan is the actual entry point for agentic use. Most business owners on this plan do not hit their monthly usage limit. There is enough headroom to run real, sustained work across the month without watching the clock.
The $200/month plan exists for heavier operators. At that level, even sustained high-volume use rarely exhausts the cap.
The Most Common Mistake: Blaming the Tool When the Plan Is the Ceiling
When a business owner on the $20 plan hits the 5-hour cap and gets the "try again at 9 PM" message, the natural reaction is frustration with Codex. The tool stopped. The task did not finish.
Codex did exactly what it was configured to do. The cap enforced itself. The plan worked as designed — for casual users.
The problem runs deeper than inconvenience. Long-running goals can sustain 24 to 36 hours of autonomous operation. A 5-hour cap mid-run does not just pause the task. It breaks the workflow. Restarting requires reorienting Codex, re-establishing context, and in some cases re-executing steps that already ran. Hitting the cap once is information. Hitting it repeatedly across routine work means the plan is structurally incompatible with what you are trying to build.
Watch me explain this live to see how usage limits show up in a real Codex session.
How This Interacts With Other Settings
Usage limits connect directly to two other configuration decisions.
Speed setting. The speed slider in Codex is a billing decision wearing the costume of a performance preference. Fast mode burns through usage credits significantly faster than Standard. On the $20 plan with Fast mode running, you will exhaust your window faster than you expect. Standard speed extends how long your credits last without degrading what Codex produces. Treat it like data roaming: leave it at Standard unless the urgency is worth the cost. Learn more about the speed setting.
Goal duration. Codex's goal mode can sustain autonomous operation for 24 to 36 hours or more. The Prevent Sleep setting keeps your computer running so Codex can continue working. But if you hit the 5-hour cap mid-goal, the goal stops — and the longer and more complex the goal, the more disruptive that interruption becomes. Long-running goals require a plan with enough headroom to support them without interruption.
When Hitting Limits Is a Signal to Act
One clear diagnostic: if you are hitting the 5-hour cap during an unusually heavy session, that is expected. Codex ran a lot of work and the window filled.
If you are hitting the cap multiple times a week, across routine tasks, before goals complete — upgrade. The $20 plan is doing exactly what it was designed to do for a user base that does not run autonomous 36-hour goals.
The upgrade from $20 to $100 is the decision that changes the operational ceiling. A $100-per-month tool functioning at the level of a $50,000 annual employee only holds up if the plan can sustain the workload. A capped plan at $20 cannot get there.
If you are already on the $100 plan and still hitting limits consistently, move to $200. At that tier, even heavy sustained use rarely exhausts the weekly cap.
What to Do Right Now
Check your current plan. If you are on the $20 plan and running anything beyond light exploration, the ceiling is already in place.
Track how often you hit the 5-hour cap. Once during a heavy session is normal. Multiple times across a routine week means the plan is structuring your work more than your goals are.
Upgrade before you start the Foundation Phase. The onboarding sequence — file organization, the Business Intelligence Gathering Skill, building the Agent Home Base — requires sustained Codex operation. A cap mid-setup interrupts a process that needs to run to completion. Learn how the Foundation Phase works.
Leave speed at Standard. The single easiest way to extend your usage window without changing your plan. More on speed settings here.
The Honest Summary
Usage limits are a pricing mechanism tied to your plan tier. The $20 plan has a ceiling that does not support agentic work. The $100 plan is where most business owners find enough room to operate. The $200 plan handles high-volume, sustained, heavy use.
If Codex keeps stopping, start with one question: what plan am I on, and was that plan built for what I am trying to do?
The answer takes five seconds to find. The fix takes three minutes to execute.
*
This article is also discussed in LinkedIn post 09.
— Shanee
Use the prompts behind this system
The Growth Academy Skills Dashboard includes 100+ Codex skills and prompts for SMB owners.
See the Skills Dashboard →