Second banked Codex reset lands: Tibo's "Day 28/ Banked 2/2" closes his 28-day series

The second banked Codex reset is out. Tibo (Thibault Sottiaux, who leads Codex at OpenAI) confirmed it on November 1 at 23:27 UTC with four words: "Day 28/ Banked 2/2". That is the last of the two banked resets he announced on October 31, and the last entry in his 28-day run of daily Codex updates.

As with the first one, the post came after the credit, not before it. A third-party tracker, Will Codex Reset?, logged the banked reset at 14:41 PST (22:41 UTC), and users were already saying it had arrived about 40 minutes before Tibo posted. Vaibhav Srivastav of OpenAI quoted Tibo's post shortly after with "banked reset for y'all - enjoy!".

Nothing about the mechanics has changed. A banked reset does not refresh your usage by itself: it sits in your account until you redeem it, and per OpenAI's help page on Codex resets, you can redeem it only once a covered allowance has dropped below 80%. In Codex CLI that's /usage and then Redeem reset; in the desktop app it's under Settings > Usage & billing. Redeeming restarts your usage period, so your next scheduled refresh moves with it. Each promotional banked reset carries its own expiry, shown in your account.

The gaps are the same ones as with the first reset. Tibo gave no plan list, no per-account count and no expiry date. Trackers such as TiboTracker say it's one banked reset per user, and replies come from both Plus and Pro subscribers, but neither Tibo nor an official OpenAI account has confirmed that. At least one reply under Tibo's post reports a bug with the banked reset; we haven't been able to verify it.

If you didn't redeem the first one, you may now be holding two. Several popular accounts in the replies are telling people to save them for an expected GPT-6.2 model. OpenAI hasn't announced one, and the resets expire, so that advice is a bet rather than a plan.

With the series over, the bigger change for Codex users is the one coming in December, when ChatGPT and Codex move to one shared, token-based usage limit on Plus, Pro and Business.