OpenClaw vs Hermes: the always-on personal-agent debate

An always-on personal agent is a program that runs all day on your own machine, talks to you through the chat apps you already use (WhatsApp, Telegram, Slack, Discord), and keeps acting between your messages: watching inboxes, running scheduled jobs, remembering what you told it last month. OpenClaw and Hermes are the two big open-source ways to run one, and two of the most-starred projects on this entire list. The choice matters because it sets three things at once: your security posture (this thing has your accounts), your maintenance load, and, since June 2026, your monthly AI bill. The flame war treats them as rivals; the architecture says they are opposite design philosophies that happen to share a category.

Stars as captured for the main list. Both are rated headless (designed to run unattended) and resumable (a dead run can pick back up); the guide to rankings defines this vocabulary.

What the field reports actually say

Primary-source notes from the debate threads (r/openclaw, r/hermesagent, r/AskClaw, r/AI_Agents; links inline), claims attributed as claims:

• The migration driver is update churn, not features. The recurring OpenClaw complaint isn't capability; it's that frequent releases break working setups ("the last 5 updates in a row", broken Telegram sessions, flaky scheduled jobs; experience report). Hermes converts say they are "in the repair shop one-eighth of the time." The confounder, named by an OpenClaw user: Hermes has shipped a fraction of OpenClaw's release count (24 vs 100+ as of August 2026), so it has had less time to accumulate breakage; its stability record is partly an artifact of age (thread). Counter-reports exist in both directions ("I went to Hermes and it was a nightmare… back with OpenClaw").
• The learning loop is real, and double-edged. A three-week side-by-side had Hermes turn a daily news-briefing task into a reusable skill plus a scheduled routine, unprompted. The dark side, from a detailed migration report: bad decisions get learned too, "etched in stone", and scraping a mislearned pattern out of skills, memory, and scheduled jobs "reminds me of scraping a virus infection out of your PC manually."
• Run-both is the power-user consensus, with a twist. OpenClaw as the coordinator, Hermes as the execution specialist. The most-cited benefit isn't throughput, it's redundancy: multiple independent reports of telling one agent to diagnose and fix the other when it bricks. Cost of running both: roughly +30%, for reportedly much more than +30% output.
• Trust the threads less than usual. Both camps accuse the other of astroturfing, and the "everyone is migrating" narrative is contested inside OpenClaw's own subreddit. Volume of sentiment is unusually weak evidence here; the mechanism-level reports above are what's load-bearing.

The billing scare (April to June 2026)

Some context if you're new to this: running an agent on "subscription auth" means logging it in with the flat-rate Claude subscription you already pay for, instead of a metered API key that bills per token. In 2026 that arrangement nearly changed, twice.

• Early April 2026: Anthropic banned third-party agents from running on Claude subscriptions (capacity issues; an estimated 135,000+ OpenClaw instances were on subscription auth), then reinstated them alongside an announced catch: a separate metered Agent SDK credit pool ($20 to $200 per month by plan, billed at API rates) that would end flat-rate always-on agents.
• June 15, 2026: Anthropic paused the credit-pool change the day it was due to take effect. As of August 2026, third-party and programmatic usage draws from normal subscription limits, and Anthropic says any revised plan will come with notice.

The episode is the lesson: an always-on agent's economics sit on policy that can move under you. What the ops threads add: the durable cost problem is usage shape, not harness choice.

• The trap is frontier models on background work. One thread's summary: running a top-tier model on heartbeats is "hiring a PhD physicist to check whether the fridge door is closed" every 15 minutes. One lightweight monitoring setup ran $0.50/hour, about $360/month before optimization.
• The fix that recurs across threads, in priority order (worked example, claimed ~80% reduction in an afternoon): (1) wake less: deterministic scripts and narrow watches that only invoke a model on a match (Hermes's wakeAgent and OpenClaw's model-bypassing message send both support this); (2) route by tier: cheap or free models for background work, a mid-tier model for conversations, never a frontier model on a timer; (3) slim the tool list: big tool registries silently tax every request. Field claims put monitoring setups under $5 to $10 per month after all three.
• The hedges people adopted during the scare, and mostly kept: open-weight models (run locally or via OpenRouter), and spreading load across other providers' plans. Both harnesses are provider-flexible; Hermes most natively, since open weights are Nous's founding thesis.

Our read

Forget the flame war's framing of better and worse. OpenClaw optimizes for presence; Hermes optimizes for discipline. Almost every observed difference (heartbeat vs isolated scheduled jobs, unbounded vs bounded memory, chat-everything vs CLI-first admin, relaxed vs restrictive security) falls out of that one fork in the design tree. Pick by which failure you'd rather live with: an exuberant agent you have to contain and patch weekly, or a careful one you have to coax and can't fully drive from your phone. If you genuinely can't choose, the coordinator-plus-specialist pattern is real, the two interoperate over ACP (a protocol that lets one agent hand work to another), and roughly +30% cost is a fair price for agents that can repair each other. Whatever you pick, your bill is determined by questions 3 to 5 of How to pick a harness, not by this page.

Part of best-of-Agent-Harnesses. New to this decision? Start with How to pick a harness. Spot an error or a stale claim? Open an issue.

Agents can query this page's data directly: claude mcp add agent-harnesses -- uvx agent-harnesses-mcp (MCP server).