As I understand it, there was an update to Codex where users can choose which reset to use from the settings, and each reset should remain available for around 30 days.
However, on my account, I’ve already had three automatic resets, even though I only used a small portion of each one. This has been frustrating because it interrupts my workflow and makes the experience much worse.
Am I misunderstanding how the new reset system is supposed to work, or is there an issue with my account? I’d appreciate it if someone could clarify why my resets are being consumed automatically.
I am requesting an account-level investigation into repeated and unexpected Codex usage resets.
My understanding is that eligible banked rate-limit resets should remain available for up to 30 days and be redeemed when the user chooses. However, my account has experienced three resets that appear to have been applied automatically, even though I had used only a small portion of the available usage during each period.
This is not simply a request for an explanation of the general reset policy. I need someone to review my account’s reset and usage history because the repeated automatic resets are disrupting active development work, changing the timing of my usage window, and preventing me from planning longer Codex tasks reliably.
Similar reset-availability and account-crediting problems have also been reported by other users in the OpenAI Developer Community, including the discussion titled “Banked resets missing, my account never got any.” This suggests the issue may involve account eligibility, reset classification, or the way resets are being applied.
Please investigate and confirm:
The exact dates and times of the three resets applied to my account.
Whether each event was a global/hard reset or the redemption of a saved banked reset.
Whether any banked reset was automatically consumed, removed, or replaced without an action from me.
Why the resets were applied despite my having substantial unused usage remaining.
Whether the behavior is expected under the current Codex reset policy.
Whether any incorrectly consumed or missing reset can be restored.
Please escalate this ticket to the Codex usage or account engineering team if the first-line support team cannot access the necessary reset logs. A generic description of rate limits will not resolve the issue; I am specifically requesting verification of what occurred on my account.
Account details:
ChatGPT plan: PLUS
Region and timezone: Oman, UTC+4
Thank you.
Global or hard resets refresh the hourly or weekly usage window automatically. They are not saved as credits, and if you keep using Codex afterward, the new usage can make it look like the reset was never applied.
Saved or banked resets appear as reset credits on the Codex usage page. These can be redeemed after you reach a usage limit and may remain available for a limited time.
So the automatic resets you saw were most likely global resets, not banked resets being consumed. Eligibility for saved resets can also vary by campaign and account type, including Plus, Pro, and ChatGPT Business.
I also hope the Codex team improves the harness system, because currently the results are really bad. A few months ago, Codex was much better. Now, even the UI results often seem broken or lower in quality.
I also hope the team expands the weekly usage limits. When a hard reset happens, it should not add one or two extra days before the weekly limit resets. This affects how much value we receive from our monthly subscription.
Because of these issues, some users may start thinking that other models, such as Kimi K3 or Qwen 3.8, are better options. However, we are still trying to continue using Codex, so the team should help users stay with it by improving the quality, limits, and reset system.
If the Codex team cannot improve the current harness system quickly, they should at least allow us to use our Codex subscription inside other IDEs, such as Cursor or Trae IDE. Many of us cannot afford separate subscriptions for Cursor or Trae, but during the free trials, the experience was very good.
Allowing users to use their existing Codex subscription inside these IDEs would be greatly appreciated by many Codex users.
-Dabt Edu
Thanks for laying this out so clearly, @Dabt. The frustration around declining harness/UI quality, weekly limits, and reset timing makes sense, especially when it affects the value of a monthly subscription.
I’m sending this to the team for logging as a feature request. The main asks are better Codex quality and reliability, expanded usage limits with predictable resets, and the option to use an existing Codex subscription in third-party IDEs like Cursor or Trae.
Appreciate you sticking with Codex and sharing specific ways the experience could improve.