This Unlocks So Many Insane Hermes Use Cases — Transcript

Explore how the Hermes agent's self-evolving skill system and persistent memory unlock powerful automation use cases, especially when paired with Claude Code.

Key Takeaways

Hermes offers superior automation capabilities through self-evolving skills and smarter memory management.
Pairing Hermes with Claude Code enhances autonomous workflow creation beyond typical personal agents.
Hermes runs securely in a sandboxed environment, reducing security risks present in OpenClaw.
Upcoming pricing changes for Claude Code usage may impact free agent operation after June 15th.
Setup is user-friendly and flexible, supporting import from OpenClaw and multiple deployment environments.

Summary

Hermes agent is a powerful personal agent with features surpassing OpenClaw, including persistent memory and self-improving skills.
Combining Hermes with Claude Code creates highly autonomous workflows that can automate complex tasks.
Hermes was developed by Noose Research and predates OpenClaw, offering a more secure sandboxed environment.
Persistent memory in Hermes intelligently manages token limits by pruning outdated information to maintain focus.
OpenClaw lacks Hermes's memory management and sandbox security, leading to potential issues.
Upcoming changes after June 15th will introduce extra costs for using Claude Code with third-party apps like Hermes.
Setting up Hermes is straightforward via terminal commands, with options to import OpenClaw data or configure manually.
Hermes supports multiple deployment options including local machines and VPS, and can connect to various messaging platforms like Discord.
Users can personalize Hermes by providing direct info or linking to a second brain vault for onboarding.
The video also highlights practical considerations around subscription costs, setup challenges, and agent customization.

Full Transcript — Download SRT & Markdown

Speaker A

You've probably already heard by now that the Hermes agent is the most powerful personal agent around, and that's not wrong. It actually has numerous features that make it so much better than OpenClaw. But what happens when you connect it to one of the most

Speaker A

powerful coding agents out there, Claude Code? On its own, Claude Code is great, but it's missing one crucial part from the Hermes agent, the self-evolving skill system. Paired with that, you can create workflows that are so much more

Speaker A

autonomous, even for things that we didn't think could be automated. But other than as a personal agent, you can set it for any business that wants to automate their processes. And it's really simple. But since a lot of you

Speaker A

might be new to the Hermes agent, you don't need to worry as we're going to guide you through it. But before we get into the setup, let's start with why the self-evolving skill system matters in the first place. When we came across it,

Speaker A

we figured it might actually be better than OpenClaw. It wasn't just some random project. It's actually built by Noose Research, one of the leading labs in open source AI, and it has become one of their most popular projects. Also,

Speaker A

here's something interesting. The Hermes agent was actually built before OpenClaw. It just didn't get much hype at first. The people over at Noose Research also tried OpenClaw, but they ran into issues with it, so they switched to their own setup. They saw

Speaker A

its problems firsthand and open-sourced their solution. Most of the features Hermes has are the same as OpenClaw's.

Speaker A

Just like OpenClaw, you can connect it to multiple platforms. But there are two things that make it so much better. The first is persistent memory, and the second is self-improving skills.

Speaker A

OpenClaw already has persistent memory, which lets it remember information about you and shape its answers to what you like. But that has its limits, too.

Speaker A

Hermes goes further. It saves those memories, and whenever it finds a reusable workflow in your chats, it turns it into a skill. Hermes's persistent memory is built on a really smart setup. Hermes puts a limit on how large the user.md and memory.md files

Speaker A

can be. As you're chatting with the Hermes agent, it keeps updating those files after each run. Now, why does that limit matter? It's because of how models work. Just like you, a model also has a really bad attention span. It can only

Speaker A

focus on a limited amount of information at a time, and it gets confused when it's given a lot of information. And all that information from the prompts and tools to the system instructions and on top of that your own files is fighting

Speaker A

for the model's attention in the context window. So the more you fit into that context, the more the model loses focus on the actual task because all the extra information becomes noise to the agent.

Speaker A

