 |
VOOZH | about |
|
VOOZH | about |
We’re so glad you’re here. You can expect all the best TNS content to arrive Monday through Friday to keep you on top of the news and at the top of your game.
Check your inbox for a confirmation email where you can adjust your preferences and even join additional groups.
Follow TNS on your favorite social media networks.
Become a TNS follower on LinkedIn.
Check out the latest featured and trending stories while you wait for your first TNS newsletter.
OpenClaw made the always-on agent feel personal by making it live somewhere you could point at — a Mac mini on a shelf, drawing seven watts, running while you sleep. Peter Steinberger’s open-source project surpassed 300,000 GitHub stars by April and became one of the fastest-growing repositories on GitHub. The whole appeal was ownership: your hardware, your credentials, your lobster.
On Tuesday at I/O, Google launched Gemini Spark, and it makes the opposite bet. Spark is a 24/7 personal agent built on Gemini 3.5 Flash and connected to Google’s Antigravity agent stack. It runs in the background on virtual machines on Google Cloud. You never see the machine. Google plans to let you text and email the agent directly, so it works while your laptop is shut.
Strip away the branding, and Spark and OpenClaw do roughly the same job. Watch an inbox, draft the status update, browse the web, run the recurring task. Both are converging on MCP for tool connectivity, though the implementations differ in maturity. Both promise the assistant who does things rather than answers questions.
The substrate decides who holds your context, who sees your credentials, and who can change the terms later.
The difference is the substrate. OpenClaw runs on the metal you bought. Spark runs on metal Google rents to you and never names. That sounds like a deployment detail. It is actually the whole argument. The substrate decides who holds your context, who sees your credentials, and who can change the terms later.
The self-hosted version asks for real work. Buy the Mac mini, keep it awake, install a daemon, set up Tailscale, and rotate the key when it expires. The reward is control. Your credentials and workflows can stay under your own hand, depending on how you wire up models and integrations. That control is not the same as safety. A misconfigured local agent with shell, browser, and inbox access is its own hazard, and Chinese regulators have already flagged exactly that risk with OpenClaw.
Spark asks for nothing. It is already inside Gmail, Docs, and Sheets, with no manual wiring, because Google owns both ends. That out-of-the-box reach is the structural advantage no third-party agent can copy. The history here is fairly settled. Dropbox beat the home NAS. Gmail beat the mail server. Managed nearly always beats self-hosted for the median user, because most people will trade control for not having to think about it.
OpenClaw is not losing. It is being sorted into the smaller, stickier half.
So the personal-agent layer splits in two. A hosted tier where Google, and soon OpenAI, own the runtime and the context. A self-hosted tier for developers who want the credentials on their own hardware and will pay for the setup time. OpenClaw is not losing. It is being sorted into the smaller, stickier half.
This is where I would slow down before calling the race. Cloud storage won because the thing you handed over was inert. Files sat in a Dropbox folder, and nobody read them. A personal agent is of a different kind. To be useful, Spark needs broad standing access to your Gmail, Docs, Sheets, calendar, and live inbox. It does not just store your context. It reads it to act on it.
That changes the deal. Handing Google a folder of files is not the same as handing Google a system that processes your job, your relationships, and your calendar well enough to send mail on your behalf. The honest version of the worry is not that Google keeps your data. It is the unsettled gap between access, retention, and what trains the next model.
The self-hosted camp is small today, but that’s not because of nostalgia for running your own server. It is the instinct that an agent this intimate should answer to you, on hardware you can unplug. That instinct does not scale to everyone. It does not have to. It only has to hold the developers and the privacy-sensitive, and that is a durable floor.
The question for developers is not which agent is better. It is whether you are comfortable with Google holding the keys to the one that runs your life.
