Amir

When Claude writes code, it signs the commit: Co-Authored-By: Claude. I'm paying for the model, and it still takes a credit line. Okay, fine. But co-authorship is a claim about contribution. And that logic should work both ways. So what about all those people who involuntarily "contributed" the training data? You know, half the internet. Don't they deserve co-authorship on the models?

I use 19m gpt 5.6 sol tokens yesterday. Assuming 80% is output and 20% is input (my claude usage is like this) It would cost me roughly $475. OpenAI is so generous.

We applied the resets automatically because of two reasons. 1. It is not possible to use a banked reset from the web or mobile ChatGPT. We are launching it next week and it will require a bit of education for all our new ChatGPT Work users. 2. The system is under a lot of pressure and full resets are more predictable in how they affect load on the infrastructure. This helps us keeping things stable in the first 48 hours of the launch. And we will use banked resets once we are back in the normal operating cadence!

Hello beautiful people! We have reset usage limits across Codex and ChatGPT Work. And another one will come later in the day. Rejoice. Now that I have your attention, a quick update on ChatGPT Work, Codex and all the updates we shared yesterday. We’ve spent the last 24 hours reading feedback, looking at usage patterns, and talking with many of you. The short version is that there is a *lot* of excitement for GPT 5.6 Sol, ChatGPT Work on mobile & web, but also that we didn't get everything quite right. - We made it too easy to use the highest-compute settings without making the impact on usage limits sufficiently clear. - We reorganized the desktop app in one bold move, making familiar things like chats and projects harder to find. - Our launch framing was focused on ChatGPT Work and to some of our Codex fans it made it feel like Codex was going away over time. Absolutely not our intention, we love Codex and it is here to stay. - And we introduced regressions for some existing multi-agent workflows, alongside a collection of rough edges in plugins and other parts of the experience. We’re landing a first set of improvements today. We’re resetting usage twice so people can keep experimenting, changing defaults and the model picker so they don’t push people toward unnecessarily expensive settings, fixing several plugin submission issues, improving how we represent Codex in the product, and cleaning up some of the most immediate desktop problems. A larger set of improvements will land next week. We’re bringing chats and projects back into the sidebar in a more familiar and customizable way, making usage and reset timing much more visible, clarifying when to use ChatGPT Work and when to use Codex, and addressing the many other smaller pieces of great feedback we've had. The ambition behind this launch hasn’t changed. We think bringing ChatGPT and Codex together into a workspace where people and agents can collaborate is a very important step forward. But an ambitious direction doesn’t excuse avoidable confusion or regressions in the first version. Please keep the feedback coming. We’re moving quickly, and you should see the experience already get better with a few updates today; and substantially better again next week.

POV: gpt 5.6 decided it would be ultra smart to send an email on your behalf without discussing anything about it with you

To celebrate the launch of GPT-5.6 Sol, we will reset the rate limits again (twice) across ChatGPT Work and Codex over the next 24 hours. We want you to have the time to truly try ambitious tasks and get the hang of it. Happy exploring!

Sydney, Australia 🇦🇺 Hurstville. This is an example of monoculture, but it's certainly not Australian monoculture. For those who are unfamiliar with Sydney, this is not Chinatown. This is just one of many suburbs full of people who have refused to assimilate for decades.