#OpenAI

5.6 sol growth is insane. the inference team has done heroic work to be able to support demand. we are going to move mountains to continue to scale, but it is possible there are some hiccups soon.

OpenAI has reduced GPT-5.6 Sol's thinking budgets in an effort to make the model more efficient They essentially bumped everyone's reasoning down by 1... so if you were running Sol Extra High, you now have to set it to Max to get the same effort So we basically don't have Max reasoning anymore, how do you feel about these changes? 🤔

@thsottiaux 简而言之： - 用 Claude 和 Codex 认证设置 CLIProxyAPI - 连接到 Claude Code - 创建 "claudex" 别名来设置一些环境变量 大概花了 2 个提示（不过说实话我已经把代理设置好了）

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.

fwiw, I think that turning Codex into ChatGPT Desktop is a generational fumble

GPT-5.6 Sol on 750 Token/s in Blender. Not sped up. Holy moly. That’s so much more impressive than looking at benchmarks

3D pelican riding a tricycle, plus a pelican riding a pelican, demoed by @edbayes https://percys-garage-3d.openai.chatgpt.site/ fun fact: no one read or edited the code, and no assets were uploaded. this was built entirely by giving 5.6-sol high simple text instructions like “set a goal to render this as accurately as you can”, “add a g-wagon”, and “can you add another ride: a pelican riding a pelican?”