Hermes Agent Review: Why It Just Crossed 150K Stars

What is Hermes Agent?

Hermes Agent is an open-source AI agent built by Nous Research, designed to run anywhere, talk to you from any messaging platform, and improve itself over time. It crossed 154,000 GitHub stars on 2026-05-17, after roughly ten weeks since release (~March 2026) — making it the fastest-growing project in the OpenClaw ecosystem. MIT-licensed, runs on a $5 VPS or a GPU cluster, model-agnostic.

After using it on real research workflows for two weeks, this post explains why the star growth is justified — and the one trade-off you should know about.

Key Takeaways

• 154K stars in 10 weeks — fastest-growing OpenClaw-ecosystem project of 2026, crossed 150K on 2026-05-17 (added ~10K in the six days since 5/11)
• Multi-platform gateway: Telegram, Discord, Slack, WhatsApp, Signal, Email, CLI — from one process
• Self-improving skill loop: agent creates skills from experience, then improves them during use
• Model freedom: 200+ models via OpenRouter, plus Nous Portal, NVIDIA NIM, Xiaomi, GLM, Kimi, MiniMax, OpenAI, HuggingFace — hermes model switches them, zero lock-in
• Runs anywhere: 7 terminal backends (local, Docker, SSH, Singularity, Modal, Daytona, Vercel Sandbox). Serverless persistence on Modal / Daytona — costs almost nothing when idle
• Direct OpenClaw migration: hermes claw migrate ports your SOUL.md, memories, skills, command allowlist, API keys
• The honest downside: token usage is higher than minimalist agents — capability has a cost

Quick Facts

What makes Hermes Agent different?

Most "AI agent" projects are CLI tools. Hermes is structurally different — it's an agent harness that decouples four things that other tools weld together: where the agent runs, where you talk to it from, which model it uses, and what it remembers between sessions.

That decoupling is why people are starring it. You can run Hermes on a Modal serverless container, message it from Telegram while you're on the train, have it use Claude Sonnet for coding and Kimi K2 for cheap bulk work, and let it carry context across both — all configured by config file, not code changes.

If you've used Claude Code or OpenClaw, Hermes is best understood as "the same agent loop, freed from the laptop."

What does the multi-platform gateway actually do?

A single hermes gateway process makes the agent reachable from Telegram, Discord, Slack, WhatsApp, Signal, Email, and the CLI simultaneously, with cross-platform conversation continuity.

Concretely: I can ask a research question from Telegram on the bus, see the agent fire up a Python script on my home VPS, get the result back in Telegram, and pick up the same conversation from my laptop CLI when I get home. No tab juggling, no re-establishing context.

The gateway also handles voice memo transcription — record audio in Telegram, Hermes transcribes it, then operates on the transcript as if you'd typed it. For thinking-out-loud research workflows, this is the killer feature.

Best for: anyone whose work doesn't sit in one terminal window all day. Especially valuable for field researchers, clinicians, anyone in lab settings.

How does the self-improving skill loop work?

Hermes implements a closed learning loop: after complex tasks, the agent autonomously creates a skill (a SKILL.md file) that captures what worked. On future invocations, that skill is auto-loaded. If the skill needs refinement, the agent improves it during use.

This is grounded in the agentskills.io open standard — the same skill format used by Anthropic and the broader OpenClaw ecosystem. So skills you accumulate in Hermes work in Claude Code, and vice versa. No format lock-in.

There's also a _spawn_background_review() mechanism that periodically spawns a sub-agent to review your conversation history and persist memories. One GitHub issue calls this "an excellent mechanism." It's the kind of feature you don't realise you need until you've had it for a week.

For scientists: this means lab protocols, statistical workflows, and review patterns you teach the agent once are reused automatically next time — without you maintaining a prompt library.

How does the "any model, anywhere" promise hold up?

Switch models with hermes model. No code changes, no lock-in. The supported list is unusually broad:

