The Unbearable Burden of Being Right
I tried to use the most advanced AI capability of 2026 on the most advanced device I own, and got told to go use my laptop.
Perplexity announced \"Computer Use\" this week, joining Anthropic, OpenClaw, Standard Intelligence, and others in a race to build AI agents that can operate your computer on your behalf. Not just answer questions or generate text, but actually click buttons, fill out forms, navigate between applications, move files around. The kind of thing that turns AI from a conversational partner into a coworker who can take things off your plate.
So naturally I pulled it up on my phone. And there it was, floating over a meadow rendered in the style of a screensaver from 2004: \"Coming to mobile soon. Currently only available on desktop.\"
I laughed. Then I thought about it for a while.
Coming Soon
AI already does useful things on your phone. It transcribes your meetings, summarizes your emails, generates images, answers questions. What it cannot do is act autonomously across applications on your behalf. It cannot see your screen, decide what to click, open a different app, pull information from one place and put it in another. That kind of cross-application agency is what computer use is, and it is the capability that only works on the desktop.
The phone is the computer that won. It is the device that most people on earth use for most of their computing, most of the time. It is the thing the entire technology industry spent the last fifteen years optimizing for, building around, designing toward. And it is now, by architecture and by intention, the device least prepared for autonomous AI.
This is not a failure. That is what makes it interesting.
The reason computer use agents work on the desktop and not on your phone is the sandbox. Mobile operating systems were designed from the ground up to keep applications isolated from each other. Each app lives in its own container, unable to see what other apps are doing, unable to reach into the file system or manipulate another application's interface. This is why your phone does not get viruses the way your laptop does, why a rogue app cannot reach into your banking app, and why billions of people trust a pocket-sized device with their entire lives.
These were engineering and product choices that created security and trust at a scale no computing platform had achieved before. And they are the reason that autonomous AI agents cannot operate where most computing actually happens.
On a desktop, an AI agent can see the screen, interpret what is there, decide what to click, and execute that action across whatever application is relevant. This is possible because the operating system was never designed to prevent it. Desktop operating systems grew up in an era where interoperability between applications was a feature, not a threat. The boundaries are porous. The file system is shared. One application can, for better and worse, reach into the world of another.
Mobile took the opposite lesson from the same history. The chaos and insecurity of the desktop era was the problem that mobile set out to solve. And it solved it. Completely.
So here we are. The platform that is least secure, least controlled, and least modern is the one where the future works. The platform that represents a decade of disciplined, correct, compounding decisions is the one showing you a landing page that says \"coming soon.\"
Mechanisms
This is not just a technology story. It is a structural pattern, and once you see it, you find it everywhere.
Here is the mechanism. Every good decision, if it works, gets built upon. The next decision assumes the first one will persist. The decision after that assumes both will. Over time, what began as a series of individual choices becomes architecture. And architecture has a property that individual decisions do not: it becomes load-bearing. The sandbox was a design choice. Then it became an API surface that developers built against. Then a revenue model that depends on the app store as the single point of entry. Each layer was added because the previous layer was sound. Each layer made the previous layer harder to revisit.
This is how local optimization creates global inflexibility. Each decision, viewed on its own, solves the problem in front of it and makes the immediate system better. The accumulation of those decisions, each one correct, produces a global architecture that is optimized for a context that may no longer apply. The system is not broken. It is locally optimal everywhere and globally stuck.
The economics make this worse. The sandbox is not just a security architecture. It is an economic architecture. App stores generates revenue. The permission model creates liability protection. When you ask why a phone maker does not simply open the sandbox for AI agents, part of the answer is security, but part of the answer is that every opened boundary is a revenue surface that becomes contestable and a liability perimeter that becomes ambiguous. The same is true inside any organization. Governance is never just about quality. It is about who approves, who bears risk, and who is exposed when something goes wrong. Incentives and architecture become mutually reinforcing, and the combination is what gives the structure its weight.
Once enough people and systems and economics depend on a structure, it develops its own center of mass. The engineers who built it have careers invested in maintaining it. The developers who designed around its constraints have codebases that assume it. The finance teams who model revenue have projections that depend on it. None of these people are being obstructionist. They are being rational. The structure rewards them for preserving it and penalizes them for questioning it. And by the time the external context shifts enough that the architecture needs to evolve, the internal context has organized itself entirely around the architecture as it stands.
This is the trap. Not incompetence, not resistance to innovation, not a failure of vision. The trap is that good decisions, made well and built upon faithfully, become the geology of an organization. Governance accumulates like sediment, each layer deposited by a rational process, and over time the strata harden into something that no strategy memo can reorganize.
And there is a timing problem that makes this particular moment especially difficult. Institutions compound safety over decades. AI compounds capability in months. The structures that organizations built to manage risk were designed for a world where the external environment moved at roughly the same pace as the internal one. That assumption no longer holds, and the mismatch is what makes the burden feel unbearable. The architecture is not just in the way. It is holding up the roof while the ground underneath it shifts. And that is why people are so reluctant to touch it. Not because they are lazy or unimaginative, but because they rightly fear what happens if the thing they depend on collapses while they are still inside it.
Geology
I have spent the last eighteen months focused on an AI transformation inside a large organization. The kind of place that has built processes and governance structures and risk frameworks over decades, each one in response to a real need, each one making the organization more resilient, more consistent, more trustworthy. Clients trust the organization in part because those systems exist. And every day you feel the weight of systems that are doing exactly what they were designed to do, at a pace that was set long before the world started moving this fast. You cannot fix something that is not broken. You can only recognize that the context around it has changed enough that what it produces is no longer what you need.
The instinct when you recognize this pattern is to argue that the old decisions were wrong. That the sandbox was a mistake, that the governance was too heavy, that the risk framework was too conservative. This is tempting because it gives you something to blame and something to dismantle. It is also wrong, and the people who built those systems know it is wrong, which is why they resist when you try it.
The harder and more honest path is to hold two things at once. The decisions were right. And they are now in the way. The tension between them is not something you can resolve by picking a side. It is something to lead through, together. And leading through it looks less like conviction and more like humility. It means telling the people who built the current system that they were right, and meaning it, while also making clear that being right then does not settle the question of what is right now. It also means accepting that the things you are building today will one day be someone else's geology. The new platforms, the new frameworks, the new ways of working — they will accumulate and harden and eventually resist whatever comes after them. This is not a problem you solve once. It is a condition you learn to operate inside.
So what do you do?
Two Speeds
You do not tear down the architecture. And you do not pretend it is not there. What I have seen work, in the technology version and the organizational version of this problem, is building parallel structures that operate under different rules while the existing architecture continues to do what it does.
The phone makers will not remove the sandbox. What they will likely do is create a controlled layer within it where agents can operate with explicit permissions, a space where cross-application access is possible without dismantling the security model that everything else depends on. An agent zone inside the compliance perimeter. The sandbox stays. The new capability gets a surface to run on. Both coexist, governed differently.
The same principle applies inside organizations. You do not replace the governance structure that took decades to build. You create a parallel track where AI-native work can move at its own speed, with its own risk model, inside boundaries that are defined clearly enough that the existing structure does not feel threatened. Two speeds, running side by side, with clear rules about what crosses between them. Over time, the boundary shifts as confidence builds and evidence accumulates.
This is not easy. Parallel structures create their own tensions. People in the existing structure feel bypassed. People in the new structure feel constrained. The leadership work is not in designing the parallel system. It is in maintaining the legitimacy of both long enough for them to converge, which they eventually do, but only if neither side has been delegitimized along the way.
The screenshot on my phone this week was a small thing. A landing page for a feature that will probably work on mobile within a few months. But I keep coming back to it because it captures something that I think matters about this moment.
The future does not get blocked by your mistakes. It gets blocked by your achievements.