aifollow.news Search
Back

Tibo reset monitor

Codex quota resets and reset cards: timing, eligibility and Tibo’s original posts.

All times in Beijing · UTC+8

Banked reset · In progress

Codex Banked reset · Announced

Codex Banked reset · Announced

Recent source message ·

  • Eligibility:Not specified in the source

Check Tibo’s confirmation post and the usage shown in your Codex account for completion.

Tibo@thsottiaux Source post
Day 3/ The big one is GPT-6 in Chat, but today is also a little celebration day with a new high of 40M active users across Codex and ChatGPT Work. Loading a banked reset in everyone's paid accounts. See you again tomorrow!
Reply / quote context
Open original post ↗

Roundup of Day 2/ 2.1/ Approve for me (auto-review) is now included and does not use usage. Can be between 2-10% of plan when used. Also better for you. 2.2/ Simplified API for builders. 2.3/ Meeting notes integrated. 2.4/ Decisions API live for builders. Will use in the app to improve the experience.

Latest from Tibo · @SimonasLTU1 This was all client-side + network for playground only. Shipped optimized rendering logic that can keep up with ultrafast, try again
Tibo@thsottiaux Source update
@SimonasLTU1 This was all client-side + network for playground only. Shipped optimized rendering logic that can keep up with ultrafast, try again
Reply / quote context
Open original post ↗

Okay, so as a poor peasant with a ChatGPT Pro $100 subscription and like $2 sitting in my OpenAI Playground balance, I decided to test GPT-6.1 Sol ULTRAMOTHERFUCKINGFAST in the API. The result? 12,566 output tokens in 4 minutes 16 seconds. Do the math 😂 That's about 49 tok/s. I don't know... maybe I'll try it one more time to see if that's actually the real speed, but if it is, I'm sorry, calling 49 tok/s "Ultrafast" is pretty horrible...

Reset events · 90 days
8 events
Banked events · 90 days
4 events
Median confirmation gap
13.6 days
Latest reset confirmation

Counts recognized events. Announcements and confirmations are grouped; discussion is excluded. Counts do not establish individual account resets.

Event calendar

Choose a date for resets, banked resets and original posts.

2026 / 10

This month 3 collected events

2026-10 · Event calendar · All times in Beijing · UTC+8
MonTueWedThuFriSatSun
1 2 3 Confirmed 4
5 6 7 Confirmed 8 Banked 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31
  • Source confirmed
  • Estimate passed; unconfirmed
  • Announced
History months

10/2

2026Entire month

Selected 2026-10-02: 0 records.

No records for this day

No reset or reset-card records have been collected for this date. Choose a labelled day to view its records.

Recent record · 2026-10-08 →
How is timing estimated?Sources and rules

Start with the original words.“Next hour” starts at publication. Explicit clock times use their stated time zone; PST and PDT use their corresponding offsets. Missing zones use an explicitly labelled Pacific-local assumption. Estimates add a separate 1–2 hour allowance.

Missing times get a reference window.The reference is 16:30–21:30 Pacific, adjusted for daylight saving time. We count confirmation-post timestamps; these do not establish when a reset button was pressed.

Of 7 collected confirmation timestamps in 90 days, 4 fall in that window.

Source facts and estimates stay separate.Only explicit confirmation posts are source-confirmed. Six hours after an estimated window, a record may say “likely completed (estimate)”; it remains unconfirmed. Banked resets do not restore usage by themselves. Posting time is not delivery time.

Public posts are checked continuously.New posts every 1.0 hours; relevant older sources every 6.0 hours. Messages publish automatically and may be withdrawn by an operator. Check your own quota and banked balance in Codex.

Earliest collected record ·
Coverage is limited to accessible sources successfully read by this monitor, not a complete historical archive. Manual evidence is labelled separately.

Refresh ↻Curated by aifollow.news · Independent of OpenAI