About

TokenResets (Token Resets) tracks public Codex and Claude AI usage-limit announcements. It answers one question with evidence: did a provider actually reset usage limits, for whom, when, and what kind of reset was it?

How the ledger stays current

A scheduled Cloudflare Worker checks the enabled public announcement accounts, enumeration catalogs, and official status feeds every 10 minutes. Detection is not a forecast: it looks only for public evidence that already exists.

1. Deterministic filters reject unrelated rate-limit discussions and non-definitive future claims.
2. Source identity, statement context, timing, duplicate records, and affected scope are checked.
3. Qualifying evidence is written to the ledger and queues a static-site rebuild.
4. Failed rebuild or notification operations remain in an outbox for another delivery attempt.

No generative AI classifies events, fills missing fields, or writes summaries. See themethodology for inclusion rules and thesource registry for the public endpoints currently monitored.

Daily integrity check

At 00:00 KST, automation audits the previous Korean calendar day. It checks the 144 expected detection opportunities, failed runs, source freshness, newest upstream candidates against the ledger, pending operations, database invariants, and the public API, homepage, sitemap, RSS, and Atom surfaces. Bounded automatic recovery runs before one consolidated Telegram report is sent to the operator.

A healthy report means the monitored paths agreed at inspection time. It does not prove that a provider made no unmonitored or private announcement.

What this is not

• Not a personal usage meter. This site never reads your account.
• Not a way to bypass or extend usage limits.
• Not affiliated with any provider listed here.
• Not a prediction service. We do not guess when the next reset will happen.

Privacy

Your personal reset timers stay in your browser. They are stored in IndexedDB on your device and are not sent to TOKEN RESETS. Website delivery, analytics, API rate limiting, and anonymous reactions are explained in the privacy notice.

• We never ask for provider credentials, session cookies, or API keys.
• The application database does not store raw IP addresses.
• API abuse controls and reactions use salted, pseudonymous hashes.

Operator

TOKEN RESETS is operated by DDALGAK STUDIO, a Korean sole proprietorship. Seebusiness information orcontact the operator.

Trademarks

Provider and product names are used only to describe what is being tracked. They belong to their respective owners. This service is independent and not endorsed by any of them.

Corrections

If something here is wrong, it will be corrected as a new revision with the reason stated, and the earlier version will remain visible. Events are never quietly deleted.