Why usage is not a simple message count
Codex work is agentic. A request can involve reading many files, running tools, generating long outputs, and revisiting context. The amount consumed therefore depends on much more than the number of prompts you send.
Large repositories, long-running cloud work, higher reasoning effort, repeated tool calls, and large context can use substantially more allowance than a small local edit.
What the reset changes
A normal window reset restores availability for that specific window. A public hard reset can restore a wider active allowance. A banked reset must be available and redeemed under the rules shown in the Codex interface.
A service recovery may make Codex usable again without changing quota. That is why outage recovery and quota restoration are tracked separately here.
How to verify your own status
Use the Codex Usage page or limit banner as the account-level source of truth. Compare the displayed reset time, remaining percentage, plan, and active model before assuming a public announcement applies identically to your account.
If the app and web surfaces disagree, record both timestamps and percentages before restarting or contacting support. A time-zone formatting difference alone does not explain different remaining percentages.