So that token limit is there to prevent this from happening. Once Hermes hits the token limit on the files, the model goes through them and cuts out anything that isn't useful. It holds the newest information in memory so the agent isn't

Speaker A

distracted by old details you don't need anymore. OpenClaw doesn't do any of this. It just lets the memory keep growing. There's another issue we faced with OpenClaw. To secure it, we had to sandbox the agent ourselves. Hermes runs

Speaker A

in a sandbox on its own. That means it runs in an isolated environment where it can't reach things it shouldn't or accidentally do something it isn't supposed to. So, it gets rid of most of the security problems OpenClaw had. And

Speaker A

if you want to run Hermes with a Claude Code setup, now is the best time to do it because greedy little Daario discovered another way to make money off Claude by starting to charge for using your Claude subscription with

Speaker A

third-party applications. After June 15th, you won't be able to use your Claude Code subscription to run agents like Hermes for free. You'll have to pay Anthropic extra. Your plan will include a monthly agent SDK credit, and that credit gets spent whenever you connect a

Speaker A

third-party app through your subscription. The same limit applies to running Claude in non-interactive mode, which is the mode a lot of agents use to run Claude Code in the background without needing any permission prompts.

Speaker A

So until June 15th, you can keep running the Hermes agent without the ridiculous API costs. Now, setting up the Hermes agent is actually pretty simple. You just copy the install command and run it in your terminal. It first installs all

Speaker A

the dependencies it needs, then runs the installer in interactive mode. If you want to set the agent up on the new plan where you get their models and built-in tools, you can go for it. But we wanted our own setup, so we went with

Speaker A

the manual option. You can also reconfigure the agent later on using the Hermes setup command. This step is where you set up everything the agent needs.

Speaker A

Hermes can import from your previous OpenClaw settings. So, it first asks whether you want to bring those over.

Speaker A

You can check for yourself exactly what gets brought over, which covers your user profile and credentials along with your skills and your soul file, which is basically the agent's personality and instructions. But just like how your bloodline's been passing down that

Speaker A

amazing height for generations, inheriting from one agent to another comes with its own issues. The login details you bring over still point to the same channels your OpenClaw agent used, and the files OpenClaw relied on don't carry over cleanly because those

Speaker A

instructions were written specifically for OpenClaw. So importing them just causes problems and that's why we chose not to import ours. After that, you choose which model Hermes uses. We wanted it on Claude models through the Anthropic subscription. But when we

Speaker A

tried it, we couldn't actually use the Claude models and got an error. Turns out Daario was already asking us to set up that extra usage even though it's not June 15th yet. So that policy might already be rolling out gradually, but it

Speaker A

might still work for you. Either way, we could still use Claude Code in non-interactive mode right now, which is what we'll be using for most of our tasks anyway. And you can change your model provider anytime later on. Once

Speaker A

the model is set, it asks where the agent will actually run, whether that's on hosting or a VPS you've set up. And for those of you who don't know, a VPS is basically a server you rent and run

Speaker A

yourself. But since we have Mac Minis running entirely for this, we went with the local option. And no, we weren't the ones who caused the Mac Mini shortage because unfortunately, just like you, our AI B2B SaaS business actually ran out

Speaker A

of funding. After that, it asks you to connect whichever messaging platform you want. We chose Discord, but you can connect any of them. We won't walk through the Discord bot setup here, but you'll find the full instructions in our

Speaker A

community, AIABs Pro. Once that's done, it asks a few more questions, and your agent is ready. You just type Hermes, and once the UI loads, you can start chatting with the agent right there. In order to tailor itself to what you

Speaker A

actually need, it needs information about you. So, you can either keep using it for a month and let it figure you out on its own or just tell it who you are upfront before it touches any other task. If you want to set it up as a

Speaker A

personal agent, you can either give all the information about yourself in the chat. Or if you'd rather not type it all out, link it to your second brain vault instead. Just give it the path to your second brain and tell it to onboard

