A free tool called OpenClaw reached 3.2 million users in weeks. It let anyone send a message on WhatsApp, go to sleep, and wake up to find an errand done — meeting booked, email drafted, something purchased. It spread that fast because it solved a real thing: the friction between wanting something done and having to do it yourself. Then it hit a ceiling. It required technical setup that broke for anyone who couldn’t navigate a command line. The gap between what it promised and who it could actually serve was enormous.
That gap is exactly what Google and Meta are now racing to close. Google’s new agent, internally named Remy, runs inside Gemini and connects to the full suite — search, email, calendar — designed to run continuously in the background, learning your patterns, anticipating needs without being prompted every time. Meta’s version, Hatch, went further in a different direction: before deployment, it trained in practice environments navigating real consumer apps — DoorDash, Etsy, Reddit — learning to move through the internet the way a person would. Meta also announced a shopping layer for Instagram that lets a user tap a product in a video and complete the purchase without leaving the app.
The conventional read is that this is a feature war. But that’s too small a frame.
The Interface Is the Moat, Until It Isn’t
What these companies are really doing is making a bet that the next durable moat isn’t the software — it’s the relationship. The agent that knows your calendar, your shopping history, your habits, the cadence of your week — that agent becomes hard to replace not because it’s technically superior, but because it’s contextually irreplaceable. Data as lock-in is not a new idea. But the personal AI agent turns that dynamic ambient. Passive accumulation of trust.
This is also what Dario Amodei was gesturing at when he told a financial services audience that SaaS companies are going to need new moats. The old one — complexity of building software — is dissolving. Writing code is getting cheaper fast, and that means any SaaS business whose pricing assumed that building was hard is now pricing against a cost curve that’s moving against them. Amodei was blunt: “I think individual SaaS companies, it’s very possible for them to lose market value, go bankrupt, completely go bust.” But he was also precise — it depends on the response. The companies that see clearly what they have and pivot toward it will do fine. The ones that don’t pay attention will be blindsided. He didn’t say which was which. He didn’t need to.
The thing worth noticing is the quiet admission embedded in that framing: Anthropic is not just a model company anymore. When your CEO is giving a livestreamed event called “The Briefing: Financial Services” and predicting which industry categories survive the disruption your own technology is creating, you are now something more like infrastructure. You are the river, commenting on which banks will flood.
The Body Enters the Room
Meanwhile, in Beijing, something else entirely was happening that didn’t make the same headlines — but should probably be read alongside them.
Auto China 2026 was nominally a car show. It became something else. XPeng brought a humanoid robot called Iron, running on the same underlying AI stack as its driver assistance system. The same model that reads road conditions can, in principle, navigate a room, pick up an object, interact with a person. Xiaomi is already running humanoid robots on its factory floor — repetitive fastening work, 90% success rate over hours of autonomous operation in live production conditions. Chery priced its humanoid at around $40,000 and is selling it through dealership networks. Selling through dealership networks.
The framing from the AI software conversation and the framing from the robotics conversation are usually kept separate. They shouldn’t be. The personal agent that manages your calendar and the robot that assembles your car are downstream of the same architectural decision: build a general intelligence layer, then let it inhabit different physical and digital containers. That’s what XPeng demonstrated when it showed that one model powers both the car and the robot. The container changes; the intelligence is the same substrate.
The Erlang-to-Java migration story buried in a book about AI-assisted coding makes this tangible in a different register. A large enterprise is considering abandoning a language famous for resilience because AI coding tools perform significantly better in Java — simply because the training data volume is larger. The architecture of what’s already legible to machines is now influencing what gets built going forward. It is not neutral. The world is reorganizing itself around what the model already knows.
The Real Question
So here’s the thing underneath all three stories. We keep treating this moment as a tools upgrade — better software, faster robots, smarter assistants. But what’s actually changing is the location of intelligence. It is moving out of dedicated applications and into ambient layers. It is moving out of screens and into physical environments. It is moving out of one-at-a-time prompts and into continuous background processes.
The to-do list that Google wants to own isn’t a list anymore. It’s a relationship. The robot on the factory floor isn’t a machine anymore. It’s a student who improves while it works. And the SaaS moat that Amodei is eulogizing wasn’t really about software — it was about the cost of solving problems. That cost is dropping. The companies that understood their value as problem-solving reach are positioned for what comes next. The ones that thought their value was the software itself are going to have a hard time explaining what’s left.
The interface disappearing is not the end of something. It is the beginning of accountability for what the product actually was.
Leave a Reply