Codex Pricing Is Not the $20 You Think

Codex has no standalone price. It rides on your ChatGPT plan, from Free through Go at 8 dollars, Plus at 20, Pro at 100 or 200, and Business at 20 per seat. Since April 2, 2026 every plan meters usage in token based credits worth 4 cents each. OpenAI's help centre puts real spend at 100 to 200 dollars per developer per month.

Updated August 28, 2026 · by the AITerm team

How much does Codex actually cost per month?

Between 100 and 200 dollars per developer, per OpenAI's own help centre, and that is the number worth planning against. The plan line is 8, 20, 100 or 200 dollars. Credits are what turn that into a real bill, because every plan meters usage in token based credits at 4 cents each since April 2, 2026.

You're probably about to open the pricing page, read the grid, and stop there. That grid is the cover charge. It tells you what you pay to be allowed in, not what an afternoon of agent work removes from your balance.

So, here is the arithmetic that nobody puts on the page. A credit is 4 cents, so 25 credits is a dollar. Morphllm's reading of the OpenAI rate card puts GPT-5.3-Codex at 43.75 credits per million input tokens and 350 per million output, which is 1.75 dollars in and 14 dollars out.

Look at those two numbers next to each other. Reading your codebase is nearly free. Thinking about it is not.

The plans, and what each tier really buys

Every tier buys the same Codex. What changes is how much of it you get before the window closes, and the multipliers are the honest way to read the grid: Pro at 100 dollars is the 5x tier, Pro at 200 is the 20x tier. Business seats are 20 dollars per user on annual billing, 25 on monthly, from two seats up.

In practice, the question is never which plan has the features. It is how many hours per day you actually keep an agent busy. One session on Plus is fine. Two sessions on Plus is a plan that expires by lunch.

And yes, one thing quietly disappeared: pay as you go Codex seats for Business, which billed actual token usage rather than a flat seat. New pay as you go seats stopped being available on June 24, 2026, so credit pools are the model now. If you were planning a variable cost line for a team, that door is closed.

How do you read your Codex usage?

Three surfaces, and they answer different questions, which is exactly why people think the numbers disagree. In the CLI, /status reports window consumption as percentages and /usage reports token totals. Credit balances and exact reset timestamps only exist on the web analytics page.

# how much of the 5 hour and weekly windows you have burned
/status

# token totals, and where you redeem a banked reset
/usage
/usage daily
/usage weekly
/usage cumulative

# put the two window percentages in your prompt line, permanently
/statusline   # opt in to five-hour-limit and weekly-limit

Turns out the /statusline trick is the one worth setting up today. It exposes two opt in items, five-hour-limit and weekly-limit, that sit in your prompt and refresh as you work. That turns a command you forget to run into a number you cannot avoid seeing.

Look, for anything longer than today, ccusage is the tool. It is MIT licensed, it reads the logs already on your disk, nothing is uploaded, and it covers Codex alongside Claude Code, Gemini CLI and a dozen other agent CLIs. Run it with npx and you get daily, monthly and per session tables in a few seconds.

One more surface most people never find: banked resets. Plus and Pro subscribers each got one complimentary reset when the mechanism launched on June 11, 2026, and you earn more by referring colleagues, up to three during the promotional window. They expire 30 days after they are granted, and you cannot buy them. Check /usage before you assume a dead window means a dead afternoon.

The five hour window is the real unit

Codex meters a rolling 5 hour window with a separate weekly cap stacked on top, and both are tracked independently. The window opens with your first message. Everything inside it counts: your prompts, the files the agent reads, terminal output, cloud tasks, and the model's own reasoning.

Here's the thing. The part that catches people out is the sharing. Local CLI messages, requests from the IDE extension and tasks you delegate to the Codex cloud all draw from one pool. Delegating to the cloud does not buy you a second budget.

Weekly numbers are not published. Every plan table carries a footnote saying weekly limits may apply, with no figure beside it, which is why the community threads are full of people reverse engineering their own caps. OpenAI temporarily removed the 5 hour limit for Plus, Pro and Business on July 12, 2026, then restored it on July 30. That two week reprieve is the reason half the advice you will find online is already wrong.

Honestly, this is the bit we got wrong for a month. We budgeted Codex in dollars, watched the credit balance, and kept getting stopped anyway. The money was fine. The window was not, and the window does not care that you are willing to pay more.

What we paid per shipped change

Thirty days of Codex on the AITerm repository, one Pro 5x seat plus credit top ups, came to roughly 180 dollars. Over that month the agent contributed to 34 merged pull requests, of which 11 became changes that reached a release. That is about 16 dollars per shipped change, and around 5 dollars per merged PR.

The split is the interesting half. Around 70 percent of our credits went to output tokens, roughly 20 percent to fresh input, and the rest to cached input. That is not a quirk of our repo. It is the rate card doing exactly what an 8 to 1 ratio does.

So we spent two weeks doing the wrong optimisation. We trimmed AGENTS.md, cut example blocks, moved reference material out of the project file, and watched the monthly bill move by an amount we could not distinguish from noise. Then we capped reasoning effort on routine tasks and started writing acceptance criteria into the prompt, and the same month's work cost noticeably less.

Here's the thing. A vague prompt does not make the model read more. It makes the model think longer, out loud, at 14 dollars per million tokens.

Four agents empty one window four times faster

Roughly, yes, and we measured it because the brief is the same everywhere and the number is nowhere. One Codex session doing a sustained refactor kept our 5 hour window alive for about four hours. Four sessions on four git worktrees, same repo, same day, hit the cap in about seventy minutes.

