Openclaw

Robotic claw extending from a laptop screen flinging a paper-airplane text message toward three small house silhouettes across colored permission zones

OpenClaw Texted My Ex and Why iMessage Access Is a Trap

The viral r/ChatGPT “my OpenClaw texted my ex” post reads like a joke, but the comments treat it as a warning sign. Keep OpenClaw’s iMessage, SMS, and contacts skills off your personal Mac. Wait until LTS ships and the founder’s “rough week” supply-chain fixes land. Scope write-access skills to a disposable VPS instead.

Key Takeaways

The viral “texted my ex” post is a leading indicator, not just a meme.
iMessage, SMS, and contacts are write-heavy skills that touch your real social graph.
Forgetful agents plus unsupervised cron jobs turn wrong-recipient sends into expected behavior.
Run write-heavy OpenClaw skills on a disposable VPS, not your personal Mac.
Wait for the LTS release before treating OpenClaw as personal-machine infrastructure.

The viral OpenClaw meme is not just a meme

A screenshot of OpenClaw happily reporting that it had texted the OP’s ex hit 4.8K upvotes and 176 comments on r/ChatGPT in about three weeks. The top replies are jokes (“Of all the things that didn’t happen, this happened the didn’test”). The serious comments point at a real safety category that is forming in real time.

Brass alchemist scales weighing a heavy pile of gold coins with a red 1500 price tag against a small pyramid of bronze coins and a teal dragon-circuit gem, with five colored arrows pointing to isometric server towers

Ditching Claude Opus for GLM 5.1 in OpenClaw at $18/Mo

Anthropic’s third-party tool rules priced agent users off Claude Opus 4.7. The cheapest working OpenClaw stack now is Z.ai’s $18/mo GLM 5 Turbo plan. Next rungs: Ollama-cloud’s $20/mo GLM 5.1, then MiniMax’s $40/mo highspeed tier. Kimi 2.6 stays API-only since local setup needs about 750 GB of RAM.

Key Takeaways

Z.ai’s $18/mo plan running GLM 5 Turbo is the cheapest OpenClaw backend that actually works.
MiniMax highspeed at $40/mo handles heavier workloads without the four-figure surprise bills.
Kimi 2.6 needs around 750 GB of RAM to self-host, so almost everyone runs it through the API.
Keep Claude on the planner role; route scheduled jobs to the cheap backends.
China-hosted models trade dollars for privacy on iMessage, contacts, and email skills.

Why $1,500/mo Opus Bills Pushed Users to GLM

The pressure here is simple. Once Anthropic’s third-party tool rules kicked in, OpenClaw users on the Claude Pro CLI got nudged onto pay-per-token API access. At Opus 4.7 list pricing of $15 per million input tokens and $75 per million output tokens, agent loops add up fast. The OP of the r/openclaw PSA thread tracked his own bill at about $1,500/mo before he switched. That figure is the anchor most cost threads on the sub now cite. The pricing pain did not ease with the next model either: the community reception of Opus 4.7 leaned on token-burn complaints from power users hitting caps in minutes, which is exactly the pattern that turns an OpenClaw cron fleet into a four-figure surprise.

Allegorical illustration of a translucent brain memory vault with a chaotic multi-armed robot dropping speech bubbles on the left and a calm robot carrying a memory shard on the right

OpenClaw vs Hermes and Why Memory Kills Agent Loyalty

Hermes Agent , built by Nous Research, has taken about 30% of OpenClaw’s user base by fixing one failure: memory. The Kilo.ai synthesis of 1,300+ r/openclaw comments confirms the figure. OpenClaw still wins on multi-agent breadth and 100+ skills. The right answer depends on which failure mode hurts you more.

Key Takeaways

About 30% of r/openclaw users have switched to Hermes Agent, mainly for memory reliability.
Memory failures, not features, are the top reason people leave OpenClaw.
Hermes ships with memory that works by default; OpenClaw needs heavy prompt-engineering to behave.
OpenClaw still wins for multi-bot setups across Telegram, Slack, and Discord.
A growing minority skip both and use OpenAI Codex business-tier instead.

Why r/openclaw Is Migrating to Hermes

The most-cited migration thread on the subreddit is the 167-comment OpenClaw vs Hermes thread . The top-voted answer to “is Hermes worth a look” reads as a clean defection notice. The poster ran OpenClaw for weeks on the same workload, then switched in an afternoon:

Editorial infographic of an engineer at a control panel splitting glowing data flow between a sealed OAuth gate and an open brass pipe feeding a glowing terminal monolith

OpenClaw on Your $20 Claude Sub After Anthropic Banned It

OpenClaw’s bundled claude-cli backend is officially sanctioned by Anthropic. OAuth-token extraction tools stay blocked. The carve-out works because shelling out to claude -p preserves prompt caching, so a $20 Pro or $200 Max sub routes through OpenClaw without four-figure API bills. The catch used to be a 5-hour usage cap. From June 15, 2026, that claude -p traffic moves onto a separate monthly Agent SDK credit, so the real limit is now a modest dollar budget.

Towering brass clockwork robot on a cracked pedestal leaking forgotten paper notes from its memory chamber while handing down a tidy morning news briefing

1,000 OpenClaw Deploys Later

After publishing a 7-minute OpenClaw deploy video and watching roughly 1,000 isolated VMs spin up afterward, one r/LocalLLaMA cloud-infra operator concluded the only OpenClaw workflow that survives unsupervised execution is a daily news digest. Memory is the load-bearing failure mode, not a fixable bug. OpenClaw sits at 370K+ GitHub stars, but the working-workflow count has barely moved.

Key Takeaways

A cloud-infra operator watched roughly 1,000 OpenClaw deploys and found one reliable use case.
Memory unreliability is built into how the agent works, not a bug a patch can fix.
Daily news digests are the exception because they keep no state between runs.
The same digest can be built with a cron job and any LLM API in about ten lines.
OpenClaw’s founder admitted that recent releases were a “rough week”.

The 1,000-Deploy Post That Broke the Consensus

The contrarian thesis is anchored to one specific source: an r/LocalLLaMA post titled “OpenClaw has 250K GitHub stars. The only reliable use case I’ve found is daily news digests” , with 335 comments and 891 votes. The OP is not a casual skeptic. He runs cloud infrastructure where strangers spin up Linux VMs, published a deploy walkthrough that took off, and now has a dataset most reviewers do not have access to.

Self-Driving Business: Integrating OpenClaw with Google Workspace CLI

By combining OpenClaw (an open-source autonomous AI agent) with Google’s Workspace CLI and the Model Context Protocol, you can build a self-driving business layer that monitors Gmail, manages Google Drive, and updates Calendar - all without manual intervention. The setup requires configuring OAuth credentials in Google Cloud Console, installing the GWS CLI via npm, and exposing the Workspace tools to OpenClaw via an MCP server - giving your AI agent structured, programmatic access to the entire Google productivity stack.