What Is Hermes Agent? The Open-Source AI Agent That Grows With You

Key Takeaways

• Hermes Agent remembers across sessions and writes its own skills, solving a gap OpenClaw never fully closed.
• Its self-evaluation often marks tasks successful even when they weren’t, so early skills need a second look before you trust them.
• Self-hosting means owning the server, the untested updates, and the security, the same tradeoff that applies to most open-source agents.
• Cloudways handles updates, isolation, and backups by default, while you still choose the model and channels Hermes uses.

Nous Research has a slogan for Hermes Agent: “the agent that grows with you.”

NVIDIA’s engineering blog keeps returning to a different word, reliability, since every skill that ships has actually been tested and reviewed first, rather than just released and hoped for.

Someone who lived with it for three months, deliberately breaking it and rebuilding it, landed on a more practical description. Just a different kind of software.

Cut past all three, and here’s what’s actually true:

Hermes Agent is open source and runs on a server of your choosing, not one controlled by Nous Research. You connect an AI model to it, tell it what you need done, and it carries that out on its own, checking back in with you only when something needs your input.

It’s not the first agent to work this way. OpenClaw, an earlier open-source agent, figured out how to act independently first. What Hermes added on top of that was memory that actually sticks, remembering things between sessions instead of forgetting everything the moment you close the app.

Is Hermes Agent an AI Agent or Just Another Chatbot?

Ask a chatbot something, and you get an answer. Nobody goes back to check if that answer actually held up. Hermes was built to do exactly that.

Hermes Doesn’t Just Remember, It Teaches Itself

Hermes gets a task. It runs the task. Then, on its own, it stops and asks itself a question, did that actually work?

If the answer is yes, it writes the method down, names the skill, and files it away, ready to reuse for similar tasks going forward.

Nous Research breaks this into four stages, execute, evaluate, extract, refine.

The evaluate stage is where users on Reddit keep finding problems. Across more than 1,300 comments pulled from r/openclaw threads, the same complaint kept resurfacing, Hermes almost always decides it did the job correctly, even when it didn’t.

One user described asking it to pull water test results from a state environmental site. It jumbled the numbers and reported back as if the job had gone perfectly, which matters because a wrong result marked as a success gets saved as a skill too, and repeated the next time a similar task comes up.

The skill-writing part is genuine. The part deciding whether a skill was worth writing in the first place hasn’t caught up yet.

How Does Hermes Agent Work?

A gateway to connect your messaging apps, a memory that updates itself, a system that turns finished work into skills, and whatever model you choose to run. Take any one of those away, and it isn’t Hermes anymore.

The Gateway Connects Hermes to Your Messaging Apps

Nous Research’s own site lists seven ways to reach it, Telegram, Discord, Slack, WhatsApp, Signal, Email, and the command line, all running through one process behind the scenes.

Cloudways has four of those wired up in the dashboard, Telegram, Discord, Slack, and WhatsApp. The other three still exist, just not as a toggle you click. You’d be configuring them by hand.

Skills, How Hermes Writes Its Own Instructions

Finished work becomes a plain text file, sitting somewhere on the server.

Nous Research didn’t invent a new format for this. They built it on agentskills.io, an open standard OpenClaw’s ecosystem also uses. Practically, that means a skill built for OpenClaw sometimes runs on Hermes without any changes, so switching between the two, or running both, doesn’t always mean starting from zero.

How Hermes Remembers You Across Sessions

Two systems handle this, and they do very different things.

FTS5 is a search extension borrowed from SQLite, letting Hermes dig back through old conversations by keyword instead of pretending they didn’t happen. Honcho dialectic modeling is the other half, gradually building a picture of who you are, what you prefer, how you work, so instructions you gave weeks ago still shape how it responds today, not just what you said five minutes back.

There’s a limit to how much it can hold at once, the file it writes to has a hard size cap, and hitting that cap means someone has to manually clean it up.

Why Hermes Needs Your Own AI Model

No model comes built into Hermes AI agent. That’s a deliberate choice, not an oversight.

Plug in Claude, GPT, Gemini, or an open-weight model through OpenRouter, and Hermes routes everything through whatever you’ve connected. Change your mind later, and one command swaps the model out. No uninstalling, no rebuilding.

An Agent That Remembers, Ready in Minutes

Skip the server setup and start talking to Hermes through the channels you already use.

Launch Hermes

What Can You Use Hermes Agent For?

The users who get the most value out of Hermes aren’t running one-off tasks.

They do a consistent type of work over and over, where the last time informs how the agent handles the next.

That’s what the memory is for. It wouldn’t matter for a task done only once.

Ongoing Research Projects

Say you’re tracking a competitor’s pricing changes over several months.

Hermes keeps its own notes as it goes, and can search back through them. A question you ask in month three has the context of everything asked in month one, without you re-explaining who the competitor is each time.

