How to Understand OpenAI Codex Usage Limits on the $20 Plan
I was hesitant to commit to OpenAI Codex’s $20 subscription. The pricing page mentions “usage limits” but doesn’t spell out exactly what you get. Would I hit a wall mid-project? Would I need to upgrade after a week?
After using it extensively for a month, here’s what I learned about the actual limits.
The Confusion
OpenAI’s pricing page says “$20/month” with “usage limits apply” — but what does that actually mean for a developer?
I couldn’t find clear documentation on:
- How many requests per day?
- When do limits reset?
- Is there a weekly cap?
What I Discovered
The $20 plan uses a dual-limit system:
┌─────────────────────────────────────────────────────┐│ $20 Plan Limits │├─────────────────────────────────────────────────────┤│ Daily Limits ││ ├── Reset every 5 hours ││ ├── Multiple sessions per day ││ └── Not a fixed "per day" count ││ ││ Weekly Limits ││ ├── Overall usage cap ││ └── Resets weekly ││ ││ Promotional Periods ││ └── 2X limits until April 2nd (current) │└─────────────────────────────────────────────────────┘The 5-hour reset cycle was surprising. I expected a midnight reset, but instead it’s a rolling window. This actually works better for my workflow — I can code in the morning, take a break, and have fresh limits by afternoon.
Real-World Usage
I work in large codebases that require loading significant context for targeted updates. During weekdays, I’m in Codex for 6-8 hours. Weekends, I work on personal projects for another 4-6 hours.
Here’s my typical week:
Day Hours Limit Status───────────────────────────────────Monday 7 hrs ████████░░ 80%Tuesday 6 hrs ████████░░ 75%Wednesday 8 hrs █████████░ 85%Thursday 5 hrs ████████░░ 70%Friday 4 hrs ███████░░░ 65%Saturday 5 hrs ████████░░ 60%Sunday 3 hrs ██████░░░░ 50%───────────────────────────────────Week End: ~30% remainingEven with the promotional 2X limits, I’m not hitting walls. The limits reset multiple times during issues or outages, which OpenAI has been handling well.
Comparison With Competitors
I tried the alternatives before settling on Codex:
| Tool | Base Price | Usage Experience |
|---|---|---|
| Codex | $20/mo | Never hit limit, 20-30% remaining |
| Claude | $20/mo | Hit limits faster on large codebases |
| Cursor | $20/mo | Good but less generous |
| Windsurf | $20/mo | Similar to Cursor |
The Reddit user Kaushik_paul45 put it well: “No one provided this much usage on a base subscription.”
When You Might Hit Limits
The limits are generous for typical development, but you could hit them if you:
- Load massive codebases repeatedly — Each context load counts against your allocation
- Run overnight sessions — The 5-hour reset might interrupt long refactors
- Share your account — Multiple people using one subscription will drain it faster
- Ignore the reset schedule — Planning around the 5-hour windows maximizes value
How I Optimize My Usage
I’ve developed a workflow that respects the limits:
Morning Session (9 AM - 2 PM)├── Load project context once├── Batch related changes together└── Avoid re-loading files unnecessarily
Afternoon Reset (2 PM - 7 PM)├── Fresh limits available├── Continue with new features└── Review and commit changes
Evening (7 PM+)├── Light usage only└── Save heavy work for next resetThe key insight: load context once, work in batches. Don’t ask Codex to re-read the same files repeatedly.
The Bottom Line
For $20/month, Codex provides enough usage for:
- Full-time professional development
- Large codebase navigation
- Weekend personal projects
- Daily coding sessions with breaks
The 5-hour reset cycle means you get multiple “fresh starts” per day, not just one daily allocation. During promotional periods, the limits are even more generous.
If you’re on the fence, the base tier is worth trying. I expected to upgrade within a week — instead, I ended most weeks with 20-30% unused.
Final Words + More Resources
My intention with this article was to help others share my knowledge and experience. If you want to contact me, you can contact by email: Email me
Here are also the most important links from this article along with some further resources that will help you in this scope:
Oh, and if you found these resources useful, don’t forget to support me by starring the repo on GitHub!
Comments