Published: 2026-05-29

The Biggest Lies You've Been Told About Hermes Agent

Chapters / key moments (click to jump — plays here on the page)

Craig Hewitt runs two Hermes agents in production — one on a Mac mini, one in the cloud — and has worked through every tutorial and step-by-step repo on YouTube. In this video he debunks the six most persistent myths about Hermes Agent, gives an honest assessment of where it actually excels, and offers practical security advice most tutorials skip entirely.

Source video

"The Biggest Lie You've Been Told About Hermes Agent" by Craig HewittWatch on YouTube →

Key Takeaways

  • Myth 1: You need a Mac mini or VPS. Reality: your regular computer works fine to start — each hosting option has tradeoffs, none is required.
  • Myth 2: Hermes replaces Claude Cowork. Reality: Claude Cowork is the most productive AI tool for most people. Hermes fills the always-on, always-monitoring niche — they're complementary.
  • Myth 3: Build a multi-agent army. Reality: stick with one agent for at least 6 months before spinning up more. Master it first.
  • Myth 4: Memory drift is solved. Hermes handles memory better than OpenClaw, but its tendency to auto-create skills for everything creates skill bloat — use an agent guard to prevent this.
  • Myth 5: Your whole business runs on Hermes from day one. Reality: the first 80% of setup is easy; the next 80% (making it reliable, consistent, and customized) takes months of work.

The Honest Agent Stack

Hewitt's framing is refreshingly direct: "The most productive AI tool in the world right now for 95% of you is Claude Cowork." Hermes is excellent at specific things — always-on monitoring, proactive task execution while you're away, building long-term memory across many interactions. But it's not the right tool for focused development work or anything requiring you to be at the keyboard directing the agent. For that, Claude Cowork, Claude Code, and Codex are purpose-built.

The practical recommendation: use Hermes for proactive background work (always-on, always monitoring), and use Claude Cowork or Claude Code for anything where you're in the session doing directed work. Both can be running simultaneously and pass work to each other.

Critical Security Advice on Skills

Hewitt makes a point that rarely appears in other tutorials: don't install skills from third-party repos directly, because supply chain attacks against node packages are increasingly common. Instead, point your agent at the skill repo and say: "Look at what this does and make me a skill like it that fits my needs." Since skills are just markdown files, your agent can read and adapt them without downloading and executing arbitrary code. This one practice meaningfully reduces your attack surface.

On the auto-skill-creation issue: Hermes defaults to automatically creating new skills for repeated patterns. This creates bloat over time — overlapping skills that compete with each other and slow the agent down. Add an agent guard that prevents Hermes from creating new skills without explicit permission.

Related on OpenClawDatabase

← Back to News digest · See also: Hermes guide

Weekly Digest — In Your Inbox

Get the week's top AI agent news, updates, and guides — every Friday.