Recurring Technical Work

Pointing Hermes at the same class of problem more than once is another obvious use. A service that keeps failing for the same underlying reason. A log pattern that needs checking every time it shows up.

Handle it manually once, and Hermes writes the process down as a skill so it doesn’t have to be solved from scratch again.

The SSOJet documentation has a real example of this, a skill for detecting and recovering a lagging Postgres replica, written entirely by the agent after it handled the issue manually one time.

Personal Project Continuity

Working alone has its own tradeoffs compared to working with a team.

Hermes has nothing to consult except its own memory when a project picks back up between sessions. Whatever it wrote down is the only continuity that exists.

That’s valuable. It’s also a liability for any task Hermes only thought it completed correctly.

The Honest Limitations of Hermes Agent

Three issues come up consistently for anyone who’s used Hermes for more than a week.

Self-Evaluation Passes Almost Everything

At the end of every task, Hermes runs a self-check to decide if the outcome was a success.

It calls most tasks successful, even ones that shouldn’t be. That matters past the moment it happens, since anything marked successful can get saved as a skill for later reuse, whether it deserved that label or not.

When Memory Fills Up, It Just Stops

The memory file Hermes writes to has a size limit.

Hit it, and the agent can’t write anything new to memory, no automatic trimming, no cleanup. Someone has to open the file and consolidate it by hand. OpenClaw solved this differently, its own memory compacts on its own once it reaches a size threshold. Hermes doesn’t do that yet.

Skills Drift, and the Self-Patching Doesn’t Always Help

Say Hermes learns that invoices need dashes instead of slashes. That rule holds until the underlying project changes, the client switches systems, say, and wants slashes again. Hermes has no built-in way to know the old rule is dead. It might keep applying it, or patch it wrong once something looks off.

Nous Research’s own documentation names this directly, skills drift out of date as the project underneath them changes, and Hermes can patch a skill to catch up automatically. That patching happens without asking first, and the patch is sometimes worse than the skill it replaced.

One independent audit of long-running Hermes setups found a related, smaller issue, a minor formatting mismatch got absorbed into memory as if it were a real user preference. Weeks later, the agent believed it had a different set of preferences for the same user it talked to every day.

There’s a partial fix. A background process called the Curator runs roughly once a week, moving skills nobody’s used recently out of the active list instead of leaving them there forever. It never touches anything installed from the community hub, only skills the agent wrote itself.

It solves pile-up. It doesn’t undo a bad patch already sitting inside a skill someone’s relying on right now.

None of this makes Hermes unusable for most people. It just means treating its early skill-writing like a new hire’s first few weeks, useful, mostly right, and worth checking before trusting completely.

The Risk of Self-Hosting Hermes Agent

Hermes has to live somewhere before any of this works. Setting that up in the first place is a bigger job than it sounds like.

Setting It Up Takes Real Time

Installing Hermes is not a five-minute exercise. There’s a server that needs to stay on, a model connected through your own API key, and each messaging channel connected by hand, same list of options covered earlier, none of them arrive pre-connected.

None of this is exotic. It’s just time most people don’t budget for before they start.

Updates Are Your Job Now

Nous Research has already shipped 11 versions of Hermes, a rapid pace for such a young project. Each one can fix something, add something, or occasionally break something that worked fine the day before.

On a self-hosted setup, nobody tests an update before it reaches you. Say a new release changes how Hermes talks to your model provider. You won’t know until your agent stops replying and you’re the one digging into logs to figure out why.

Security Sits on Your Shoulders

Hermes has direct access to your files and your messaging accounts. That access is the entire reason for using it, and it’s also the entire risk if the server underneath isn’t locked down properly.

In practice, that means deciding who else can reach the server, keeping the software on it up to date, and making sure a stranger on the internet can’t simply walk in through an open port. None of that comes bundled with Hermes. It comes with whoever set the server up, which is you.

The Real Cost Isn’t the Server Bill

A basic server is cheap, usually just a few dollars a month. The real cost is your time, watching the server, catching problems early, fixing them once they show up.

If Hermes is a side project, that time cost might not matter much. If you’re relying on it every day, that ongoing attention is the actual price, even though it never shows up on a bill.

Skip the Server Babysitting

No provisioning, no untested updates landing on your agent mid-task. Just connect a key and go.

Deploy Hermes

How Managed Hosting Solves Hermes Agent’s Reliability Problem

Nearly every risk covered in the last section comes down to one fact: when you self-host, you’re the only person checking that a bad update doesn’t break your setup. Managed hosting puts a second person on that job.

Setup Takes Minutes, Not an Afternoon

Self-hosting means provisioning a server, installing everything Hermes needs, and connecting each messaging channel yourself. Cloudways skips most of that. You get a server with Hermes already installed, ready to configure from a dashboard. Pick a plan, add your model’s API key, and most of the setup is done. You still have to connect each messaging channel individually, that step doesn’t go away, but everything around it does.

