@phils Wow, this is amazing. That home screen is incredible. So glad you like the update! 💙

As a lover of the old 12″ MacBook I'm a bit sad to see that the MacBook Neo weights 2.7lbs (the same as the MacBook Air). There was something really magical about the 12″ weight of 2lbs. It was light enough you could carry it around and almost not notice it. I would (literally) carry it around in an inside jacket pocket.

Physically it’s nearly identical to the Air. I was hoping it would be a return of a Mac which focused around portability. A nice update, but not quite what I wished it was.

@louie oh my, what a beautiful and distinctive font. This is so fab.

@pdadams It is at the mercy of Apple Watch, so time is the hardest one to get 100% accurate…sorry 😞

@rafa The watch is what I’ve found most transformative. The number of times I’ll be out in the garage without a phone or key and then need to open a door is surprisingly high. So good.

@matt_birchler Love that widget you got under there 😉 (and the feature too!)

@stroughtonsmith Your subliminal marketing campaign for Coppice is working. All throughout my run this morning I kept seeing signs for it. 😉

@BenRiceM Very exciting…love the little mascots! Do they have a name?

@benjaminmetzler 💪🏻, not just tracking…6 years of reaching your goal...incredible!

@mattiem For sure, one of the things I'm most glad about for Apple making this a first party thing is that they now have some responsibility for doing a good job with the code Xcode is generating. If their prompts/best practices/models are building bad outputs then they can (and should )fix it.

But on the more positive side they also have a major opportunity, if they get it right, to improve the overall quality of some code written by steering away from known pitfalls or mistakes.

@joethephish Oh man, those animations are 🔥.

@mattiem I’m not. I suppose for each of us the set of ‘best practices' we follow come from a combination of experience and contemplation. But moreover, it is super helpful to know what Apple thinks _are_ the best practices, or another way of saying it maybe is “how they expect/want us to use the API’s”.

Sometimes I find myself with another approach which works better for me, but it's best when I'm doing that intentionally and not accidentally.

Reading through the System Prompts / Hints that Xcode 26.3 injects into the agents is fascinating..and honestly is just helpful documentation to read…essentially concise examples of best practices and implementations recommendations.

Reminds me of the old programming "Guides" which apple used to publish alongside the main documentation which were more focused on how to use the API, than what it was.

There're in: Xcode.app/Contents/PlugIns/IDEIntelligenceChat.framework/Versions/A/Resources

@stroughtonsmith My focus has been on building internal/personal tools for myself at first. It _feels_ like an important skill to develop, but something which I want to learn in a 'safe space'. So I'm up to 9 projects so far. Trying to use Codex/Code as much as possible for these to really understand the edges and where they are good and where they are weak. In my actual apps I've used it mostly just for tracking down bugs, then fixing them myself...so far.

@simonbs The real switch for me, maybe a month ago, was using the agents directly in the project rather than asking questions separately and copy/pasting back in. Which was partly just a result of Xcode being a bit grumpy sometimes about files changing out from under it. The models also really seemed to hit an inflection point late last year where they went from helpful, to "really quite good".

Xcode's direct support has been great so far to tightly integrate into daily use.

Ran into a weird data consistency bug today, where certain step count badges weren't updating correctly when the user changed their step goal. Took me about 10 minutes of poking around, breakpointing and on device testing to find that it was a bad `Equatable` implementation which was tripping up the updater.

Reverted my fix and asked Codex in Xcode 26.3 to give it a try. About 1 minute later it came up with the same fix.

Wild stuff.

@simonbs That is such a fabulous combination of my interests…too bad I don't have a La Marzocco. Thanks for sharing this though super fun stuff.

@caseyliss There is definitely something to that, especially as someone who has programmed essentially alone for years and years. It is just plain _nice_ to be “talking over the code". Kinda like an super advanced version of rubber duck debugging.

RE: https://breakpoint.cafe/@brunoph/116013783280847722

Ha, look at that...that feature already exists.

Biggest thing I've found myself wanting so far in Xcode's generally very good implementation is autocomplete for class/method names in the prompt window. When I'm writing a prompt it would be great to able to precisely refer to things in the app and since Xcode already has the symbol database it seems like adding that should be pretty possible.