Limits guide
Three resets that should not be confused.
Your ordinary account window, a special global allowance reset and a banked reset credit can all change available usage. They are not the same event.
The final authority
Check the account, not the rumor.
The allowance and reset timestamp tied to your signed-in account are the final proof for you. Plan limits may differ, and usage depends on the work performed, so another user’s percentage cannot establish your remaining capacity.
In the Codex interfaces, the account usage view exposes current allowance windows. Reset Beacon never asks for your OpenAI password, session cookie or API token.
Why estimates differ
Usage is not a fixed message count.
Codex limits are based on resource use, not one universal prompt allowance. Large repositories, long-running tasks and complex tool work can consume more capacity than short, focused work. Plan entitlements can also change.
That is why Reset Beacon forecasts special reset events, not the number of tasks a specific account can still complete. Use the account’s own usage display for remaining capacity.
If the page and your account disagree
Treat your account as authoritative. A global rollout may still be propagating, the public signal may be stale, or the event may not apply to the same plan. The forecast state never overrides account-level evidence.
Related guide
Have a reset credit?
Banked resets are deliberate account actions. They need different confirmation and safety rules from a global reset.
Read the banked reset guide