Speaker A

itself from there and it learns everything about you that way. If you want to set it up for a specific automation use case, just provide the docs of the use case or the general info about the company that it's being set up

Speaker A

for. But before we move forward, let's have a word by our sponsor. So, if you're building with AI tools every day, but don't fully understand how LLMs, agents, or protocols like MCP actually wor

Speaker A

fast. That's where Educative comes in. as an interactive platform used by over 3 million developers with 2,300 plus courses where you code in the browser with no setup and get AI powered feedback on every submission. I'd start with their essentials of large language

Speaker A

models course in 2 hours. It breaks down how LLMs work from tokenization to attention mechanisms to rag. You'll finish with a real mental model of what's happening under the hood. From there, MCP fundamentals teaches you to build AI agents using the model context

Speaker A

protocol. Agentic system design goes further. Multi-agent systems that reason, plan, and act autonomously. Then the 16-hour LLM boot camp adds hands-on AWS labs in Bedrock, SageMaker, and Langraph. You'll fine-tune a model, build multi-agent systems, and ship a rag chatbot. You're writing real code

Speaker A

from the very first lesson, not sitting through tutorials watching someone else build. Educative has helped more than 10,000 developers land jobs at top tech companies. Try it free. Link in the description. You can build a collection of skills for your Hermes agent from the

Speaker A

skill hub. That's their official marketplace for skills and it has skills for all kinds of use cases. Hermes also comes with 90 skills installed by default. Those pre-installed skills are actually secure because they are maintained by the organization itself.

Speaker A

That's a real difference from openclaw skills, which we covered in our previous video. A huge number of those weren't safe at all with security issues like dangerous prompts and scripts that can literally transfer your data off to some

Speaker A

server. And the skill hub actually runs a security scan on each skill and watches for these issues. That way you can add the skills you want without the same risk. Just like any other agent, you can connect any MCP you want to

Speaker A

Hermes. But here's what separates Hermes from the rest. You can run your own Hermes setup as an MCP server itself and connect it to your other agents, letting them reach Hermes through tools. So the communication goes both ways. Connecting

Speaker A

Hermes to other agents this way fills in what those agents are missing. An agent like Claude Code on its own doesn't remember anything about you and its skills don't fix or improve themselves.

Speaker A

But through this MCP connection, you can give it access to everything Hermes can do. It also means you reach every app you've already connected to Hermes without wiring each agent up to each app separately. They just use those apps

Speaker A

through your Hermes setup instead. To run Hermes as an MCP, you run the Hermes MCP serve command. There's no output on the terminal saying the server is up, but it's actually started running as the MCP server. To connect it to your agent,

Speaker A

you add the Hermes MCP to the MCP.json file and then it's usable. You can set it at project scope, which means only the project you're working on gets access. Or you can add the config to the root.claude folder and then the Hermes

Speaker A

MCP is available across all your projects. And speaking of skills, Hermes comes bundled with a Claude code skill which has guidance on how to use Claude code through the agent. So combined with the Hermes setup running as an MCP, this

Speaker A

unlocks a lot for us. The Hermes agent and Claude Code together open up a lot of use cases, especially in businesses where multiple automations can be set up to handle repeatable processes. One of those is connecting Claude code to your

Speaker A

team's Slack workspace. This works really well because Hermes is basically an always running agent while Claude code is where the actual development happens. So we use the Hermes agent to access the team workspace just like with the Discord setup. We won't walk through

Speaker A

the Slack connection here either, but you'll find the full guide in our community. In most workspaces, you could have a dedicated channel for a project where the whole team discusses different points about it. What you can do with

Speaker A

the Hermes agent is ask it to create a cron job that monitors that specific channel. from the requirements being discussed there. It builds a PRD skill that evolves as those requirements change. Having the PRD as a skill is

Speaker A

really helpful, especially during the sessions where you're actually developing the product whenever it's needed. It pulls the relevant parts of the PRD into the context so the project stays aligned with the original requirements. The PRD on its own might

