OpenAI Codex Pro $100 temporary doubled-usage promo ended May 31, 2026; current site copy now treats Pro as standard 5x unless a new official promo appears.
high impact · checked 2026-06-02 · confidence high
View sourceThe AI Coding Pricing changelog tracks public pricing, usage-limit, credit, plan, and billing-policy changes across Claude Code, Codex, Cursor, and GitHub Copilot. Each entry should show the provider, changed field, observed date, source URL, confidence, and whether users should re-check before upgrading.
$20/mo estimate
Why this plan: Your CLI-heavy workflow at 18h/week creates a 29 intensity score (regular bucket). Pro is the lowest known Claude Code option in the current source data that matches this usage bucket.
Tradeoff: Claude still applies usage, session, model, attachment, and tool limits. Higher plans reduce limit pressure but do not remove it.
Alternative: Compare the full Claude Code pricing guide before committing to this plan.
Next step: Open the official source, confirm Pro availability, then compare it against your real weekly usage and team size.
Caveat: Usage limits are affected by message length, attachments, tools, model choice, and conversation length.
Every row is rendered with provider names as plain text, source links, last-checked dates, confidence, and caveats. Prices and usage limits can change; verify official sources before purchasing.
high impact · checked 2026-06-02 · confidence high
View sourcehigh impact · checked 2026-06-02 · confidence high
View sourcemedium impact · checked 2026-06-02 · confidence high
View sourcemedium impact · checked 2026-06-02 · confidence high
View sourceShow the newest 10 entries with provider, changed field, date observed, date checked, source URL, confidence, and caveat. If no entries exist, do not launch as an empty indexable page.
Explain source types: provider pricing page, provider help doc, terms/policy page, public support note, or observed public report. Core factual tables should prefer provider sources.
Newsletter form copy should be provider-specific and store source_path/provider_interest. Do not use generic newsletter copy.
Pricing, usage limits, credit rules, plan availability, billing-policy changes, and source-page updates for AI coding tools.
No. Entries summarize public changes we observe. Regional, enterprise, promotional, or account-specific changes may not be captured.
Yes. Providers and users should use the contact route to submit a correction with a source URL.
High confidence should come from provider pricing, docs, or terms. Medium may combine provider sources. Low should be treated as anecdotal and not drive core pricing tables.
The newsletter form should capture provider interest so users can ask for Claude Code, Codex, Cursor, Copilot, or all pricing alerts.
Yes. Use changelog entries as a discovery aid and verify the provider source before buying or changing plans.