• OpenRouter (200+ models including Claude, GPT, Gemini, DeepSeek, Llama)
• Nous Portal (Nous's own hosted endpoint)
• NVIDIA NIM (Nemotron family)
• Xiaomi MiMo, z.ai/GLM, Kimi/Moonshot, MiniMax, HuggingFace, OpenAI, or any OpenAI-compatible endpoint

In practice this matters because the right model depends on the task. Claude Sonnet 4.6 for coding, GPT-5 for legal-style reasoning, DeepSeek V3 for bulk research scans where cost matters. Hermes lets you swap mid-conversation — your context, memories, and skills come along.

What about running it "anywhere"?

Seven terminal backends ship out of the box: local, Docker, SSH, Singularity, Modal, Daytona, Vercel Sandbox. The headline trick is serverless persistence via Modal or Daytona — your agent's environment hibernates when idle and wakes on demand, so a long-running agent costs nearly nothing between sessions.

Practical setup options:

The $5 VPS path is what I'd recommend for first-time users — install Hermes, run hermes gateway, register a Telegram bot, done.

What does the community actually say?

Real signals from the open community, lightly paraphrased:

"Hermes is extremely capable. The architecture is solid and it can handle complex workflows really well. The downside, at least for me, is token usage." — early adopter comparing Hermes to OpenClaw

"Hermes has an excellent _spawn_background_review() mechanism that periodically spawns a sub-agent to review conversation history and save memories/skills." — community contributor

The two recurring themes in r/hermesagent megathreads:

• People love the cross-platform persistence (Telegram + CLI in one session)
• People build scheduled automations with the built-in cron — daily reports, weekly audits, GitHub PR reviews running every 2 hours

The official docs include a GitHub PR review agent tutorial that captures this pattern: cron schedule → agent reviews open PRs → delivers summary to Telegram. No webhook server needed.

The honest downside

Hermes uses more tokens than minimalist agents. The closed learning loop, background reviews, and cross-session memory all cost context.

If your goal is "cheapest possible single-turn agent," Hermes isn't it — pick a thinner harness. If your goal is "an agent that gets better over weeks of use," the token cost is the price of admission and worth paying.

A practical mitigation: use cheaper models (DeepSeek, Kimi) for the maintenance work (memory reviews, skill curation) and Claude / GPT for the actual work. The model-switching feature was designed exactly for this.

Why this matters for scientists specifically

For science workflows, three features dominate everything else:

1. Voice memo + Telegram: dictate observations from the lab bench, get structured notes back. No app context-switching.
2. Scheduled cron + delivery: nightly literature scan → morning Telegram summary. Weekly arXiv watch on your topic. Automated, persistent.
3. Skill loop: teach it your statistical preferences (e.g. "always check assumptions before t-test", "use BH correction for multiple comparisons") once, reuse forever.

These three together are what made me switch. We've listed Hermes Agent in the Claw4Science core group since March; the difference between listed and used daily turned out to be larger than expected.

How to install Hermes Agent

# Linux / macOS / WSL2 / Termux
curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh | bash

# Windows (PowerShell, early beta)
irm https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.ps1 | iex

# Then:
source ~/.bashrc
hermes

First-time setup:

hermes setup              # full wizard
# or step by step:
hermes model              # pick provider + model
hermes tools              # enable toolsets
hermes gateway setup      # configure Telegram/Discord/etc
hermes gateway start      # run the messaging gateway

Migrating from OpenClaw:

hermes claw migrate --dry-run   # preview
hermes claw migrate             # interactive

This ports your SOUL.md, memories, skills, command allowlist, API keys, and TTS assets.

FAQ

Is Hermes Agent free?

Yes. MIT-licensed. Free for personal and commercial use. You pay only for the underlying LLM API calls (which you control via hermes model).

Does it work without a paid API?

Yes if you run a local model via Ollama / LM Studio / vLLM, or use a free-tier endpoint (Nous Portal has one). Cloud APIs are usage-billed.

How is it different from Claude Code?

Claude Code is Anthropic's first-party CLI. Hermes is a harness — runs on top of any model, lives on any platform, persists across sessions, and works while your laptop is asleep (via gateway + VPS). Different layer of the stack; you can use both.

How is it different from OpenClaw?

OpenClaw is the broader open-source agent ecosystem. Hermes is Nous Research's specific harness within (and alongside) that ecosystem. hermes claw migrate ports your OpenClaw setup in one command.

What's the minimum hardware to self-host?

A $5/month VPS (1 vCPU, 1 GB RAM) is enough for the gateway. Heavy local work needs more. For local LLMs, GPU memory matches model size (16-48 GB VRAM typical).

Does it have a paper / arXiv?

No academic paper yet. The technical reference is the official documentation and the GitHub README.

Is it safe to give Telegram access to my files?

Hermes ships DM pairing + command approval + container isolation for exactly this concern. Out-of-the-box defaults require explicit approval for shell commands; you opt in to higher autonomy. See the security docs.

Try it

• Install — see commands above
• Repo — github.com/NousResearch/hermes-agent
• Documentation — hermes-agent.nousresearch.com/docs
• Community — Discord, r/hermesagent
• Listed on Claw4Science — core group

If you build a science-specific Hermes workflow worth sharing (cron'd literature scans, lab notebook automations, etc.), submit it — those are exactly the patterns we want to feature.

Last updated: 2026-05-17 (Hermes crossed 150K stars today; previous draft 2026-05-11 at 144K). Star count, model list, and feature claims verified against the official repo and documentation on the update date.