Speaker A

work too, but for the same reason we talked about earlier, the agent sometimes gets confused about what it needs to pay attention to. A skill gets called whenever it's needed and stays in the fresh part of the context window

Speaker A

where the model is actually paying attention. So Hermes creates the skill the way you instructed and runs it every 30 minutes as a cron job. This way whenever a requirement change gets discussed in the channel, it updates the

Speaker A

PRD and the Hermes agent makes sure those changes flow both ways. So the skill created inside your project stays updated too. At this point, you might be thinking, since we already have an MCP connected for the Hermes agent, why not

Speaker A

just use a tool to pull the information from that Slack channel and have the agent act on it? The reason is that the Slack MCP has a limitation. It can't read the entire conversation history by default. It only reads the messages it's

Speaker A

tagged in, and it won't pull the full history unless the tagged message specifically needs that context. So, setting it up through the Hermes agent is the better route because it can sync the information directly from there.

Speaker A

From there, you can also ask it to implement any feature using claude code in non-interactive mode directly through the Hermes agent channels. It loads that Claude code skill we talked about earlier, then launches Claude code and uses it to build the feature. Also, if

Speaker A

you are enjoying our content, consider pressing the hype button because it helps us create more content like this and reach out to more people. You can also bolt Hermes onto a deployed app, whether you're building it for yourself

Speaker A

or for a client. So if you have a deployed app built with cloud code, you can create skills for monitoring and health checks that guide the agent on how to monitor the running app because cloud code has the best context on what

Speaker A

the app actually needs. Then you import those skills into your Hermes agent. You can set up a cron job for that.

Speaker A

Basically a task that runs on its own on a schedule and let the agent monitor both the hosted app and the code. We also told it that if it finds an issue while running the skill and updates it,

Speaker A

it should sync those skills back to the local project. So Claude code has context on them too. So this is how its self-evolving skills help in setting up a continuous health check that gets better every time it runs. So once you

Speaker A

give Hermes the prompt, it sets up the chrome job for you. You can test run it to see if it's configured properly. It gives you a report in whichever channel you set up. And in our case, it reported

Speaker A

in Discord. And with the MCP configured, you can get those reports right inside Claude Code along with all the suggested fixes from other team members and implement them directly in your project.

Speaker A

or you can push those fixes yourself or even set up the Hermes agent to fix the issues it found using clawed code. If you want to found the next big AIB SAS company and automate everything like we did with Hermes, you should be in AIABS

Speaker A

Pro. That's where you'll find the setup guides from this video along with all the other resources and goodies we've put together. You'll also get to meet a bunch of like-minded nerds, including our team. The links in the description

Speaker A

and you can check that out. That brings us to the end of this video. If you'd like to support the channel and help us keep making videos like this, you can do so by using the super thanks button

Speaker A

below. As always, thank you for watching and I'll see you in the next one.

Topics:Hermes agentClaude Codeself-evolving skillspersistent memoryautomation workflowsOpenClaw comparisonAI personal agentsandbox securityAI LABSagent setup

Frequently Asked Questions

What makes the Hermes agent better than OpenClaw?

Hermes improves on OpenClaw by offering persistent memory that prunes outdated info to maintain focus, self-improving skills that create reusable workflows, and a secure sandboxed environment to reduce security risks.

How does Hermes manage memory differently from OpenClaw?

Hermes limits the size of memory files and prunes unnecessary information to prevent the model from losing focus, whereas OpenClaw allows memory to grow unchecked, which can confuse the model.

What changes are coming to Claude Code usage with Hermes after June 15th?

After June 15th, using Claude Code with third-party apps like Hermes will incur additional charges from Anthropic, requiring users to pay extra beyond their Claude subscription.

Get More with the Söz AI App

Transcribe recordings, audio files, and YouTube videos — with AI summaries, speaker detection, and unlimited transcriptions.

App Store Google Play

Or transcribe another YouTube video here →