Codex account allowances and public reset events run on different clocks. Use the Usage Dashboard for your exact five-hour and weekly reset times and /status for remaining limits; this radar only tracks public announcements and archive history.
Reset pressure = days since the latest event ÷ the historical average gap. It describes where the current gap sits among the tracked events (56 and counting). Above 90% means longer than usual—not an official probability and not a reason to overspend allowance.
For depth, read by era: the archive divides the event history into nine periods with different trigger logic—milestones, incidents, launches and banked resets.
FAQFAQ
Why can't resets be predicted on a fixed cycle?
Because they're event-driven: milestones, incidents and launches all trigger them, and the team never works from a calendar. The base rate (a 6.9-day average) tells you where you are, not what day it lands — which is why the radar publishes a pressure gauge, not fake dates.
Does 100% pressure guarantee a reset?
No. 100% only means the historical average gap has been reached; the archive contains stretches that ran well past it. It answers "where are we in the historical pattern", not "what will happen today".
How were the nine eras defined?
By clustering trigger logic and density: the July spree (10+ resets in three weeks) and the winter compensation era were driven by completely different causes. Every event page carries its era; the full breakdown lives on the About page.