What macOS 26 Changed for People Who Type
Every once in a while, Apple ships an operating system that changes the rules for a whole category of software without meaning to. macOS 26 did that for people who type, and I want to talk about what actually shifted, because most of the coverage missed it. The story was about Apple Intelligence, the features, the demos, the chips. The real change was quieter, and it's still settling.
I build an autocomplete for the Mac, so I've got a front-row seat to this particular shift, and I've thought a lot about what it means. Here is the honest version.
The thing that actually changed
Here is what macOS 26 did that matters. It put a genuinely capable on-device writing engine on every supported Mac, free, bundled with the OS. Not a toy, a real engine that can complete, rewrite, and summarize, running locally, with your words never leaving the machine. That is the change. Not any single feature, the engine itself, sitting there on millions of Macs, free.
The consequences are bigger than the features. For a decade, the people who wanted their Mac to help them write had to install something, a cloud tool or a local one, and the idea of machine-assisted writing was a category you opted into. After macOS 26, it's a default. The Mac can do this now, out of the box, and that changes what people expect from every other writing tool.
- You opted into a category
- The Mac itself did not do this
- Cloud tools were the default way to get it
- On-device writing engine, free, bundled
- Machine help is a default expectation
- On-device is now the natural framing
What it legitimized
Here is the shift that matters most for people like me. Apple didn't just ship a feature, it legitimized an idea. The idea that your computer should help you write, that finishing your sentence is a normal thing for a Mac to do, that this isn't a gimmick but a baseline. A billion people have now used a phone that predicts their words. After macOS 26, a Mac does it properly, on-device, and the question "why would I want my computer to finish my sentences" stopped being a question anyone needs to ask.
That legitimization is why I said, in the Apple Intelligence post, that Apple's entry helped tools like mine. It sounds backwards, a platform giant shipping the thing I sell, and it helping me. But the category was tiny before, and Apple made it normal. The people who hit Apple's walls, the coverage limits I wrote about in the built-in predictions post, then go looking for the version that works everywhere, and that's the version I build.
Where it leaves the field
Here is the honest landscape after the shift. Apple owns the free, bundled, on-device layer, and it's good in Apple's lane. The cloud assistants own the big-model, do-anything layer, and they're good in their lane. And the system-wide autocomplete tools own the layer in between, the one that's not tied to Apple's apps and not tied to a server, the one that follows you into every text field with one key.
The three layers overlap, and the overlap is where the honest competition lives. Apple's layer is free, which is powerful. The cloud layer is powerful, which is free-ish. The system-wide layer is neither free nor the biggest, and its argument is specific: it's the only one that gives you the same habit in every app, on your Mac, with your voice, for a one-time price. I wrote about the category map before Apple's engine shipped, and the map has three layers now instead of two.
What it means for you
If you type for a living, here's what macOS 26 actually changed for you. You now have a free on-device option in Apple's apps, and you should use it, because free and private is a hard combination to beat. And you now have a reason to expect the same help everywhere you type, because the moment you've felt it in one app, the absence of it in the others is a gap you notice. That gap is the opportunity, and it's the reason the system-wide layer exists.
Apple's engine made on-device writing normal, and I'm grateful for that. It also made the coverage gap visible, the places where the help stops. A tool that follows you into every field is the answer to the gap Apple's own engine created by being good in some places and absent in others.
The close
macOS 26 changed the rules for people who type, and the change is still settling. It made machine-assisted writing a default instead of an install, it legitimized the whole idea, and it drew a line between the free bundled help in Apple's apps and the help that follows you everywhere. That line is where I build, and I think it's where the category is heading.
The trial is free for 30 days if you want to see the system-wide layer, the one that works in every app, on your Mac, in your voice. The engines post and the Apple trade post have the details on how it fits alongside Apple's engine, including the part where it can use Apple's engine too. The platform changed, the layers settled, and the honest choice is clearer than it has ever been: use the free layer where it covers you, and add the layer that covers everything.
Sources
- Apple Intelligence: what macOS 26 put on every supported Mac
- Apple Foundation Models: the on-device writing engine documentation
On macOS 26+ Macs, Apple Intelligence mode stays free even after the trial ends — you always keep a working path to suggestions.
Written by Amit Ashwini, who builds WriteAmp and runs its marketing. More: why the Tab key beats the chat box · mini, midi, and max compared · benchmark methodology.