I had a limit reset available with an expiration date of 17/07/2026 (today). It is unclear when exactly do resets expire. At 00:00 of the next day? If that’s the case, I should have it available yet. At 00:00 of the given date? If that’s the case, it should have reseted at 00:00 today.
Since it didn’t reset at 00:00 today, I was totally confident it would reset tomorrow, not at a totally arbitrary time today. This completely messes with my workflow.
I need clear expiration date+time on the resets.
dfil
July 18, 2026, 1:01am
2
If you run Codex via CLI and use /usage, it will tell you the exact time of expiry. But yes, should definitely be added to Desktop app, or just be a set time.
alex_h
July 18, 2026, 3:52am
3
This doesn’t work for me.
/usage only shows my usage history in codex CLI. (linux, kitty terminal)
Any other known ways to get available usage reset counts and expiration date/timestamps?
EricGT
July 18, 2026, 12:06pm
4
For those new to the forum, Welcome!
Thanks for reporting.
I can already tell that this is going to become a hot and rather unusual issue. As users attempt to use the reset throughout the day, some will inevitably try to get as close as possible to what they believe is the cutoff time, which may not align with how the reset actually works.
The following is based on a template I use frequently, with manual adjustments made as needed.
You are welcome to discuss Codex issues on the forum, however the official place to report and track them is the GitHub issue tracker for OpenAI Codex .
I had ChatGPT look for the closest related issue and it identified:
opened 07:48AM - 12 Jul 26 UTC
bug
windows-os
rate-limits
app
### What version of the Codex App are you using (From “About Codex” dialog)?
Ve… rsion 26.707.31428
### What subscription do you have?
ChatGPT Pro
### What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
### What issue are you seeing?
A stored Codex Reset labeled “Expires 7/12” disappeared even though I did not use it.
The Codex usage screen showed that I had four stored resets available. One of those resets was labeled “Expires 7/12.”
I intentionally kept this reset unused because I planned to use it after my remaining weekly usage allowance became low.
The last time I confirmed that the reset was still available was approximately July 12, 2026 at 4:08 AM Japan Standard Time (JST, UTC+9). At that time, the usage screen showed “4 resets available,” including the reset labeled “Expires 7/12.”
I did not click the “Use reset” button, and I did not activate the reset in any other way. I then stopped using my PC and went to sleep.
At approximately July 12, 2026 at 3:50 PM JST, I turned on my PC and checked the Codex usage screen again. The reset labeled “Expires 7/12” had disappeared, and the number of available stored resets had decreased from four to three.
Observed timeline:
- July 12, 2026 at approximately 4:08 AM JST: Four resets were available, including the reset labeled “Expires 7/12.”
- Between approximately 4:08 AM and 3:50 PM JST: I did not use or activate the reset.
- July 12, 2026 at approximately 3:50 PM JST: I discovered that the “Expires 7/12” reset had disappeared and that only three resets remained.
The Codex App did not display any exact expiration time for this reset. It also did not contain any explanation stating that a reset labeled with a particular date could expire at a specific time during that date.
The only information shown to me was “Expires 7/12.” Because no specific expiration time or time zone was displayed or explained anywhere in the app, I understood this to mean that the reset would remain available throughout July 12 in my local time zone and would expire only after the end of that date.
If the actual expiration was scheduled for a specific time during July 12, that information was not communicated to me. There was no way for me to know that the reset might disappear before the end of the displayed expiration date.
This appears to be one or both of the following:
1. A bug that caused a stored reset to disappear without being used.
2. A UI and communication bug because the actual expiration time and time zone were not displayed.
This caused a significant problem because my weekly usage allowance had already decreased to approximately 11%. I had intentionally saved the July 12 reset so that I could use it when the weekly allowance was exhausted.
Because the reset disappeared unexpectedly during the displayed expiration date, I was unable to use it as planned.
### What steps can reproduce the bug?
I cannot reproduce this issue on demand because stored resets and their expiration dates are account-specific and time-dependent. However, the following are the exact steps and conditions under which I observed the issue:
1. Open the Codex usage screen.
2. Confirm that multiple stored resets are available.
3. Confirm that one reset is labeled only with a date, such as “Expires 7/12.”
4. Confirm that the Codex App does not display an exact expiration time or time zone for that reset.
5. Leave the reset unused and do not click the “Use reset” button.
6. Check the usage screen again later on the same displayed expiration date.
7. Observe that the reset has disappeared and that the available reset count has decreased, even though the reset was never manually used.
My observed case:
1. On July 12, 2026 at approximately 4:08 AM JST, the usage screen showed four stored resets.
2. One of those resets was labeled “Expires 7/12.”
3. No exact expiration time or time zone was shown.
4. The Codex App did not explain that the reset could expire at a particular time during July 12.
5. I therefore understood that the reset would remain available throughout July 12 in my local time zone.
6. I did not click the “Use reset” button or otherwise activate the reset.
7. I stopped using my PC and went to sleep.
8. On July 12, 2026 at approximately 3:50 PM JST, I checked the usage screen again.
9. The reset labeled “Expires 7/12” had disappeared.
10. The available stored reset count had decreased from four to three.
Time conversion for reference:
- July 12, 2026 at 4:08 AM JST corresponds to July 11, 2026 at 7:08 PM UTC.
- July 12, 2026 at 3:50 PM JST corresponds to July 12, 2026 at 6:50 AM UTC.
### What is the expected behavior?
A stored Codex Reset labeled only as “Expires 7/12” should remain available throughout July 12 in the user’s local time zone, unless the Codex App clearly displays and explains a different exact expiration time.
The Codex App currently does not state what time during the displayed date the reset will expire. It also does not explain that a reset may expire in the middle of the displayed date.
Because the UI showed only “Expires 7/12,” with no exact time or time zone, I understood that the reset would remain available for the entire day of July 12 and would expire after that date ended.
The number of available resets should decrease only when:
1. The user manually activates the reset, or
2. A clearly displayed expiration date and time has passed.
If a reset actually expires at a specific time during the displayed date, the UI should show the complete expiration timestamp in the user’s local time zone.
For example:
“Expires July 12, 2026 at 3:00 PM JST”
The UI should not display only “Expires 7/12” if the reset can disappear before the end of July 12.
The app should also ideally show the remaining time before expiration.
For example:
“Expires July 12, 2026 at 3:00 PM JST — 2 hours remaining”
### Additional information
Environment:
- Operating system: Windows
- Local time zone: Japan Standard Time (JST, UTC+9)
- Windows time zone setting: (UTC+09:00) Osaka, Sapporo, Tokyo
- Last time the reset was confirmed as available: July 12, 2026 at approximately 4:08 AM JST
- Time the disappearance was discovered: July 12, 2026 at approximately 3:50 PM JST
- Stored reset count before the disappearance: 4
- Stored reset count after the disappearance: 3
- Missing reset label: “Expires 7/12”
- The missing reset was not manually activated or used
The Codex App did not show an exact expiration time for the reset. It also did not provide any explanation that the reset could expire at a particular time during July 12.
Since the app displayed only “Expires 7/12,” I understood that the reset would remain available throughout July 12 in my local time zone. I had no information that would have allowed me to predict that it could disappear before the end of that date.
I have screenshots showing:
1. Four stored resets available, including the reset labeled “Expires 7/12.”
2. The Windows date and time when the reset was last confirmed as available.
3. The later usage screen showing only three stored resets.
4. The Windows date and time when I discovered that the reset had disappeared.
Please investigate the following:
- The exact internal expiration timestamp assigned to the missing reset.
- The time zone used to calculate that expiration.
- Whether account-side logs show the reset as used, expired, deleted, or otherwise removed.
- Whether the reset disappeared due to an incorrect expiration calculation.
- Why the Codex App displayed only “Expires 7/12” without an exact expiration time or time zone.
- Why the app did not explain that a reset might expire before the end of the displayed date.
- Whether the missing reset can be restored if the records confirm that it was never used.
Please also improve the UI so that every stored reset displays:
- The full expiration date
- The exact expiration time
- The applicable time zone
- The remaining time until expiration
I have separately contacted OpenAI Support regarding the account-specific restoration or compensation of the missing reset. This GitHub issue is intended to report the apparent reset expiration and UI communication problem so that other users do not unexpectedly lose stored resets under the same circumstances.
4:08 AM JST — 4 resets available
<img width="521" height="706" alt="Image" src="https://github.com/user-attachments/assets/21e23e99-4814-4eac-bdf0-a8da1be7c2ab" />
3:50 PM JST — 3 resets available
<img width="530" height="647" alt="Image" src="https://github.com/user-attachments/assets/19b0765d-3ac5-4ab5-80eb-6211ee6054fb" />
If that issue matches your problem, consider adding a
If it is not the same issue, try searching the existing GitHub issues for a closer match. If you cannot find one, then open a new issue with as much detail as possible.
alex_h
July 18, 2026, 3:47pm
5
In case helpful to anyone, I told Claude Fable to find out how to run a codex usage limit reset for me and it reported that it was able to run one through the backend CLI and then it updated my codex CLI from 0.144.5 to 0.144.6 and reported that 0.144.5 was neither functioning properly for doing the reset nor for showing the reset that it had run.
I opened a new 0.144.6 and indeed a usage limit reset had been expended and my limits were reset. I have no real idea how Fable did it, and at the moment I don’t care. I’m back to work. Hope this helps someone!
reaction on the GitHub issue page itself, not just on the forum topic, as reactions on GitHub help the developers gauge impact and prioritize work.