Codex provider verdict · snapshot 2026-07-20

How much Codex headroom does ChatGPT Plus/Pro actually buy you?

Currentness: Source audit is overdue or does not match this snapshot. This is a modeled decision aid, not a current recommendation.

Plus/Pro is appropriate for interactive Codex work that fits shared rolling ChatGPT plan headroom. API/BYO is safer for bursty, CI, team, programmatic, or spend-controlled workflows.

Local Codex CLI and ChatGPT cloud Codex share ChatGPT plan headroom. OpenAI publishes five-hour estimate ranges and states weekly rolling caps exist, but the exact weekly ceiling is not published here as a number.

Codex pricingUsing Codex with ChatGPT planOpenAI API pricing

Lived reliability · Jul 12–18, 2026Bounded caution

Capability and a concrete switching account are cautiously positive; quota accounting, capacity stops, and Windows app incidents limit completion trust.

Decision: Trial Codex for the work it appears to fit, but verify quota telemetry and Desktop stability on your model, plan, and operating system before switching.

Confidence / evidence
Moderate · corroborated reports · first-party issue report · community incident report · practitioner report
Corroboration / limit
Separate reports cover fast quota drain, delayed or disputed accounting, capacity stops, and repeated Windows hangs; one practitioner reports switching direction for a specific use case. No receipt measures prevalence. Windows incidents do not establish CLI or macOS reliability, and one switching account is not market momentum.
Evidence before tiers

One shared subscription bucket; an unpublished weekly ceiling.

Interpret Plus and Pro as subscription headroom for local + cloud Codex, not as a guaranteed API-style token allotment.

Shared window
Local + cloud

Codex CLI and ChatGPT cloud Codex draw from ChatGPT plan headroom.

Using Codex with ChatGPT plan
Rolling bucket
5 hours

Tier ranges below are five-hour GPT-5.5 message estimates.

Codex pricing
Weekly ceiling
Unpublished

A weekly rolling cap exists; no exact weekly number is shown here.

Codex pricing
Escape route
API/BYO

Metered API usage is a spend-control decision, not a ChatGPT cap.

OpenAI API pricing
Tier evidence

Plus / Pro 5× / Pro 20×, with estimate labels intact.

ChatGPT Plus

GPT-5.5 · ~15–80 GPT-5.5 msgs / 5h (local+cloud shared)

$20/mo

estimateshared local + cloudnot a guarantee

5h messages
~15–80 GPT-5.5
shared estimate
Tokens / mo
39M
25,000 tok/msg
Eff. $/M
$0.513/M
price ÷ est. tokens
API equiv.
13×
derived vs OpenAI API

OpenAI publishes five-hour estimate ranges and a weekly rolling-cap concept, not an exact weekly ceiling to copy here.

Codex pricingCodex by plan Methodology

ChatGPT Pro 5×

GPT-5.5 · ~75–400 GPT-5.5 msgs / 5h

$100/mo

estimateshared local + cloudnot a guarantee

5h messages
~75–400 GPT-5.5
shared estimate
Tokens / mo
199M
25,000 tok/msg
Eff. $/M
$0.502/M
price ÷ est. tokens
API equiv.
13×
derived vs OpenAI API

OpenAI publishes five-hour estimate ranges and a weekly rolling-cap concept, not an exact weekly ceiling to copy here.

Codex pricing Methodology

ChatGPT Pro 20×

GPT-5.5 · ~300–1600 GPT-5.5 msgs / 5h

$200/mo

estimateshared local + cloudnot a guarantee

5h messages
~300–1600 GPT-5.5
shared estimate
Tokens / mo
780M
25,000 tok/msg
Eff. $/M
$0.256/M
price ÷ est. tokens
API equiv.
26×
derived vs OpenAI API

OpenAI publishes five-hour estimate ranges and a weekly rolling-cap concept, not an exact weekly ceiling to copy here.

Codex pricing Methodology

Visible calculation trail · checked 2026-06-24

Range → selected point: OpenAI publishes ~15–80 GPT-5.5 messages / 5h. The model selects 45 messages, an editorial central estimate inside the range—not the low bound, high bound, or exact arithmetic midpoint. OpenAI Codex range and window · 2026-06-24 ↗

Monthly utilization assumption: 40 active hours/week ÷ 5h × 52/12 = 34.67 five-hour windows/month. The 25,000 tokens/message input is an adjustable editorial workload assumption for context, tool results, history, and output—not a measured average. Change the workload assumption.

Tokens/month: 45 × 25,000 × 34.67 = 39.00M (displayed 39M). Effective $/M: $20 ÷ 39.00M = $0.513/M.

