How do saved Codex resets work?

Available, applied and expired are different states.

A saved or banked reset can wait in an eligible account for you to apply it. The offer controls which allowance it refreshes and when it expires. Receiving the offer does not mean your current usage has already been reset. Read the details in your Codex app or Usage settings before using it.

Set your Codex clock

Copy the expiry you can actually see.

In the Codex clock settings, enable “Saved reset expiry”. Enter the displayed date and time in the device time zone shown beside the form. If the account does not give you a precise expiry, leave this field empty. A social post’s timestamp is not an adequate substitute.

The expiry appears separately from your next allowance reset. A calendar export adds a separate event with a requested alarm 15 minutes beforehand. It does not redeem the reset, reserve eligibility or guarantee that a calendar notification will arrive.

Check the schedule again after applying an offer.

OpenAI distinguishes saved, automatic and purchased resets; the effect depends on the affected allowance. Review the resulting Usage screen after a reset is applied. If the time changes, update your personal clock and export a replacement calendar file.

What LimitSlate can keep for you.

Your account time, optional session time and optional saved-reset expiry stay together in the local clock. Each carries a label showing that you entered it. The browser does not read account cookies or keys, and no entered value is included in a public feed request.

Use the ordinary reset timer for the next scheduled allowance refresh, the expiry field for a saved offer’s deadline and the reset log for public reports. Keeping those three meanings separate avoids treating an old offer reminder as a new refill.