Someone Else Tests the Updates First

When Nous Research releases a new version of Hermes, it doesn’t go straight to your instance. Cloudways checks it first. If the release causes a problem, it gets held back until that’s fixed, so you’re not the one finding out mid-task that something broke.

The Server Comes Locked Down

On a self-hosted setup, you decide who can reach the server and which ports stay open. On Cloudways, that’s already handled, the server starts isolated and secured. Hermes still has full access to whatever you connect it to, your files, your messaging accounts, but the server itself isn’t exposed for anyone outside to find.

You Still Own the Model, Not the Server

Managed hosting doesn’t change your relationship with the AI model. You still choose which model powers Hermes, still pay that provider directly, still decide which channels it can use. What changes is who’s responsible for the server underneath it.

Learn more about Cloudways managed AI agents.

What’s Included in Cloudways Hermes Hosting

The last section explained what managed hosting fixes. This one covers exactly what you get.

Validated Updates and Security

Every Hermes release is checked by Cloudways before it reaches your instance. If a release causes issues for other users, it gets paused for everyone until the issue is fixed.

Each instance also runs on its own dedicated resources. Nobody else’s traffic, activity, or configuration can affect your instance in any way.

How BYOK Works on Cloudways

Whichever model you connect, Anthropic, OpenAI, Google, or an open-weight model hosted elsewhere, bills you directly. Cloudways only charges for the server Hermes runs on.

That separation matters for one practical reason: upgrading your Cloudways plan for more server power doesn’t change what you pay your model provider, and switching models doesn’t change your server bill. The two costs never mix.

Terminal Access for Power Users

Managed hosting doesn’t mean you lose access. Every Cloudways plan includes SSH access to the server, so you can check logs or make manual changes if you want to.

Most people won’t need this. It’s there for the people who do.

Both OpenClaw and Hermes run on the same Cloudways infrastructure. Because they share the agentskills.io format, some skills built for one also work on the other, so trying the second tool later doesn’t always mean starting from zero.

Everything Included, Nothing to Manage

Tested updates, an isolated server, and full terminal access, all on one Hermes plan.

Get Started

Hermes Agent vs OpenClaw: Which One Should You Run?

An analysis of over 1,300 comments across 25 threads in r/openclaw found no clear winner. The community splits into roughly four camps, and each one has a legitimate reason for its choice.

Where OpenClaw Wins

OpenClaw supports more messaging channels and has a much larger library of community-built skills, tens of thousands, compared to Hermes’ smaller collection.

It also natively supports running several separate agents at once, each with its own memory and its own job. And it’s been around longer: 137 releases at the time of that analysis, versus 11 for Hermes, meaning more time for real-world problems to surface and get fixed.

Where Hermes Wins

Users who’ve tried both tools report an easier setup process with Hermes. Its default memory settings also need less manual tuning to work well.

And according to the same analysis, Hermes has a checkpoint-and-rollback feature, the ability to undo a bad update with a single command, which OpenClaw doesn’t have.

Where Neither Has Fully Solved the Problem

OpenClaw isn’t without its own issues.

That same analysis found users reporting that recent updates broke cron jobs and message delivery. Hermes has a different problem, the self-evaluation flaw covered earlier, where it often believes a task succeeded even when it didn’t.

Choosing one tool over the other isn’t about avoiding flaws. It’s about deciding which set of flaws you’re more willing to manage.

Running Both

Some experienced users don’t choose at all. A setup that comes up repeatedly pairs OpenClaw for scheduling and multi-channel routing with Hermes for repeatable execution tasks, the two connected through a shared protocol.

Choose OpenClaw if you want one clear answer instead of four options and if you want more channels and don’t mind more setup work.

Go with Hermes if you want less configuration and don’t mind a newer, less proven tool.

If you’re still unsure, either is a reasonable starting point, and picking one now doesn’t stop you from trying the other later.

The Bottom Line

Hermes Agent solves something OpenClaw never quite nailed: memory that survives past the session it was created in. That’s the actual reason it’s worth knowing about.

It also comes with real, current limitations. Self-evaluation that trusts itself more than it should. A memory file with a hard ceiling. Skills that drift and sometimes get patched wrong. None of that makes it a bad tool. It makes it a young one, still catching up to what it’s trying to do.

Running it yourself means owning every part of that directly, the server, the untested updates, and the moment something breaks, with nobody else checking the logs.

Cloudways changes who’s standing in that gap. Updates get tested before they reach you. The server starts isolated instead of exposed. What you choose, which model, which channels, stays entirely yours.

The memory problem is the one worth paying attention to here, not which version number Hermes happens to be on this month.

Your First Agent, Running Today

Pick Hermes or OpenClaw, connect your key, and let it start remembering from day one.

Explore AI Agents