Hermes Agent: The OpenClaw Alternative That Actually Works

A while ago I set up OpenClaw. After about five minutes I immediately realized what a security nightmare it was and uninstalled it. But those five minutes got me thinking about the possibilities. Setting up an agent as a second brain, a personal assistant that's always available, opens up a lot of interesting use cases.

OpenClaw is vibe-coded quite sloppily though. Even within those five minutes of testing it had already glitched out. I uninstalled it and moved on with life. But recently I found Hermes Agent from Nous Research, and this one is different.

What Makes Hermes Different

For one, it's actually well made. I've run into a couple of configuration issues here and there, but for the most part it works quite well. It's got a good amount of features and integrations out of the box, and if you need something custom you can always just ask it to make it. The GitHub repo has over 23k stars and I see commits every day.

I've been running it with FirePass from Fireworks AI, which serves KIMI K2.5 at a really fast inference speed. We're talking up to 200 tokens per second. Super responsive, and at $7/week for unlimited developer tokens it's hard to beat. I talked about FirePass in my Claude Code alternatives post.

Running It on a Server (The Right Way)

I'm currently running Hermes inside a Digital Ocean VPS, which means I can give it access to everything on the server. Hermes has some cool sandboxing options if you don't want to go that route. You can have it only execute code in a sandbox container like Docker, a remote container like Daytona, or even have it SSH into a separate server as its sandbox environment. That's way safer than running code directly on your laptop.

I think giving it a dedicated server is the best approach. Higher uptime, you don't have to keep your laptop running, and after you connect it to Telegram you can message it from anywhere.

Why I Actually Use It: Messaging from Anywhere

When I'm at my desk I have Claude Code, Codex, and a dozen other coding tools. Hermes isn't competing with those. Where it shines is when I'm away from my computer.

I use it a lot on the train. Pulling out a laptop on a crowded commute isn't practical, and the internet is spotty, but Telegram messages usually get through. I can ask Hermes to check if a PR has merge conflicts, draft a reply to an email, or look up documentation for something I'm thinking about. By the time I get to my desk, the work is already done.

That's the real use case: not replacing my desktop setup, but having an assistant I can text from my phone when a laptop isn't an option.

What I Have It Connected To

My current setup has Hermes connected to Linear so I can create issues and check project status, Google Workspace for email drafts and calendar management, and GitHub for repo access and PR reviews. Telegram is the interface I message it through.

Hermes supports a lot more: Discord, Slack, WhatsApp, Signal, even iMessage if you're on Mac. I stuck with Telegram because it works well on both my phone and laptop, and the bot API is solid.

Running Claude Code on the Same VPS

On the same server, I also run Claude Code with full permissions and a Telegram interface. The idea was to have a more powerful coding agent I could message remotely.

It's still experimental and pretty rough. There's no way to really control it remotely: you can't clear the context, send slash commands, or do anything except send messages. It kind of works, but in practice it's much better to either ask Hermes to do the task directly, or ask Hermes to launch and control a Claude Code session for you. Hermes can spin up Claude Code, feed it a task, and report back with the results. That flow is way more reliable than trying to control Claude Code through raw Telegram messages.

Memory Systems: The Best Part (and the Rough Edges)

The best part of Hermes is that it continually learns as you use it. It has several memory systems that build up over time. It creates skills, remembers your preferences, and generally becomes better at doing things the more you use it. This is what makes it feel like a real assistant rather than just a chatbot.

Unfortunately, this is also where I ran into the roughest edges.

I tried Mem0 first. It worked, but it's really not a great memory system. The recall is mediocre and it doesn't feel like it's building up a real understanding of who I am.

Next I tried Honcho, which is a very interesting concept: a memory system that learns and uses LLMs internally for reasoning. Unfortunately it was mis-attributing everything. Things I said were being attributed to the AI agent, and everything was backwards. Didn't stick with that.

I've been trying Holographic, which ships with Hermes, but that hasn't been super useful either. It's just not putting memories in there reliably. Hermes has 8 different memory providers to choose from, so I'll keep experimenting. If you have suggestions on this, I'd love to hear them.

Customizing Your Agent's Personality

There's a lot of fun in personalizing your agent and making it the kind of agent you want. You can set up the soul.md file, which defines how it acts and responds. You can play around with different ideas for what your AI assistant should sound like and act like. Want it to be formal? Casual? Sarcastic? That's all configurable.

If you're interested in how I structure projects for AI agents generally, I wrote about that in How I Structure Projects for AI Agent Collaboration. A lot of the same principles apply to setting up Hermes.

Frequently Asked Questions