Public updates archive

Tibo updates and reset archive

Tibo is the name used by Thibault Sottiaux, whose public X account is @thsottiaux. This page collects public posts from that account about Codex, with context and links to the original sources. This site is an independent community project.

01 / Completion notice

Latest recorded completion announcement

An announcement does not confirm your account limits have recovered. Please check your own account.

What would you like with your side of reset? It's done. https://t.co/gpNaB6otgy
02 / Public updates archive

Post history

Includes collected posts only, not the complete X history.

JSON data ↗
Clear filtersDate filters use UTC; publication times below use Beijing time.
Matching archived posts 116Page 1 of 6

Good plans are simple. I have one that should result in significantly more usage for everyone. Hope to get it done soon.

Mashed @poteto on the house.

What would you like with your side of reset? It's done. https://t.co/gpNaB6otgy

Category guide · An announcement does not confirm your account limits have recovered. Please check your own account.

Global reset landing by EOD PST time. Enjoy

Category guide · An announcement does not confirm a completed reset

Day 8/ Reset

Category guide · An announcement does not confirm a completed reset

The results of this poll has gotten me confused. I definitely thought it would sway much more favorably in the 2X direction across Pro 100/200/500 at the cost of bringing back 5h limits in order to smoothen the demand curve. https://t.co/zwn7kboMhT

We're all proud of you @birdabo. Thank you for solving this one, hadn't thought about it

With this change, we are not charging long context fees for GPT-6.1 Sol when drawing usage from the subscription.

Day 7/ We have increased default context length for GPT-6.1 Sol to 500k when used through Codex & Work, up from 272k or an ~ 80% increase. We will go higher in the future, but it helps reduce occurrence of compactions and with tasks that require keeping a lot of context and nuance over periods of time. It was carefully tested and is the new sweet spot for most of our users. You can still override it if you want to be higher our lower, with maximum context length of GPT-6.1 Sol of 1M.

Pro users, would you rather have

Put the reset in the bag. All propagated. https://t.co/HGxaD3Zdcj

Category guide · An announcement does not confirm your account limits have recovered. Please check your own account.

The day we reach perfection it will be resets from there onwards https://t.co/I6A9WHOjXT

Global reset by EOD. May the tokens do good things for you.

Category guide · An announcement does not confirm a completed reset

@rohit3a Folks. Why do you think we picked 300k for context length for Codex. We ran the numbers and it’s better. We can run it at 1M too but it would just cost more of the usage. Good defaults are important.

Day 5/ Composer predictions in the desktop app. Often leads to a double take with how on point they are. Included in the Pro plans without consuming usage. https://t.co/02dqoClrWn

Confirmed landed across all accounts. How are we doing so far? https://t.co/tzw7dNX4pN

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! https://t.co/mHSI0PbWfe

Displayed records last synced

03 / Category guide

Understanding announcements

Completed reset announcements

Treat a post as a completion announcement only when it explicitly says that limits have been reset. Check the original for eligible users, limit types and scope; a public announcement alone does not confirm that every account has received the reset.

Reset previews and plans

Posts about preparing, planning or soon performing a reset are previews. Timing can change, and a preview does not mean the reset has happened. Check subsequent announcements and your own account status.

“Banked” resets

Read terms such as banked, saved or for later use in the context of the full original post. They do not mean your current limits have refreshed or promise a specific date or guaranteed reset.

Regular limit refreshes

Limits recovering under the rules that apply to your account differ from an extra reset announced separately. Check the information in your account and official documentation for your limits, reset times and applicable rules.

04 / FAQ

Frequently asked questions

Who is Tibo?

Here, Tibo refers to Thibault Sottiaux, whose public X account is @thsottiaux. This site follows public posts from that account about Codex and keeps links to the originals in the archive.

How does a Tibo reset differ from a regular limit refresh?

On this page, Tibo reset refers to community discussion of reset-related posts from that account; it is not a separate account feature. Distinguish extra resets mentioned in announcements from regular account limit refreshes, and check the original announcement for scope.

Does a reset announcement mean my limits have already been restored?

It does not establish that. Announcements may apply only to certain users or limit types, and previews may not have been carried out yet. Check your actual usage and reset times in your Codex account. This site cannot access or change your personal limits.

Can the next extra reset time be known?

Past records alone cannot establish it. Previous posting times, frequency and community speculation are not promises of another reset. If there is a specific preview, check the original post for the date, time zone and subsequent updates.

Where do the archive records and translations come from?

The archive contains public posts collected by this site, with a source link for each record. Translations are reading aids; check the original if the meaning is unclear. Collection and translation can be delayed, and the archive may not include every post. This site is not affiliated with OpenAI or the account.