Many users report abrupt changes in the usable capacity of Codex and Work plans, especially Pro. The immediate question is not whether one universal bug exists. It is:
What did I buy? What consumed it? Can I independently reconcile the two?
Do not buy extra credits or rerun expensive failures just to investigate this. When an incident occurs naturally, preserve the evidence you already have: date/timezone, plan, client/version, model/reasoning level, service tier if known, parent/subagent count, task duration, allowance or credit balance before and after, session/feedback IDs, screenshots, and sanitized logs. Unknown fields stay unknown.
Structured incident schema:
Different cases may have different causes: model choice, concurrent subagents, duplicated context, Priority/Fast, compaction, runtime defects, ordinary charging, or accounting errors. Explained cases are useful evidence. Unreconciled cases become stronger only after plausible alternatives are tested.
For Pro users, predictability is the central product issue. If a plan is described as providing 5x or 20x usage, customers need enough stable accounting to understand what that multiplier means in practice.
Useful product changes are straightforward:
auditable per-request usage;
visible parent/subagent attribution;
visible service tier;
understandable allowance units;
transparent effective pricing;
reliable spend caps;
enough history to reconcile disputed depletion;
correction or restoration where provider records establish an error.
My public forensic package is one case study, not a universal explanation:
Zenodo:
Do not post credentials, private prompts, customer material, payment details, or raw account identifiers. Counterexamples and corrections belong in the same record as complaints.
We are not powerless. We are fragmented. Fragmentation is an engineering problem.
Can you clean up your markdown please? That’s pretty messy. Did you paste markdown into the WYSIWYG composer? (there’s a switch in the composer). Perhaps you can paste it in again in the markdown mode.
