A public board for source-linked AI usage-limit reset events, browser countdowns, alerts, RSS and a free API across major AI products.
Used this tool? Rate it
Used this tool? Rate it
AI Limit Reset Tracker is a public information board for AI usage-limit reset events across Codex, Claude, ChatGPT, Cursor, Gemini, Copilot and Grok. It collects publicly announced events and documented schedules, puts a link beside each record, and exposes the resulting history through a web board, feeds and a public API. It is designed to answer a planning question—what public reset information is available for a group of AI products—rather than to inspect a person's subscription, billing record or remaining messages.
That boundary is the most important way to read the service. A usage limit can be a rolling session allowance, a calendar quota, a vendor-wide reset, a temporary boost or a plan-specific counter. A public event can help explain a broader change, but it cannot reveal whether one private account has capacity. AI Limit Reset Tracker therefore works best as a source-linked status aid: it helps people find the relevant public signal, understand its category and decide which vendor surface should answer the next, account-specific question.
The project describes itself as independent and says it is not affiliated with OpenAI, Anthropic, Google, GitHub or Anysphere. Its data role is deliberately narrower than that of the vendors it tracks. Product names identify the services on the board; source links let a reader check the underlying public announcement; and the site's own labels, estimates and summaries remain the project's interpretation of those public materials.
The documented methodology says the service watches official accounts and vendor status pages, then retrieves the original post rather than copying a third-party retelling. This makes the board more useful than an unlinked timer: when a reset affects a work decision, a reader can follow the source and see whether it refers to a global change, a limited program, a status incident or a different kind of notice.
Candidate posts are labelled as reset, banked reset, boost, limits, incident or note. The methodology says posts over a confidence threshold can be published automatically, while the rest are reviewed by a human; questions and replies do not qualify as resets. A boost, policy change and incident can each affect a next step without being a reset.
The project says it collapses same-kind announcements within 24 hours into one event for interval statistics, while leaving extra posts visible in a signal view. The resulting history is curated rather than a raw scrape of social posts.
Forecasts use historical gaps only after at least eight recorded intervals, and the methodology explicitly describes them as estimates rather than predictions of vendor intent. Separately, the project calculates Gemini API daily quotas at midnight Pacific and Copilot premium requests on the first day of each month in UTC. The distinction is practical: a documented calendar can support a scheduled reminder, while a probability is only a signal that waiting, switching work or checking the vendor may be worthwhile.
Use the board as a decision route, not as a substitute for a provider account page. First identify the type of limit encountered: a short rate cap, a rolling session window, a fixed calendar quota, a billing-cycle allowance or a vendor-wide event. Then use the matching feature. This keeps a public history from being mistaken for a personal balance and avoids treating every countdown as an official promise.
The countdown tool is a manual reminder. The site asks the user to enter a reset time shown by the provider, stores that value in the browser and calculates the next occurrence locally. This is a privacy-preserving design for someone who does not want to grant the tracker account access, but it also places responsibility on the user to enter the right time and retain the relevant browser storage.
The related Chrome extension follows the same model. Its page describes a manual “Hit limit” action, Chrome sync storage for the entered times and a public status-feed request every five minutes. It is not a live usage reader for Claude, ChatGPT or another vendor site. The extension was still described as under Chrome Web Store review when this content was checked, so the browser option should be treated as an announced product route rather than assumed to be generally installable.
AI Limit Reset Tracker is most useful for planning around public signals, watching multiple products and bringing a compact status feed into another workflow; none of those uses turns it into an account entitlement system. It fits the moment before a person decides where to look next, rather than the moment they need a binding answer about a specific subscription.
Someone who alternates among an AI coding tool, a chat product and an API can use the board to see which products have a documented schedule and which depend on public announcements or private windows. A Codex reset tracker can be useful as a planning cue when a team is watching public events. A Claude limit reset still needs confirmation in the relevant account when a person's own five-hour or weekly window is the constraint.
The public API offers a board-status endpoint, a latest-event endpoint and a history endpoint. RSS feeds and an SVG README badge provide lighter-weight options for a dashboard, incident note or project documentation. The advantage is not an official integration with the tracked vendors; it is a reusable, source-linked signal that a team can display alongside its own operational information.
Browser push is presented as an instant notification on the current device without an account. Email uses double opt-in and a one-click unsubscribe. Telegram, per-product feeds, RSS and JSON serve different delivery patterns. Choosing one route deliberately is better than subscribing everywhere and interpreting duplicate notifications as confirmation from multiple sources.
It suits people who switch among several AI products, maintain a lightweight operations view, publish developer documentation or want a low-friction reminder for a reset time already visible in their account. It is also a reasonable fit for teams that want a small public status input rather than a new vendor integration. The service gives those users a common vocabulary for public resets, schedules, incidents and estimates.
It is a poor fit for someone who needs a contractual answer about a bill, an exact remaining quota, a private plan entitlement or a guaranteed reset moment. In those cases, the right next step is the vendor's account, billing, usage or status surface. The tracker can still provide context, but its own terms say it is supplied as-is for information and that forecasts are not promises.
LimitReset is primarily a web board and public data service. Its documented delivery options are a browser page, browser push, opt-in email, Telegram, RSS, JSON/CSV history and a public JSON API. The site also presents a Chrome extension route, but its own extension page says that route is under review in the Chrome Web Store. There is no claim here of native mobile apps, desktop clients or an account-connected integration with each tracked vendor.
The API documentation describes the API as free, keyless, CORS-enabled and cached at the edge for 60 seconds. It documents /api/v1/status for a board summary, /api/v1/{product}/latest for a latest verified event plus forecast, and /api/v1/{product}/events for history, with a CSV variant. It also lists product RSS feeds and SVG README badges.
The countdown route is browser based. Personal reset times entered on the web site stay in localStorage according to the privacy policy, while extension times stay in Chrome storage.sync. These are separate storage choices with different sync behaviour, but neither is presented as an upload of account usage to LimitReset. The extension's only stated network request is the public status feed.
The board, public API, RSS and badges are described as free. That is an access statement, not an unlimited-service guarantee: the terms say abusive API traffic may be rate limited, and the API documentation asks users to link back when they use the data. There is no published paid plan on the pages checked for this review, so this is not a conventional subscription comparison with feature tiers.
| Need | LimitReset route | More appropriate alternative |
|---|---|---|
| A public event or schedule | Source-linked board, history or product feed | The original vendor announcement or documented schedule |
| A private reset time | Manual browser countdown after the user enters it | The vendor's own usage or billing screen |
| Machine-readable public status | Keyless JSON API, CSV, RSS or badge | A vendor API or status page when the product exposes the required account-specific data |
| A binding guarantee | Informational history and estimates only | The relevant vendor contract, support channel or account record |
For an exact personal reset time or entitlement, the vendor account screen is the necessary alternative because LimitReset asks the user to supply account-visible time rather than reading it. For a public announcement, the original vendor source is the necessary cross-check because the board's classification is an interpretation. The service therefore complements official product surfaces rather than replacing them.
The core limitation is scope. LimitReset cannot determine a private account's remaining allowance, and forecasts are historical estimates rather than vendor commitments. A public reset event can coexist with a personal rolling window, a model-specific cap or a billing restriction that remains unchanged. The terms also say the site is provided as-is for informational purposes and should not be the basis for financial or contractual decisions.
The project applies its own source discovery, confidence threshold, classification and deduplication rules. Same-kind notices within a day may be merged for statistics, and questions or replies are excluded from reset status. Readers who need original conditions should follow the link rather than infer them from a label.
Forecasts need at least eight historical gaps and are explicitly not promises. API access is free only for reasonable use, and abusive traffic may be rate limited. The API is cached at the edge for 60 seconds, which is useful for public dashboards but means an API response is not a direct live read of a vendor account. These restrictions are product boundaries, not evidence that the tracker is unreliable; they define what the service does and does not claim to know.
The privacy policy says the site does not sell data and uses Google Analytics for aggregate traffic, with Google anonymizing IP addresses. It says personal reset times entered on the website remain only in browser localStorage and are not sent to analytics. Optional alert subscriptions retain the minimum delivery identifier—a Telegram chat ID, push subscription or email address—and delete it after unsubscribe. The extension states that it collects no data, asks for no website access and keeps entered reset times in Chrome sync storage; its referral links add a UTM parameter so aggregate referrals can be counted.
This review found no product-specific listing in the checked Product Hunt, G2 or Capterra searches and no direct editorial coverage in the checked major technology-media searches. That is a limitation of available independent validation, not evidence of a product defect. The factual content here therefore relies mainly on the service's own public methodology, documentation, policy and terms; readers should keep that source boundary in mind when evaluating operational claims.
No. It does not connect to vendor accounts or manage account state. Use the relevant provider's usage, billing or account page for a private allowance, and use the tracker only for public reset information or a manually entered local reminder.
No. The methodology describes a forecast as a history-based estimate and the terms say forecasts are not promises. A forecast may support a decision to wait or check a provider, but it cannot guarantee a reset.
The service presents browser push, double-opt-in email, Telegram, RSS, JSON and per-product subscription paths. Browser push is device specific, while email and messaging routes require the delivery information needed to send the alert.
The API documentation says it is free and does not require a key. The terms still limit it to reasonable use and allow rate limiting for abusive traffic.
For the website countdown, the privacy policy says entered reset times are stored in the browser's localStorage. The Chrome extension uses Chrome sync storage for the times entered there.
The extension page says it requests no access to websites and does not read Claude, ChatGPT or other provider usage. It uses the manually entered time and the public status feed instead.
