Tibo
’s public posts↗
Last checked · 5 Sept 2026, 17:31 UTC
The latest signal is unavailable.
We could not load the data. This does not mean there is no reset signal.
Loading the latest reset signal
Reset-card grants have been announced.
· Tibohas announced: A full reset card was announced for all Plus, Pro and Business users.
Tibohas announced: A full reset card was announced for all Plus, Pro and Business users.Direct reset
No new signal
The next reset has not been scheduled.
Reset card
Cards announced
Latest post ·
Times shown in UTC
- Latest direct reset
- UTC
- Latest reset-card post
- UTC
- Direct resets in the past 30 days
- 5
- Typical time between resets
- 5.8 days
Tibo’s latest reset post
将为所有 Plus、Pro 和 Business 用户发放完整重置卡。
“Because we are beyond happy to have Astra rolled out today ahead of schedule and you have been super patient with us (not really, but it’s ok!)… we will do the full banked reset today too for all Plus, Pro and Business users. Lands end of day. Happy Astra day and enjoy a phenomenal weekend. PS: If you create the account or upgrade before 8pm PT you will get it too. Still time!”
Reset history curve
Cumulative direct resets and reset-card posts over the past year.
Hover or tap a point for the date and post.
Reset and reset-card history
Times shown inUTC
Because we are beyond happy to have Astra rolled out today ahead of schedule and you have been super patient with us (not really, but it’s ok!)… we will do the full banked reset today too for all Plus, Pro and Business users. Lands end of day.
Happy Astra day and enjoy a phenomenal weekend.
PS: If you create the account or upgrade before 8pm PT you will get it too. Still time!Some Plus and Business users won't yet get access to Astra today, we've got you covered with a banked reset. Lands by end of day and if you create your account by 8pm PT then you'll get it too.We will give one banked reset for every day you don't have access to Astra on your paid ChatGPT plan, starting today. Team is moving mountains to give access as fast as we can.
First one will land in ~ 3 hours. There is still time to create your account if you don't have one.What I wanted to say yesterday is that we hit 25M active users and to celebrate we have now reset usage for all paid subscriptions for ChatGPT Work and Codex.
See you soon for more news from The Reset Company.We are reseting usage for all paid users of Codex and ChatGPT Work.
Please continue reading for an update on Codex usage limits. The team has been working around the clock, going through thousands of reports and shipping fixes.
Depending on how you use Codex, you should see your usage go between 10% and 50% further than before.
We really went with a fine comb, with many uncovered small things being longstanding and here is what we found and fixed:
- Compaction. We were keeping old images during compaction, sometimes making the context large enough to trigger compaction again. After the fix, usage dropped around 10% for users making heavy use of images. Fixed.
- Memory. Background memory workers could inherit Stop hooks and keep running when the hook wouldn’t let them finish. This affected fewer than 1% of users, with the long tail being pretty bad and we saw one example thread check whether it could stop 15,000 times. Fixed.
- Goals. In some cases, a set /goal could finish and then keep going past the intended stop condition, or the model would keep retrying broken tools without stopping. We saw examples consume anywhere from 15% to 70% of a weekly allowance. Fixed.
- Automations. Some custom schedules could run more frequently than configured. Fixed.
- Subagents. Smaller models (e.g. Luna) sometimes picked more capable helpers without being explicitly asked. The same was true where the orchestrating model not running in /fast mode could request sub-agents to run /fast. Fixed.
- Computer History. The older implementation could lead to repeatedly summarizing overlapping activity. For some cases we saw it consume up to one fifth of the weekly usage per week. Fixed.
- Rolling task summaries. Ordinary turns were triggering extra background requests. These added about 1% to token usage. Small each time, but it adds up. We have disabled this.
- MCP. Some tool results could be encoded twice. We also found tool instructions getting cut off and fetched again. Fixed.
We’ve also made architectural changes to prevent these from regressing and our teams will get paged if it happens regardless. We are also working on showing you directly in the app where your usage goes so you don’t have to guess.
Goes without saying that we’re resetting usage limits and I hope you enjoy a very nice Saturday!Good Sunday. Reset has been propagated to accounts and we landed some fixes to usage for things mentioned yesterday as issues we found. You should feel a positive difference. More to come tomorrow and will keep communicating.