So, that changes the correct behaviour, and this is the part no pricing page will ever tell you. On a subscription, running four agents does not buy you four times the throughput. It buys you the same throughput, compressed into a shorter slot, followed by a wall.

The median in our anonymous daily ping is three simultaneous agent sessions per user. Three is a comfortable number on a 20x seat. On Plus it is a way to be finished by 10am.

Fair question: why not stagger them instead? That is exactly what we do now. Two agents on the heavy work, a third on review, and the fourth task queued rather than launched, because a task started at 80 percent window consumption is a task you will restart later with a cold cache.

There is a quieter multiplier hiding in there too. Every session sends its full conversation with each request, so long lived parallel sessions pay the input cost again on every turn. Cheap per token, but four sessions multiply it, and it lands in the same window.

Is Claude Code cheaper than Codex?

Usually not, and the gap is smaller than the loudest threads claim. The subscription tiers match exactly at 20, 100 and 200 dollars, so price differences come entirely from token consumption. Third party measurements published in 2026 put Claude Code at roughly 1.4 times the tokens of Codex on matched tasks, working out near 23 percent higher cost for equivalent work.

And yes, you will also find a widely shared anecdote about one complex refactor costing 155 dollars on Claude Code against 15 on Codex. Treat it as one. A 10x gap on a single task says more about how the two agents were prompted than about the price of either.

In practice, we run both daily, so here is our actual allocation rather than a verdict. Codex takes the long mechanical runs where the brief is already written: migrations, test backfills, dependency work across many files. Claude Code takes anything where we want the agent to push back.

Anthropic doubled the Claude Code 5 hour caps for Pro, Max, Team and seat based Enterprise on May 6, 2026, and dropped the peak hours reduction. The free plan got neither. That single change dated a lot of the cost comparisons still ranking on this query, so if you read one without a date on it, close the tab.

Six habits that cut our Codex bill

Honestly, none of these are clever. All of them survived a month of measurement, which is a lower bar than it sounds and still more than most advice on this topic clears.

The one we did not put on that list, because it is a product opinion rather than a habit: the window should be visible without typing anything. We built the quota panel in AITerm for exactly this, showing the live 5 hour and weekly state per provider next to each agent session, because the number that stops your afternoon should not live in a browser tab.

The short version: budget 100 to 200 dollars per developer and stop arguing about the 20 dollar line. Optimise output tokens, not context. And measure your own cost per shipped change, because it is the only number that tells you whether any of this is working. That's it.

Going further

Sources

1. Codex Pricing, OpenAI, 2026: the plan grid from Free through Go, Plus, Pro 5x and 20x, Business and Enterprise, and the footnote stating that additional weekly limits may apply without publishing a number.
2. ChatGPT Rate Card, OpenAI Help Center, 2026: credit based pricing for Business, Enterprise and Edu, the per model token rates, and the stated 100 to 200 dollars per developer per month figure.
3. Codex now offers pay-as-you-go pricing for teams, OpenAI, 2026: the pay as you go seat model for Business, since withdrawn for new seats.
4. Codex pricing to align with API token usage, instead of per-message, Hacker News, 2026: the April 2, 2026 switch from message based billing to token aligned credits, and the developer reaction to it.
5. Codex Pricing 2026, Morphllm, 2026: the reading of the rate card used here, 43.75 credits per million input tokens and 350 per million output for GPT-5.3-Codex, the 4 cent credit value, the 5 to 45 credit range for a typical task, and the June 24, 2026 end of new pay as you go seats.
6. OpenAI Codex pricing in 2026, CloudZero, 2026: plan by plan cost breakdown and the variables that move real spend, namely model choice, concurrent instances and automations.
7. Codex 5 hours usage limit feels misleading, OpenAI Developer Community, 2026: the paid user thread documenting how the rolling window behaves in practice and what happens at the cap.
8. Rate limit cost per token jumped on the Plus plan, openai/codex issue 28879, 2026: user measurements of window consumption changing under the credit model.
9. Show remaining Codex credits in the CLI statusline, openai/codex issue 19555, 2026: confirmation that credit balances and reset timestamps live on the web usage page rather than in the CLI.
10. How to Check Your Codex Usage and Rate Limits, SessionWatcher, 2026: the split between what /status and /usage report, the /statusline opt in items, and the July 12 to July 30, 2026 window during which limits were lifted for Plus, Pro and Business.
11. ccusage, Codex guide, ryoppippi, 2026: the MIT licensed local CLI that reads agent logs on disk, its Codex support and the ccusage codex daily command, with costs estimated from public rates.
12. codex-reset, 2026: how banked rate limit resets are granted and redeemed, the June 11, 2026 launch grant for Plus and Pro, the referral mechanism capped at three, and the 30 day expiry.
13. Where to find Codex usage limits, r/OpenAI, 2026: the top ranking thread on this query, and the confusion about where the numbers went that this article answers.
14. Claude Code Limits, 5 hour caps doubled in May 2026, Verdent, 2026: the May 6, 2026 change to Claude Code limits for Pro, Max, Team and seat based Enterprise, the removal of the peak hours reduction, and the exclusion of the free plan. This is the change that dates most Codex versus Claude Code cost comparisons still ranking today.
15. Claude Code vs Codex, 23% higher cost per task, Tech Insider, 2026: the measurement putting Claude Code near 1.4 times the tokens of Codex on matched tasks, and the widely repeated single refactor anecdote treated here as an anecdote rather than a rate.