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!
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.
Tibo 最新推文 · @SimonasLTU1 This was all client-side + network for playground only. Shipped optimized rendering logic that can keep up with ultrafast, try again
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...
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.
Update on rate limits in Codex.
We’ve found (a) some inefficiencies when using images in long sessions with multiple compactions (b) high p95+ usage for Computer History (c) a feature that was meant to generate conversation titles that was draining a bit more usage than intended. And we have a tiger team combing through everything and shipping fixes tomorrow. We also found a novel approach to drive efficiency up significantly that is completely unrelated and we will be working on next week.
As part of some of the fixes tomorrow, we will also do a full reset of the usage for all paid subscriptions.
See you then.
Update on rate limits in Codex. We do see that for some users the cache hit rate has been worse this week than the stable state the weeks before. This could explain that usage is draining somewhat faster for those users as hitting the cache consistently is an important component of being efficient.
We are investigating and will have an update tomorrow.
Update on rate limits in Codex.
We’ve found (a) some inefficiencies when using images in long sessions with multiple compactions (b) high p95+ usage for Computer History (c) a feature that was meant to generate conversation titles that was draining a bit more usage than intended. And we have a tiger team combing through everything and shipping fixes tomorrow. We also found a novel approach to drive efficiency up significantly that is completely unrelated and we will be working on next week.
As part of some of the fixes tomorrow, we will also do a full reset of the usage for all paid subscriptions.
See you then.
Tibo@thsottiaux
来源原帖