API baseline: GPT-5.5 direct API at 15:1 input/output: ($5.00 × 15 + $30.00) ÷ 16 = $6.5625/M. OpenAI GPT-5.5 API rates · 2026-06-24 ↗

API equivalent: $6.5625/M ÷ $0.5128/M = 12.80× (displayed 13×).

Visible calculation trail · checked 2026-06-24

Range → selected point: OpenAI publishes ~75–400 GPT-5.5 messages / 5h. The model selects 230 messages, an editorial central estimate inside the range—not the low bound, high bound, or exact arithmetic midpoint. OpenAI Codex range and window · 2026-06-24 ↗

Monthly utilization assumption: 40 active hours/week ÷ 5h × 52/12 = 34.67 five-hour windows/month. The 25,000 tokens/message input is an adjustable editorial workload assumption for context, tool results, history, and output—not a measured average. Change the workload assumption.

Tokens/month: 230 × 25,000 × 34.67 = 199.33M (displayed 199M). Effective $/M: $100 ÷ 199.33M = $0.502/M.

API baseline: GPT-5.5 direct API at 15:1 input/output: ($5.00 × 15 + $30.00) ÷ 16 = $6.5625/M. OpenAI GPT-5.5 API rates · 2026-06-24 ↗

API equivalent: $6.5625/M ÷ $0.5017/M = 13.08× (displayed 13×).

Visible calculation trail · checked 2026-06-24

Range → selected point: OpenAI publishes ~300–1600 GPT-5.5 messages / 5h. The model selects 900 messages, an editorial central estimate inside the range—not the low bound, high bound, or exact arithmetic midpoint. OpenAI Codex range and window · 2026-06-24 ↗

Monthly utilization assumption: 40 active hours/week ÷ 5h × 52/12 = 34.67 five-hour windows/month. The 25,000 tokens/message input is an adjustable editorial workload assumption for context, tool results, history, and output—not a measured average. Change the workload assumption.

Tokens/month: 900 × 25,000 × 34.67 = 780.00M (displayed 780M). Effective $/M: $200 ÷ 780.00M = $0.256/M.

API baseline: GPT-5.5 direct API at 15:1 input/output: ($5.00 × 15 + $30.00) ÷ 16 = $6.5625/M. OpenAI GPT-5.5 API rates · 2026-06-24 ↗

API equivalent: $6.5625/M ÷ $0.2564/M = 25.59× (displayed 26×).

Subscription vs API/BYO

The risk model changes at the quota wall.

Subscription headroom

Fixed price, quota-wall risk

Choose ChatGPT Plus/Pro Codex when work is interactive. The upside is predictable monthly spend; the downside is rolling-limit drain across the shared local + cloud Codex bucket.

Using Codex with ChatGPT plan

OpenAI API / BYO

Metered spend, explicit controls

Choose API/BYO when work is bursty, CI-driven, team-distributed, programmatic, or needs spend attribution. ChatGPT subscription rolling caps are not the API risk.

OpenAI API pricing

Choose Codex subscription when…

Interactive Codex headroom is the thing you are buying.

  • You mostly run local CLI or ChatGPT cloud Codex in human-paced loops.
  • A shared rolling window is acceptable because monthly price is predictable.
  • You can pause or defer work when the ChatGPT plan wall appears.
Use API/BYO instead when…

A hidden ceiling would stop work at the wrong time.

  • CI, batch refactors, agents, or scheduled jobs need to keep running.
  • Teams need spend controls, attribution, or programmable routing.
  • Your buyer question is what a run costs, not how much interactive headroom a plan has.
Source receipts

Compact dated receipts for the decisive claims.

DateSourceClaim usedLabelLink
2026-06-24 OpenAI Codex pricing ChatGPT Plus is $20/mo with an estimated ~15–80 GPT-5.5 messages per 5 hours; ChatGPT Pro 5× is $100/mo with ~75–400; ChatGPT Pro 20× is $200/mo with ~300–1600. official price + range open source
2026-06-24 OpenAI ChatGPT plan help Local Codex CLI and ChatGPT cloud Codex usage share ChatGPT plan headroom; treat the five-hour window as one shared local + cloud bucket. official plan mechanics open source
2026-06-24 OpenAI Codex pricing Weekly rolling caps exist for Codex subscription usage, but the exact weekly ceiling is not published; this page does not invent one. unpublished cap open source
2026-06-24 OpenAI API pricing OpenAI API/BYO usage is metered separately by API pricing, making spend control the risk model instead of a ChatGPT subscription quota wall. metered API escape open source