It Will Never Be the Year of the Linux Desktop · unix.foo
AUTO
LIGHT
DARK
SECTION<br>POSTS
FILED<br>2026-05-27
WORDS<br>1826
READ<br>9 MIN
Every year someone says that this is the year of the Linux desktop.
It is never the year of the Linux desktop.
There are many reasons for this. Drivers. Games. Adobe. Microsoft Office. Battery life. The thing where you close the lid of a laptop and open it again later to find that it passed into the good night. These explanations are all correct in the small and unsatisfying in the large. They explain why a person did not switch to Linux last Thursday. They do not explain why the desktop, as an institution, will continue to belong to Apple and Microsoft.
And now there is a new and more depressing explanation.
The future computer user is not a person.
Or at least not only a person. The robots are coming for the desktop. The interesting part is that the ramps were already there.
They were called accessibility APIs.
If you use a Mac and open the Accessibility Inspector tool that’s built into the system (you really should try it), you can see a second version of the computer, hiding inside the first one. The first version is the one you look at: windows, shadows, rounded rectangles, a little bouncing icon in the Dock from Slack announcing that you are falling behind.
The second version is a tree. A literal hierarchy of objects. Window. Group. Button. Text field. Scroll area. Static text. Each object has properties. Some have values. Some have actions. Some will tell you where they are. Some will tell you what they contain. Some will let you press them without moving the mouse at all.
This is not how computers were initially designed to be used, if by “used” you mean “used by sighted people moving a pointer around.” It is how computers had to be exposed to people who could not rely on pixels. VoiceOver needed it. Switch control needed it. Dictation systems needed it. The operating system had to learn to describe itself.
And now the agents need it too.
You can see this most clearly in OpenAI’s Codex Computer Use<br>feature, which on macOS doesn’t just take a screenshot. It also pulls “available text” out of the frontmost window including text the app makes available outside the visible scroll area, which is to say, content that is technically not on the screen at all. It also allows the agent to interact with your entire Mac without interrupting your usage as it has its own independent mouse that can work in the background.
OpenAI bought the company that built this in October 2025: a twelve-person shop called Software Applications Incorporated, whose product, Sky, had never been publicly released. Sam Altman had personally invested in the seed round. The founders had previously sold Workflow to Apple, where it became Shortcuts. What OpenAI got for an undisclosed but evidently real amount of money was the team’s bet about the right way for an AI model to drive a Mac. The bet appears to have been correct. The binary that runs this inside Codex today is still named SkyComputerUseClient.
This is the part where you might expect me to say that the reason macOS is suddenly so good for agents is the accessibility API. But that’s not really the full story. Windows has accessibility APIs. Linux has accessibility APIs. APIs are easy to have. You write them down in a header file, give a conference talk about them, and then spend the next twenty years explaining why nobody used them correctly.
The reason macOS is so far ahead is because of defaults.
Apple did not, when most of this was being soldered into place in the late 1990s, anticipate that a stochastic parrot with an $800+ billion valuation would one day need to change a setting in Finder. Apple just decided that if you build a normal Mac app out of normal Mac controls with things like NSButton, NSTextField, WKWebView, the boring stock pieces then your app should be accessible by default. The developer didn’t have to do anything. They wrote a regular app and got a high-fidelity accessibility tree for free, because Apple put the cost of compliance into the SDK instead of the application. The blind user got the tree. The accidental beneficiary, all these years later, is Codex.
This is one of those situations where a moral concern turns out, in retrospect, to have also been infrastructure.
For most of software history, accessibility was treated by most engineering teams as either a compliance chore, an act of kindness, or a thing you would get to at the end if there was time, which there never was, because the only features that were ever truly protected were the ones that affected someone’s bonus.
This was always wrong! But it is now wrong in a way that rich people can understand. A bad accessibility tree no longer excludes only disabled users. It also excludes agents. Accessibility is, by accident, becoming agent compatibility.
Agents are now new customers. History is not sentimental...