I just wrote this post on my blog i think people should read. https://www.olibuijr.com/blog/openclaw-is-just-ssh-with-extra-steps OpenClaw Is Just SSH With Extra Steps Jensen Huang called it “probably the single most important release of software… probably ever.” Sam Altman hired its creator. It hit 250,000 GitHub stars in under four months. VentureBeat, TechCrunch, and every AI newsletter on the planet ran breathless coverage of the revolution. The revolution? You can now message your AI agent on Telegram. Let that sink in. The “most important software release ever” is a chat interface to a computer you already own. What OpenClaw Actually Does Strip away the hype and OpenClaw does something genuinely simple: it runs an LLM on your machine and connects it to messaging platforms. You send a Telegram message, the agent reads and writes files, runs shell commands, and sends back the result. That’s it. That’s the revolution. To be fair, it does this across a staggering number of platforms — WhatsApp, Telegram, Slack, Discord, Signal, iMessage, IRC, Teams, Matrix, LINE, Mattermost. The integration work is real. The UX is polished. The onboarding is smooth. But the core capability? Remotely controlling a computer through text messages? We’ve had that since 1995. It’s called SSH. The Setup That Already Existed Harper Reed — one of the sharpest engineering minds in the industry — wrote about his remote Claude Code setup in January 2026. His stack: Tailscale for networking mosh for resilient connections tmux for session persistence Blink SSH on his iPhone His philosophy? “I want to just SSH into shit.” Roger Gonzalez took it a step further. He built a three-layer setup — mosh, tmux, and ntfy for push notifications — that lets him code from the beach on his phone. When Claude needs input, ntfy sends a push notification. The entire architecture is composable Unix tools. No messaging platform needed. No 250,000-star GitHub repo. These aren’t workarounds. These aren’t hacks. This is the way Unix systems have worked for thirty years. tmux sessions survive disconnections. mosh handles flaky mobile connections. SSH keys handle authentication. It’s boring, battle-tested, and it works. The Dropbox Argument Now, there’s a counterargument, and it’s a good one. On Hacker News, someone compared OpenClaw skeptics to the infamous 2007 comment about Dropbox: “You can already build this with an FTP server and shell scripts.” That commenter was technically correct and completely wrong. Dropbox succeeded because it made file syncing work for everyone, not just people who could configure rsync. The same logic applies here. SSH is powerful but it requires meaningful technical knowledge. Your project manager can’t SSH into your dev box and ask Claude to generate a status report. With OpenClaw, they can send a Telegram message. Fair point. But here’s where the comparison breaks down. Dropbox solved a problem that billions of people had — file access across devices. OpenClaw solves a problem that a much smaller group has — remotely controlling an AI coding agent. And within that group, the people who actually need an AI coding agent overwhelmingly already know how to use SSH . The audience that can’t SSH but needs an autonomous AI agent is vanishingly small. The $600 Paperweight But the hype machine wasn’t satisfied with just software. It needed hardware. In the months after OpenClaw went viral, something absurd happened: people started panic-buying Mac Minis. Apple Stores in Berlin, San Francisco, and Tokyo ran out of stock. Online shipping dates slipped from days to months. Developers were buying stacks of three, five, sometimes twelve units . Apple had to announce expanded manufacturing in Houston just to keep up with demand. The pitch was seductive: run your AI locally. No subscriptions. No cloud dependency. Your own private AI agent humming away in a $599 aluminum box on your desk. There’s just one problem. The AI running on that box is terrible. A 32GB Mac Mini can comfortably run models up to about 14 billion parameters. The best of these — Devstral-24B, Qwen3-Coder-30B — score roughly 47% on SWE-bench Verified , a standard benchmark for real-world coding ability. Claude Opus 4.6 scores 80.8% . Gemini 3.1 Pro hits 80.6% . That’s not a gap. That’s a different sport. Put differently: your $599 Mac Mini gives you AI that performs at the level of cloud models from 2024 . You are paying for hardware to run technology that is 12 to 18 months behind what you can access for $20 a month with a Claude Pro subscription. And here’s the part that would be funny if it wasn’t sad: most people who bought Mac Minis for OpenClaw aren’t even running local models. OpenClaw primarily functions as middleware that makes API calls to cloud services. The Mac Mini is sending HTTPS requests to Claude or GPT and relaying the responses to your Telegram. A task — as one reviewer put it — that a Raspberry Pi could do . Peter Steinberger, OpenClaw’s own creator, tried to warn people: “Please don’t buy a Mac Mini. You can deploy this on Amazon’s Free Tier.” Nobody listened. The 2026 Mac Mini gold rush will be studied in business schools as a case study in hype-driven purchasing. Thousands of developers spent $600 to $2,200 on depreciating hardware to run models that produce results their $20 cloud subscription already handles — better, faster, and with automatic upgrades to every new frontier model the moment it drops. The Parts That Are Actually New (and Concerning) OpenClaw does have one genuinely novel feature: the “heartbeat.” Unlike SSH, which is reactive — you connect, you type, you get output — OpenClaw agents can initiate actions autonomously. They can complete tasks overnight, schedule follow-ups, and notify you when something needs attention. This is a real capability difference. And it should terrify you. Gartner analysts called OpenClaw’s security design “insecure by default” with “unacceptable” security risks. Boxmining’s hands-on review found a 2-5% failure rate on tasks — wrong dates, hallucinated details — and reported an incident where OpenClaw randomly messaged someone . An autonomous agent with access to your file system, your shell, your APIs, and your messaging contacts, running unsupervised? That’s not a feature. That’s a threat model. The Hype Machine’s Playbook Here’s what actually happened with OpenClaw: Someone built a polished wrapper around capabilities that already existed They connected it to platforms where non-technical people could see it Jensen Huang said something hyperbolic The media ran with it 250,000 GitHub stars materialized from people who had never heard of tmux Those same people bought Mac Minis they didn’t need to run models that aren’t good enough This is a pattern we’ve seen before. It happened with blockchain (distributed databases existed). It happened with “serverless” (we just moved whose server it was). It happened with “no-code” (it was always just higher-level code). And now it’s happening with AI agent communication — except this time, the hype also sold hardware. What Developers Should Actually Do If you’re a developer who wants to control Claude Code, Cursor, or any AI coding agent from your phone, here’s the unsexy truth: Install mosh and tmux on your dev machine Set up Tailscale for zero-config VPN access Get Blink (iOS) or Termux (Android) on your phone Add ntfy if you want push notifications SSH in. Attach to your tmux session. Done. Total cost: $0. Setup time: 20 minutes. No Mac Mini required. No messaging platform middleware. No VC-funded startup that might pivot, get acqui-hired, or change their terms of service. And for the love of everything, if you’re going to use an AI agent, use a frontier model. Claude Opus 4.6 and Gemini 3.1 Pro exist. They score 80%+ on real-world coding tasks. Your Mac Mini’s 14B local model isn’t even in the same conversation. Or install OpenClaw. Message your AI on Telegram. Buy a Mac Mini. Just know that what you’re doing isn’t a revolution — it’s SSH with a nicer font and a receipt from the Apple Store. submitted by /u/Olibuijr
Originally posted by u/Olibuijr on r/ArtificialInteligence
