How LimitSlate tracks Codex and Claude resets

Three kinds of information.

Personal clocks come entirely from the values you enter. They are stored locally and do not connect to an AI account. Service status comes from the official OpenAI and Claude status endpoints. Announcement reports come from the two community sources identified next to every item.

Set your reset clocks

Public data loads only when you ask for it.

Feed and service-status requests start when you select “Refresh public updates”. That action requests two status summaries and two community timelines. Requests are bounded by a timeout. The interface allows at most one refresh per minute in a tab and honors a server’s Retry-After response.

A fetch-completion time means the browser completed a request attempt. It does not mean every provider announcement is in the upstream feed. The Claude community timeline does not publish a freshness timestamp. A Codex upstream timestamp older than six hours is called out when available. Missing sources remain visible as failed checks.

• OpenAI status (status)
• Claude status (status)
• codex-reset.com (feed)
• claudereset.org (feed)

Attribution travels with the report.

Codex announcements are provided by codex-reset.com ↗ (opens in new tab); Claude announcements by claudereset.org ↗ (opens in new tab). Each displayed entry includes its data source and a source-post link. These are community reports, not independent account-level verification by LimitSlate.

Labels are conservative.

We distinguish expiry reminders, saved offers, announced future resets, reported resets, allowance changes and general Provider updates. The source post controls the interpretation. Unknown or malformed records are not promoted into verified facts. We do not count every report as a reset or treat a saved-offer post as a reset. The next-reset estimate described below is arithmetic over dated reports, not a prediction of goodwill offers.

The next-reset estimate and the history snapshot.

At build time, a script reads the two community timelines once, records the size and SHA-256 of the raw response bytes, and keeps only the date, provider, label and source link of each dated report, using the same filters as the live loader. Reports less than two days apart count as one occurrence. For each provider, the gaps between the last eight occurrences of reported or announced resets give a median; the next reset is “expected around” the last occurrence plus that median, and the shortest and longest gap are shown as the range. Fewer than three occurrences, or an unreachable source, means no estimate. The estimate describes public reports, not your account; a reset time you enter always takes precedence on the dial.

Snapshot 2026-10-30: codex-reset.com not reachable at 2026-10-30 17:44 UTC (UNREACHABLE), no entries; claudereset.org read at 2026-10-30 17:44 UTC, 8963 bytes, SHA-256 dce3801729e20cef8cd5eac9a9c55103cb099b212af75d0820a6f19160e35d3c, 15 dated reports kept. The reset log lists every entry of the snapshot with its source link.

The daily allocation.

For more than 24 hours remaining, the desk divides your entered allowance percentage by the remaining days. Within the last 24 hours, it displays the remaining percentage until reset. It does not infer usage, forecast task completion, or automatically refill an expired clock.

Corrections and editorial checks.

Provider guidance was checked on 2026-10-30. It can change after publication. Send a correction with the relevant URL and original provider source using the Contact link in the footer. We do not display fabricated reviews, traffic totals or probabilities.