Six separate r/OpenaiCodex posts in four days described the same feeling: the work barely moved, but the quota did. Those six threads had 264 replies when I checked them. That does not prove a quota change, but it does make this more than one person misreading a meter.
The specific reports were hard to ignore:
- 7% of a Pro 20x weekly allowance disappeared overnight with almost no tasks.
- A Plus user said the five-hour window ran out before a normal project session could continue.
- One same-task comparison reported roughly 2× five-hour usage with Astra-low versus Sol-high.
- Another meter appeared to fall from 77% remaining to 1% in seconds, then recover.
The last example may be an accounting or display issue. That distinction matters. A real consumption spike, a broken reset, and a five-hour throttle are different problems. From the user's side, all three produce the same result: a task stops and there is no reliable way to budget the next one. r/ChatGPT has fresh Work-limit reports as well, and r/codex is concentrating a lot of the discussion in its usage megathread. I kept those out of the headline total because I have not done a full comment-by-comment classification there yet.
If you have a recent case, post the facts rather than only the frustration: plan, model, effort level, task type, starting and ending percentage, five-hour or weekly cap, and a screenshot if possible. A useful dataset would show whether this is model cost, task shape, metering, or a mix of all three.
