The price stayed. The allowance changed.
2.5× the monthly price. Evaluate the extra capacity against your actual work.
OpenAI now offers Pro 100, Pro 200 and Pro 500 at $100, $200 and $500 per month. New, non-grandfathered Pro 200 subscriptions have a lower included allowance. Eligible existing subscribers retain their previous allowance through October 29, 2026, then move to the lower allowance. [1]
Pro 500 includes Astra Ultrafast. Pro 200 does not gain it through grandfathering or extra credits. Pro is billed monthly; $6,000 is twelve monthly Pro 500 payments, not an annual billing offer. [1]
| Plan | Monthly USD | Astra Ultrafast |
|---|---|---|
| Pro 100 | $100 | Not included |
| Pro 200 | $200 | Not included |
| Pro 500 | $500 | Included |
Check the account, not the headline.
OpenAI’s Pro tier guide states that GPT-6 Astra Ultrafast consumes included allowance at 8× the Standard rate for the same model. This is an allowance consumption rate, not a promise of 8× faster performance. Purchased credits use different rates. [1]
OpenAI’s usage guide states that Pro 100, Pro 200 and Pro 500 currently have no five-hour usage limit in Work and Codex. The plans still have included allowances, shared across Work and Codex. This does not establish unlimited usage or remove limits from every plan or product. [4]
The sources checked on October 2, 2026 do not verify the draft’s exact 20× / 10× / 25× plan quotas, a 200-to-100 weekly message reduction, or a $2,500 transition credit. Work and Codex allowances do not correspond to a fixed message or task count. Check Settings → Usage for the allowance and reset times that apply to your account. [1][4]
A model limit and a credit balance are different: extra credits support eligible features and do not unlock Ultrafast on Pro 100 or Pro 200. [1]
Buy back time you can actually use.
of recovered productive time per month to cover the $300 difference. Excludes taxes and other costs.
The upgrade costs an additional $300 each month. Our suggested decision rule: measure blocked working time, completed tasks, review effort and rework for a representative week. Upgrade when extra capacity or lower latency removes a real bottleneck.
At an illustrative value of $50 per productive hour, six genuinely recovered hours cover the extra $300. This is a planning example, not a promise of savings. Faster generation alone does not guarantee faster delivery.
Give Codex an outcome worth finishing.
These original prompts describe deliverables, constraints and evidence. Replace the placeholders with your actual repository context. Start a new task for a different objective; retain relevant decisions instead of repeatedly pasting the whole repository.
Implement [feature] for [user]. Success means [observable acceptance criteria]. Follow existing project conventions. Keep changes within [scope]. Resolve routine implementation choices and finish the work. Run relevant checks and report the result, changed files and any remaining blocker. Ask only when missing information materially changes the outcome.
Reproduce [failure] using [steps]. Identify its cause, implement a focused fix, and verify the failing behavior plus relevant regressions. Preserve [required behavior]. Report the evidence and any uncertainty.
Inspect [workflow] for repeated context loading, unnecessary tool calls and avoidable retries. Propose measurable improvements. Implement changes within [authorized scope], compare on [representative tasks], and report completion time, cost where available, and correctness.
A small configuration. A clear brief.
Codex reads user settings from ~/.codex/config.toml; project configuration can live in .codex/config.toml for trusted projects. The example below is a starting point, not a way to override plan limits. Confirm model availability in your account. [2]
Our recommendation: begin at medium effort, then compare lower or higher effort on the same real task. Use live search when freshness is necessary. Keep repository instructions short and applicable to the work; remove stale rules and duplicated skill guidance. [3]
model = "gpt-6-astra"
model_reasoning_effort = "medium"
web_search = "cached"Count accepted work.
Track successful tasks, review minutes, retries and total spend together. Keep ChatGPT subscription allowances separate from API token billing. Evaluate API alternatives using actual input, output, caching and tool usage, not a subscription-to-token conversion.
For factory software, include a disconnected-device case, an invalid permission case and a recovery path in your acceptance criteria. Better generated code is useful only when the connected system behaves correctly.
Sources & further reading
- OpenAI: About ChatGPT Pro tiers
- OpenAI: Codex configuration basics
- OpenAI: Rethinking skills and prompts for GPT-6 Astra
- OpenAI: Managing usage with GPT-6 Astra in Work and Codex
Pricing, access and allowances can change. Vendor statements are attributed; prompts and evaluation methods are AiAmbA editorial recommendations. No independent performance testing is claimed.