LIVE|CLI v0.144.0·model GPT-5.6 Sol·verified 2026-07-09
Codex Insider
The unofficial wire for OpenAI Codex.

Codex Usage Limits

Every plan's price, published message ranges, and credit rates in one place — sourced from OpenAI's official pricing page and rate card, and revised whenever OpenAI changes them.

TL;DR — Codex limits today

Codex meters usage in API-token-aligned credits (since April 2, 2026), and OpenAI publishes hard message ranges for just two plans: Plus gets 15–90 local messages per 5-hour window on GPT-5.6 Sol, and Pro 20x gets 300–1,800. Prices run Free $0, Go $8/mo, Plus $20/mo, Pro from $100/mo (5x) to $200/mo (20x), Business $20/user/mo on annual billing, and Enterprise custom.

Overview

A Codex plan sets your price and your ceiling, but the meter underneath is credits pegged to API token prices, not a flat message count. Because each message burns credits in proportion to the tokens it consumes, the published caps are ranges — a heavy multi-file task lands you near the low end, quick edits near the high end. Two plans carry published ranges on the pricing page; the rest are governed by credit balance alone.

Default model
GPT-5.6 Sol
Metering
token credits
Plans tracked
7

What does each Codex plan cost?

Codex has seven plans: Free at $0, Go at $8 a month, Plus at $20, Pro at $100 (5x) or $200 (20x), Business at $20 per user per month on annual billing — a $25 monthly-billing price is reported but not shown on OpenAI's pricing page — and Enterprise at custom pricing. Every paid tier meters actual work in token-aligned credits rather than a flat message allowance.

Free
$0
no charge
no published message range
No published message range
Go
$8
per month
no published message range
No published message range
Plus
$20
per month
15–90
local messages / 5h · GPT-5.6 Sol
Range shown on the official pricing page
Pro 5x
$100
per month
no published message range
Pricing page lists Pro as “from $100/month”
Business
$20
per user / month · annual billing
no published message range
Monthly billing reported at $25 — OpenAI’s pricing page shows only the annual price
Enterprise
Custom
contact sales
no published message range
Existing Enterprise orgs moved to credits April 23, 2026
Promo in effect at our last check
As of 2026-07-09, OpenAI was temporarily including Codex with Free and Go plans and doubling limits on paid tiers. Promos move fast — treat the plan cards above as the durable baseline.

How many messages do you get on each plan?

OpenAI publishes message ranges for two plans only: Plus gets 15–90 local messages per 5-hour window on GPT-5.6 Sol, and Pro 20x gets 300–1,800 per window. The other tiers carry no published message range on the pricing page — their effective ceilings come from credit balances, model choice, and how heavy each task runs.

PlanPricePublished messages (Sol)Notes
Free$0Not publishedCredit-metered
Go$8/moNot publishedCredit-metered
Plus$20/mo15–90 / 5hLocal messages on GPT-5.6 Sol
Pro 5xfrom $100/moNot publishedCredit-metered
Pro 20x$200/mo300–1,800 / 5hMessages on GPT-5.6 Sol
Business$20/user/mo (annual)Not publishedMonthly-billing price reported at $25, not shown on the pricing page
EnterpriseCustomNot publishedExisting orgs moved to credits Apr 23, 2026

Source: OpenAI Codex pricing page (now served from learn.chatgpt.com) and the Codex rate card · verified 2026-07-09.

How do Codex credits work?

Since April 2, 2026, Codex bills usage in credits aligned to API token prices instead of counting messages. On GPT-5.6 Sol, 1 million input tokens costs 250 credits, cached input 25, and output 1,500. OpenAI's own estimate puts a typical developer at $100–200 a month, varying with model choice, instance count, automations, and fast mode.

Token typeCredits per 1M tokens (GPT-5.6 Sol)
Input250
Cached input25
Output1,500
  • The April 2, 2026 switch applied to new and existing Plus, Pro, and Business plans plus new Enterprise contracts; existing Enterprise orgs (including Edu, Health, and Gov) followed on April 23, 2026.
  • Top-up credits are purchasable when you run out mid-cycle, per OpenAI's rate-card coverage — the help-center article itself blocked our direct verification fetch on 2026-07-09, so we're flagging that one as reported rather than independently confirmed.
  • OpenAI's average-spend estimate of ~$100–200 per developer per month comes from rate-card coverage, with the spread driven by model, instances, automations, and fast mode.

How do I check my usage?

Your account's usage dashboard shows remaining quota for the current window, and since CLI v0.144.0 (July 9, 2026) the terminal also surfaces usage-limit reset credit details directly. For exact burn rates per model, keep OpenAI's official rate card open — the dashboard tells you where you stand while the rate card explains why.

The v0.144.0 addition is on the official changelog, and the dashboard is the same surface referenced in the quota-mismatch bug below — worth knowing both, since they can disagree.

Why does Codex say I hit my limit when I haven't?

The best-documented limits bug is a quota mismatch: the account dashboard shows remaining quota while the CLI and app report "usage limit reached." It's tracked as GitHub issue #30041 on openai/codex. If you hit it, confirm your dashboard balance first, then check our errors hub for current workarounds.

Phantom "usage limit reached"
Issue #30041: "dashboard shows remaining quota but CLI and app says usage limit reached." Verified open on 2026-07-09. More Codex error strings, with fixes, live in the error database.

When do Codex limits reset?

The published message ranges are metered per 5-hour window. Beyond that, Sam Altman has pledged a usage-limit reset at every additional million weekly users up to 10 million — and with Codex passing 5 million weekly users on June 2, 2026, five of those pledged resets are still on the table.

That pledge makes user milestones a limits story, which is why we track them on the stats page and cover each reset as it lands on the wire.

Changelog for this page

Every edit to this reference, newest first — that's what living document means here.

2026-07-13
Page launched. Figures verified against the official pricing page and rate-card coverage on 2026-07-09.