How to know when limits reset for graduate researchers in 2026

Q: Is Codex Forecast free to use?

Codex Forecast is free and needs no account. You can opt in to free emails that are sent when a reset actually happens. For programmatic access there is a public API that needs no key and gives stats, paginated reset history, forecasts, and operational health. For a graduate student on a budget, this makes it an option with no setup cost.

Learn how graduate researchers can know when Codex usage limits reset and compare tools that help track reset times.

By SupaKeeper · 2026-10-29

SupaKeeper is published by LunarWerx, which makes some of the tools compared here.

To know when Codex usage limits reset, track your current usage alongside the announcements and the status page OpenAI provides, and use the estimate Codex Forecast publishes when a forecast is helpful.

Option	What it can do	What to check
Codex Forecast	Gives a statistical estimate of when OpenAI will next reset Codex usage limits, combining an account check, announcements, and the status page. ^[1]^[1]	Check whether a forecast fits the need, and confirm the snapshot age and the API options before relying on it.
Existing Codex workflow	Use the usage views and reset announcements already available in the workflow.	Check whether the current approach shows the reset time clearly enough to plan around.
Tracking tool or calendar	A separate tool may provide a way to record and compare reset dates.	Check how it captures and compares reset dates before choosing it.

What you need before you start

This topic assumes you use Codex and want to know when its usage limits reset. Before you start, have a way to see your current usage so you can tell an active reset from a normal change.

Know which projects and active work areas matter, because that affects which usage signals are worth following. Keep any reset announcement you see, with its date, so past resets can be compared.

Decide whether a forecast or a record fits the need. A forecast estimates when the next reset happens, while a list of past resets shows the pattern.

Set up against one clock and one time zone. A reset estimate is only useful when it is compared to a time you can confirm.

Choose the tracking method early and keep it simple. A graduate student on a budget usually wants the least setup that still shows a usable reset time, so compare the effort of each option before committing.

Step by step

Gather the signals that show when a reset happens. These can include the account's usage display, announced resets, and status updates.

Choose one main source to follow. It can be the usage view already in the Codex workflow, an announcement feed, or a separate tracker.

Check the usage display and note the reported reset dates. Record each one so the pattern becomes visible over time.

When a reset is announced, compare it with what the usage display shows, and keep the date that matches what actually happened.

Review the pattern of past resets to expect the next one. A regular gap is easier to plan around than an irregular one.

Set an alert where one is available so you are told when a reset happens rather than checking by hand.

Recheck the tracking method when the way usage works changes. A method that matched an early pattern may not fit a busier semester.

Confirm the reset time in your own time zone before planning work around it, and rebook any dependent task when the estimate moves.

Tools that can do it

Codex Forecast is made by the team that publishes this site.

Codex Forecast is an independent tracker that runs as a website with a public API. ^[1]^[1]

Codex Forecast gives a statistical estimate of when OpenAI will next reset Codex usage limits. ^[1]

To build that estimate it combines an account it checks every 60 seconds, OpenAI staff announcements, and the OpenAI status page. ^[1]

When a measured refill and an announcement disagree, it trusts the measured refill. ^[1] Each reset used in the forecast is listed with a link to where it was announced. ^[1]

Its named-day predictions are scored in public, misses included. ^[1]

You can opt in to free emails that are sent when a reset actually happens. ^[1]

For those who want programmatic access, Codex Forecast provides a public API that needs no key and gives stats, paginated reset history, forecasts, and operational health. ^[1] The API has a published OpenAPI specification. ^[1]

The site and API share a snapshot that is cached for up to five minutes. ^[1] It is free and needs no account. ^[1]

Other approaches include using the usage views and announcements already available in the Codex workflow, or keeping a record in a separate tool after checking what it captures and how it compares reset dates. Compare each option against the exact job of knowing when limits reset.

Common mistakes to avoid

Avoid trusting a single announcement without comparing it to what the usage display shows. A change in usage is not always a reset.

Avoid mistaking the effect of a fee, a project change, or a pause for a reset. Confirm the change against usage and announcements before planning around it.

Avoid ignoring time zones. A reset estimate that looks right in one zone can be a day off somewhere else.

Avoid treating an estimate as a fixed time. A forecast helps planning but does not fix an exact reset moment, so leave slack in dependent work.

Avoid skipping the check that past resets actually match what was measured. An estimate is only as useful as the history behind it.

Avoid forgetting a way to be told when a reset happens. Without an alert, a reset can pass unnoticed during a deadline week.

Frequently asked questions

What does Codex Forecast do?

Codex Forecast is an independent tracker that gives a statistical estimate of when OpenAI will next reset Codex usage limits. ^[1]^[1] It combines an account it checks every 60 seconds, OpenAI staff announcements, and the OpenAI status page. ^[1] Each reset used in the forecast is listed with a link to where it was announced, and named-day predictions are scored in public, misses included. ^[1]^[1]

Can Codex Forecast tell an exact reset time?

Codex Forecast gives a statistical estimate of when the next reset happens, not a fixed moment. ^[1] When a measured refill and an announcement disagree, it trusts the measured refill. ^[1] It is worth treating the estimate as a guide for planning and leaving some slack in dependent work, since an estimate does not fix an exact reset moment.

Is Codex Forecast free to use?

Codex Forecast is free and needs no account. ^[1] You can opt in to free emails that are sent when a reset actually happens. ^[1] For programmatic access there is a public API that needs no key and gives stats, paginated reset history, forecasts, and operational health. ^[1] For a graduate student on a budget, this makes it an option with no setup cost.

How does Codex Forecast track resets?

Codex Forecast combines three sources to build its forecast: an account it checks every 60 seconds, OpenAI staff announcements, and the OpenAI status page. ^[1] Each reset used in the forecast is listed with a link to where it was announced. ^[1] The site and API share a snapshot that is cached for up to five minutes. ^[1] This set of sources gives a view of resets without requiring an account.

What should be checked before using a reset forecast?

Check the age of the data, since the snapshot is cached for up to five minutes. ^[1] Check whether a forecast or a record of past resets fits the need, and compare the estimate with the usage display and announcements. Confirm the reset time in the reader's own time zone before planning work around it, and recheck the tracking method when the way usage works changes.

It is free, with no account and no paid tier. ^[1]

Try Codex Forecast

Sources

Codex Forecast's own description of itself (the product of this site's publisher)