Your usage screen is the starting point
Open the official Codex usage dashboard while signed in to the account you use for work. Look for the allowance that is actually blocking you and read its reset time. If you use more than one account or workspace, check the identity before copying anything.
OpenAI documents usage estimates over a five-hour period, with weekly limits also possible. The amount consumed varies with the model and task, so a fixed number of prompts is not a dependable personal budget. The dashboard is the place to check your current limits.
Make a small record you can trust
Write down three things: the window’s name, the date and time shown, and the time zone you are reading. Give your reminder a specific name such as “Codex work account — weekly.” That is easier to recognize than a row simply called “Reset.”
If the page shows several allowances, keep them separate. A reminder for one row should not silently become a claim about another row. When a time is unclear, return to the official screen rather than adding five hours to the current clock.
- Check the account and workspace first.
- Copy the full date as well as the time, especially around midnight.
- Label the window so you know what the timer represents.
- After saving, compare the displayed result with the official screen once.
Plan a work session around evidence
While waiting, collect the information your next task will need: the desired result, relevant files, and a way to check the output. Choose one bounded deliverable to start with. This makes the next session easier to evaluate without relying on a promise about how much work a reset will buy.
For example, prepare a bug report with reproduction steps and an expected result. When access returns, you can begin with that concrete task and review the first result before expanding the scope. This is a planning habit, not a claim that a particular prompt format changes your quota.
If the timer finishes but you are still blocked
Treat the timer as a reminder to check, not a receipt for new usage. Reopen the official dashboard and compare the window, account, and time zone. Read the current message carefully; a different allowance or an access problem may require a different response.
If the app is failing more broadly, check OpenAI’s status page. A service-health update helps investigate an outage, but it does not show your private allowance. For unresolved account questions, keep a short note of the message, the time, and the affected product before contacting official support. Do not include tokens or passwords.