IssueRaiser

[Meta] Abnormal Codex usage/quota depletion and usage-accounting inconsistencies — cross-report tracker

## Summary There are now many open Codex reports describing a common **user-visible symptom family**: > Codex subscription quota or purchased credits are depleted materially faster than the user's prior baseline or local/token evidence would predict, sometimes with abrupt changes during an unchanged usage window, passive/background consumption, or usage records that do not reconcile with the meter. This meta issue is intended to **link and compare those reports in one place**. **This does not assume they all have one root cause.** The evidence already points to several potentially independent mechanisms: entitlement/provisioning, server-side weighting/accounting, background activity, retries/polling, context replay, analytics/ledger gaps, and client-side workflow amplification. The purpose is to stop treating each report as an isolated anecdote and give maintainers a single place to correlate timelines, fixes, regressions, and account-side reconciliation. ## Why a tracker is warranted Several reports contain controlled or unusually strong evidence rather than only subjective impressions: | Issue | Evidence / symptom | Why it matters | |---|---|---| | #28879 | Same GPT-5.5 plan/app: reported limit cost per token jumps ~10–20x between June 12 and June 18 despite smaller prompts and near-zero reasoning | Strong pre/post comparison; not Sol-specific | | #30939 | Usage reported 5–10x faster since mid-June; one message consumed 46% of a 5-hour window | Early recurring report

Posted by FromAriel on Aug 27, 2026, 11:24 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments

pricing (SaaS)

[Meta] Abnormal Codex usage/quota depletion and usage-accounting inconsistencies — cross-report tracker

FromArielAug 27, 2026, 11:24 PM

## Summary There are now many open Codex reports describing a common **user-visible symptom family**: > Codex subscription quota or purchased credits are depleted materially faster than the user's prior baseline or local/token evidence would predict, sometimes with abrupt changes during an unchanged usage window, passive/background consumption, or usage records that do not reconcile with the meter. This meta issue is intended to **link and compare those reports in one place**. **This does not assume they all have one root cause.** The evidence already points to several potentially independent mechanisms: entitlement/provisioning, server-side weighting/accounting, background activity, retries/polling, context replay, analytics/ledger gaps, and client-side workflow amplification. The purpose is to stop treating each report as an isolated anecdote and give maintainers a single place to correlate timelines, fixes, regressions, and account-side reconciliation. ## Why a tracker is warranted Several reports contain controlled or unusually strong evidence rather than only subjective impressions: | Issue | Evidence / symptom | Why it matters | |---|---|---| | #28879 | Same GPT-5.5 plan/app: reported limit cost per token jumps ~10–20x between June 12 and June 18 despite smaller prompts and near-zero reasoning | Strong pre/post comparison; not Sol-specific | | #30939 | Usage reported 5–10x faster since mid-June; one message consumed 46% of a 5-hour window | Early recurring report

Comments (0)

No comments yet. Start the discussion.

Comment on this issue