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.
What if you could let an yolo agent compile your Xcode projects without giving it the keys to your entire Mac?
That's xcbox (very pre-alpha): Apple container-based sandboxing for Xcode. No babysitting, no "my Mac exploded" vibes 😄
https://t.co/K2ZTOdwH1Z
My attempt to protect users from scam apps on the @AppStore has gotten my Apple Developer account flagged for termination - ironically, for "dishonest activity".
Unless it's reversed by June 30, all new installs of Sparrow Wallet will fail, and development on macOS will end.
The context: since 2023, more than a dozen fake "Sparrow" apps have appeared on the App Store, as recently as April this year. Users have contacted me after losing their savings, in some cases their life savings, to these impersonators.
I'm the developer of the real Sparrow Wallet, a desktop app, and I hold the registered US trademarks for the name and logo. I have publicly warned @Apple and the community about these fake apps from early 2024, but they keep appearing.
The app @Apple flagged was a placeholder that was never published. Its only purpose was to warn users that Sparrow is desktop-only and that other "Sparrow" apps aren't mine. This approach may have been misguided, but there was nothing dishonest about it.
I'm confident this is an automated misclassification that Apple would reverse on review - but I may be terminated before a human ever looks at my appeal. The cost would fall on @Apple's own users: blocked installs and no updates for a tool people rely on, which opens the door for more fakes.
If you value Sparrow, a repost would help. @AppleSupport
@VincentLoi1204 It’s very finicky. I’ve only been able to make it work with the complete and structured guidance, any of the other configurations just doesn’t work for me either.
So uh… Apple should really rethink the Private Cloud Compute developer access limitation. I do happen to have an app that’s had more than 2 million downloads. An app that’s been in the App Store for over 10 years. And I’m also not making any real money with it 🥲 #wwdc26
It's very cool that Apple shipped a 20B parameter on-device.
You can't put 20B parameters in RAM at any reasonable precision. To make it work they are using pretty exotic architecture by today's standards.
A small model predicts from the query (or prompt) which experts to load from Nand into RAM. The key distinction from a typical MoE is that you do this once per query and then generate all the tokens with the same experts (instead of switching the experts for every token).
Here are the skills that ship with Xcode 27.
Apple did a fantastic job with these (no surprise) from what I've poked around and looked at. Baseline SwiftUI guidance, and nuggets on how to use the new stuff like the reorderable APIs.
$ xcrun agent skills export --output-dir ~/Desktop/xcode-skills
Apple still sets the bar for software design.
The way movies on Vision Pro reflect in the icy river of the new Iceland environment during the day, and how the snow softly glows at night, genuinely gives me goosebumps.
Apple has confirmed to @9to5Mac that the Mac Pro is being discontinued with no plans for future hardware
It's also no longer available on Apple's website as of Thursday afternoon
The end of an era 🧀
Your comic reader should be as gorgeous as the stories inside it.
Introducing Glassy Comics, private, local-first, no subscriptions and built with full liquid glass glory 🙌
https://t.co/F6nxXDf3bG
#comics#ios#ipad
It’s so good to have Stacktrace by @johnsundell and @_inside back after two years.
Seeing it show up in my Overcast feed genuinely made my heart skip a beat.
I’ve honestly missed it quite a lot 🥹
@stacktracepod
Since a recent firmware included components for a virtual iPhone, I decided to see if I could boot one up. This is a virtualized iPhone 16 running iOS 26.2.
Don't get too excited, as this required a lot of IPSW patches and SpringBoard crashes when I swipe up in the setup screen.
@newlooklurker@shitpost9000@aboutzeph It’s both. The low-tech alternative would be for the watch to display a numeric code that the user has to type on their phone. Since the phone has a camera, you can use a QR Code, but a normal QR Code is not as cool as this 😄