HomeVideos

You NEED to set up a multi agent team with OpenClaw and Hermes

Now Playing

You NEED to set up a multi agent team with OpenClaw and Hermes

Transcript

507 segments

0:00

Open Claw and Hermes Agent is the most

0:02

powerful combo in AI right now. When

0:05

used together, you literally gain

0:07

superpowers and your productivity

0:09

explodes. In this video, I'm going to go

0:11

over why having these two AI agents

0:13

working together is incredible, why you

0:15

absolutely need to be building a

0:17

two-agent setup, and I'll show you some

0:19

use cases that have improved my

0:20

workflows a ton. If you stick with me

0:23

until the end of this video, you're

0:24

going to have an army of AI agents

0:26

making your life so much better. Let's

0:30

get into it. So, I have been playing

0:31

around a ton with Open Claw and Hermes

0:33

Agent over the last few weeks, and I

0:35

have come up with a system that is

0:37

amazing. First, I want to tell you why

0:39

having a multi-agent workflow is the

0:42

future and why you need to be building

0:43

this out immediately. The reliability of

0:46

my AI agents has exploded since I

0:49

started using these two together. One of

0:51

the biggest complaints I get all the

0:53

time is, "Oh, my Open Claw is constantly

0:55

breaking." or "Oh, my Hermes Agent is

0:57

constantly breaking." have them working

1:00

together, your downtime turns to zero.

1:02

The moment one of them goes down or

1:04

doesn't perform well or breaks or does

1:06

something wrong, the other comes in and

1:08

fixes it easily for you. So, the

1:10

reliability of your entire AI agent

1:13

system gets so much better when you

1:16

start using these two together. You're

1:17

basically building your own AI company

1:20

where these two AI agents have each

1:22

other's back, supports each other's

1:23

work, and make sure they both do amazing

1:25

things. These are also two very

1:28

different AI agent harnesses. They both

1:30

have very different strengths. The

1:32

people go on Twitter saying, "Oh, one

1:34

killed the other." or "One's better than

1:35

the other." They're idiots. They don't

1:37

know what the hell they're talking

1:38

about. You want to use them together cuz

1:40

they both have very different strengths

1:42

that complement each other really well.

1:44

And I'm going to second go over what

1:46

those strengths are and which you want

1:47

to use for each. It allows you to make

1:50

sure the best task gets handed to the

1:52

right agent, so the task get done

1:55

better, quicker, and cheaper. With this

1:57

setup I'm about to show you, you're

1:59

going to be saving a ton of money

2:01

because you'll be able to use the right

2:03

agents with the right models for the

2:04

right tasks, and you're going to be

2:06

getting more done at the exact same time

2:08

because you'll be able to multitask and

2:10

have the better task getting done by the

2:12

right agents. So, before I pop open

2:14

those two agents and I show you real

2:16

quick how to set them up, install them,

2:17

all that, here's just where I see their

2:20

strengths and weaknesses at the moment

2:21

and how they complement each other so

2:23

well when you use them together. And

2:25

then again, right after this we'll also

2:26

go over the workflows of using each.

2:28

Open Claw I'm using as my main agent.

2:30

The reason why I'm doing that is it's

2:32

just proven for me personally to be much

2:34

more stable, to get updates quicker, and

2:37

just a lot more reliable when getting

2:39

big tasks done. Hermes agent on the

2:42

other end has been a great

2:44

assistant/monitor

2:46

for me, and I'll show you what that

2:47

means in a second. But, it's been great

2:49

at assisting Open Claw. It has been much

2:52

more performant for me. And basically,

2:54

it's a lot faster and using a lot less

2:56

tokens, which has been great. A big

2:58

reason for that is it's just a lot

2:59

lighter weight. I think it was designed

3:02

a lot more efficiently than Open Claw.

3:04

And the best part about all these is

3:06

Open Claw's been great at keeping Hermes

3:08

agent working, and Hermes agent's been

3:09

great at keeping Open Claw working,

3:11

which has been fantastic. I haven't had

3:13

basically a second of downtime since

3:16

these two started working together. The

3:17

moment one breaks, the other swoops in

3:19

and fixes it, which has been great. So,

3:20

with that being said, knowing what each

3:22

strengths and weaknesses are, how one is

3:24

a main agent, and how the other is an

3:26

assistant, let's go over how to use them

3:28

together and some workflows I think will

3:30

be amazing for you. So, here we go. I

3:32

got my Open Claw Henry on the left. I

3:34

got my Hermes agent Hermes on the right.

3:37

I apologize when I named my Hermes

3:38

agent, I was not feeling creative in the

3:40

moment, so it's just named Hermes. It is

3:42

what it is. What I'm going to show you

3:44

now is how I use them together, some

3:47

workflows you can steal immediately that

3:49

I think will improve your life a ton,

3:51

and when you want to be using each. So,

3:53

let's talk about models I use for each.

3:55

First of all, Henry is powered by Opus

3:57

46. I'm just going to be honest with

3:59

you, Opus is the best model for AI

4:01

agents. It is what it is. I want ChatGPT

4:04

to be good for AI agents, but it just

4:06

isn't. So, I highly recommend using

4:09

Opus, the API, for your main Open Claw

4:13

agent. I understand it's pricey, but if

4:16

you want the absolute best performance,

4:18

you have to be going with Opus. If price

4:20

is a big thing and you can't be spending

4:22

that money on Opus, the next best model

4:26

is ChatGPT. You can plug in your ChatGPT

4:29

OAuth really nicely with the existing

4:31

plans you already have, so you'll be

4:33

saving a ton of money. Listen, I wish it

4:35

was better than Opus, I really do, just

4:37

because they're encouraging the use of

4:38

the OAuth, but at the moment, at the

4:40

filming of this video, it just isn't.

4:42

But, if you can't afford the Opus API,

4:45

ChatGPT still works well, plug that in.

4:47

When it comes to Hermes, I currently

4:49

have ChatGPT plugged into that. If

4:51

you're on the $20 ChatGPT plan, it's

4:54

going to be hard for you to plug it into

4:55

both of these, cuz that's going to be a

4:56

lot of usage. So, I'd recommend going

4:59

with one of the cheaper plans out there,

5:02

like the GLMs of the world, if you have

5:04

ChatGPT already on your main Open Claw

5:07

agent. As an assistant, Hermes doesn't

5:09

need quite as much intelligence, so

5:11

you're fine getting away with one of

5:12

those cheaper AI plans for Hermes agent.

5:15

So, more expensive intelligence on the

5:17

left in Open Claw, cheaper intelligence

5:19

on the right in Hermes, since it's more

5:21

of your assistant, and Open Claw is more

5:22

of your main agent. Keep in mind, things

5:24

ebb and flow all the time. If you're

5:26

watching this video in 2027, things

5:29

might be completely different. The AI

5:30

models I may be using might be

5:31

completely different. Gemini might be

5:33

the best model at the moment. Hermes

5:35

might be a thousand times better than

5:37

Open Claw in 2027, so make sure to

5:39

subscribe and turn on notifications down

5:41

below. So, every time there's an update,

5:43

or a model changes, or a harness

5:44

changes, you'll know immediately, cuz

5:46

all I do is make amazing videos about

5:47

this stuff. I also do live boot camps

5:50

every single week in the Vibe Coding

5:52

Academy on Open Claw and Hermes Agent.

5:55

So, make sure to hit that down below and

5:56

join the number one community in AI.

5:59

I'll be doing a live boot camp this week

6:00

on these two tools as well and using

6:02

them together. So, first use case I'm

6:04

going to start out with is super simple.

6:06

Then, we're going to get to the most

6:07

advanced stuff. This has been probably

6:09

the most important use case of having a

6:11

two agent system that I've ever had. The

6:13

Open Claw team is incredible because

6:15

they release new big updates every

6:17

single day. They have like the most

6:19

amazing open source community behind

6:21

them. The issue is it's constantly

6:24

breaking every time I upgrade. Every

6:26

time I upgrade, there's something breaks

6:28

and I have to go and fix it. Which for a

6:29

lot of people they're experiencing this

6:31

and it's super stressful because your

6:33

best friend AI agent goes down, you

6:34

can't talk to it anymore. Like, this is

6:36

literally an example from last night. I

6:38

updated to the latest Open Claw and

6:41

boom, it just stopped responding. It

6:42

kept saying missing API key for Open AI.

6:44

Even though I'm not using Open AI for my

6:46

Open Claw agent at all. So, what I

6:48

immediately did is I went to my Hermes

6:50

agent and I said, "Hey, I'm having

6:52

issues with my Open Claw. Here's the

6:53

error I'm getting." It went in, it

6:56

looked around my Open Claw code, and it

6:59

fixed it for me. Instantly found the

7:00

issue, fixed it for me, and it was good

7:03

to go. My downtime in Open Claw has went

7:06

from like an hour every time I upgrade

7:09

to literally seconds if it ever breaks.

7:11

My Hermes agent and my Open Claw agent

7:13

know each other inside and out. So, any

7:15

time there's an issue with one or the

7:17

other, they go in and fix each other.

7:19

This is why it's so critical to have a

7:21

multi-agent approach is because these

7:24

are fragile, these harnesses. If one

7:26

piece of code gets messed up, the entire

7:29

thing breaks. So, if you're just relying

7:31

on one single agent, you have a single

7:34

point of failure. But, if you have two

7:36

agents going, it doesn't matter if one

7:38

or the other completely breaks. You have

7:40

backup ready to go in and fix each

7:42

other. So, first use case I know is

7:44

super simple, but it probably is the

7:46

most important out of them all, and

7:47

that's just having back-up. That's

7:49

having multiple points of failure. So,

7:51

as you're doing upgrades and updates to

7:53

each, the other can watch it and make

7:55

sure they keep performing well. The next

7:57

workflow I want to go over is how to

7:59

build things with each, and that is the

8:01

supervisor builder workflow. This is

8:05

relevant if you have a mission control,

8:07

if you build out any apps with your

8:08

agents, or anything like that. So, for

8:10

instance, right now I want to build out

8:12

a dashboard for my scanner system. For

8:15

those who aren't familiar with the

8:16

channel, I have a whole scanner system I

8:18

set up that's constantly scraping the

8:20

web at all times looking for business

8:23

opportunities for me where I can build

8:25

SaaS, or guides, or different things to

8:27

solve challenges online. It's a whole

8:29

very complex scanner system. I want to

8:32

build a dashboard for this system so I

8:34

can monitor all my scanners and see how

8:36

they're performing. This is where the

8:38

monitor worker workflow comes in. I'm

8:41

going to have Henry, my Open Claw

8:43

running on the best AI model Opus, come

8:46

up with a plan. Hermes is going to

8:48

execute on it, and then Henry will go

8:50

back, make sure it performed well, and

8:52

give feedback. This is a really great

8:54

system because as long as you have a

8:56

very high intelligence model and a lower

9:00

intelligence one, you don't need the

9:02

higher intelligence one doing

9:03

everything. As long as they're planning

9:05

and monitoring, you can have the cheaper

9:07

model do the execution, and you'll still

9:09

get really good results and save tons of

9:11

money. So, let me show you how this

9:12

works. So, I'm going to have Open Claw

9:14

build a plan around this. I'm going to

9:16

say, "I want to build a dashboard for

9:17

our scanner system. It should be a

9:18

Next.js app and show the scanners, their

9:20

status, and when the last run was. Can

9:22

you build a plan for this I can hand to

9:24

the other agent, please?" Henry, my Open

9:27

Claw powered by Opus 4 6, is going to go

9:29

and build this plan that we are then

9:31

going to hand to Hermes. There's another

9:33

step I'm going to show you right after

9:35

this, and that is the review step. Henry

9:38

is going to basically make sure Hermes

9:40

is going and doing the right thing. But,

9:41

let's first get this plan from Henry.

9:43

All right, there we go. Henry finished

9:45

the plan. We have this markdown file

9:47

right here, which is great. I'm going to

9:49

click that so we can open it up. Here we

9:51

go. Boom, look at this beautiful plan.

9:53

Wow.

9:54

This is a 256

9:56

line plan. Let's give this to Hermes

9:58

now. So, I put in the plan that Henry

10:02

built, and I put in a caption, "Hey, I

10:03

want to build a dashboard. Here is the

10:05

plan." And I'm going to hit send. And

10:07

now Hermes is going to get the plan and

10:09

actually start building it out for us.

10:11

Because it has that plan from Opus, it's

10:13

going to be done really, really well cuz

10:15

it has a really well-thought-out plan.

10:17

By the way, if you have an extra monitor

10:19

or something, the setup you see here, I

10:21

have up it all times. I have two

10:22

monitors, so I have Henry and Hermes up

10:24

on my second monitor at all times so I

10:26

can quickly go and chat with them.

10:28

Having these up at all times, always

10:30

visible, like out of the side of your

10:32

eye, makes it so you're a lot more

10:34

likely to use them. So, I highly

10:36

recommend, if you're doing this setup

10:38

and you're copying me here, keep up two

10:40

windows just like this. This is

10:41

Telegram, by the way, up on your second

10:43

monitor or wherever at all times. Just

10:45

you always remember to be using them.

10:47

All right, looks like it's done

10:48

building. Let's check it out. Let's see

10:49

what we got here. See how it looks. Oh,

10:52

wow, look at this. This is all built by

10:54

Hermes agent. Okay, so here's my scanner

10:57

dashboard. 12 of the 18 scanners

10:59

healthy. Six are erroring out right now.

11:02

And then we can see each of the

11:03

scanners. This is great. I can see the

11:05

last run, the next run, how long they've

11:07

been running for. This is really, really

11:09

cool. I wonder what happens. Can I click

11:10

it and something happens? Okay, I click

11:12

it. It's loading. I'm going to imagine

11:14

it's going to show me the runs and what

11:15

it discovered and things like that. Oh,

11:17

wow, boom. I can see it. The last run,

11:19

the run history, everything in it. I

11:21

love it. That's really, really sick. So,

11:23

it did a really good job, and it looks

11:26

very nice. Now that we have the code

11:28

built, let's go back to our open claw

11:30

because again, we want to use the

11:32

smarter model as the checker, make sure

11:35

things went well, almost like a Ralph

11:36

loop. And let's say, "Check out the code

11:39

here and let me know what you think."

11:43

And I'm going to hit enter. Now, Henry

11:44

will go and check out all the work on

11:46

Hermes. If there's improvements needed

11:47

to be made, open claw will let me know.

11:49

This is how you both get better

11:52

performance and also save tons of money

11:54

because your more expensive agents

11:56

aren't doing the work. All right, and

11:57

here's the view. This is solid work,

11:59

builds clean and well-structured. Here's

12:00

my take. Looks like it's pretty good.

12:02

Has some notes for improvement, and we

12:04

can give that back to Hermes now to fix

12:06

that. But now you can see the system in

12:08

action, and it's so good. Use case

12:10

number two is the monitor system. I

12:13

regularly schedule cron jobs with Hermes

12:16

to check on things that Henry is doing.

12:19

The reason why I can do this is because

12:21

Hermes is cheaper to run because I'm

12:23

using cheaper models and it's a

12:24

lightweight agent. I can have it

12:27

constantly monitoring things Henry has

12:29

built out. So, for instance, those

12:31

scanners that Henry originally built, I

12:33

have Hermes go in and every 2 hours just

12:36

look into them. So, kind of like this

12:37

dashboard system we just built out, I

12:40

had it running on cron jobs before this

12:42

in Hermes, and it would go, see the

12:44

state of all the scanners, give me

12:46

advice on what's working and what isn't,

12:48

and just had this do it every 2 hours

12:50

and alert me when things were wrong.

12:52

Because Hermes is lightweight and

12:54

cheaper, you can have it doing cron jobs

12:57

a lot more often, checking in on other

12:59

things, checking in on what Henry is

13:02

doing, or even checking in on social

13:03

media, your emails, whatever it is.

13:05

Hermes acts as a way better monitor than

13:09

Henry because of its lightweight and

13:11

cheapness. So, if you have an app you

13:13

built with open claw, or you just have

13:16

some sort of process your open claw

13:18

does, setting Hermes up as kind of a

13:21

hallway monitor that's just checking in

13:23

every few hours to make sure it's going

13:25

well, and alerting you if something goes

13:27

wrong is a really powerful way to be

13:29

using Hermes just because as an

13:31

assistant it's just really good at these

13:33

types of tasks. Again, it's all about

13:35

checks and balances, them checking each

13:38

other's work, making sure it's going

13:39

well. It's just increasing the

13:40

reliability and performance of

13:42

everything your agents are doing. The

13:44

third use case I want to go over is a

13:47

shared memory workspace. What does that

13:49

mean? That basically means you have a

13:51

custom memory system that both agents

13:54

use where they can share information

13:56

with each other. This dramatically

13:58

improves the memory of your agents

14:01

because now everything your agents do

14:03

separately goes to one centralized space

14:07

that helps improve the memory of all

14:09

your agents and just make them all

14:10

better. The more mistakes each agent

14:13

makes, the more information that goes to

14:15

the shared memory system and improves

14:17

all your agents overall. Let me show you

14:19

how this works. So in Obsidian, I have a

14:22

few different folders here you can see

14:23

over on the left-hand side. You can see

14:25

an agent Hermes folder, an agent Open

14:28

Claw folder, and an agent shared folder.

14:30

In the individual agent Open Claw and

14:32

agent Hermes folders are all their

14:35

memory. So everything they're doing,

14:36

their daily logs, the mistakes they're

14:38

making, and any working context they

14:40

have. This is great for improving each

14:42

individual agent's memory. But here's

14:44

where it gets good is the agent shared

14:47

folder. Now they have a shared workspace

14:50

that they're both checking in on to see

14:52

what each other are doing, lessons

14:54

they've learned, decisions they've made,

14:56

and it helps them improve each other.

14:58

This is where like the recursive

15:00

self-improvement comes in is when one

15:02

agent learns something or makes a

15:04

mistake or gets better, it's able to

15:05

share all that information with the

15:07

other agents as well. By having two or

15:09

more agents doing work, they're now

15:11

improving each other even faster. As you

15:14

can see, I was planning this YouTube

15:15

video this morning with my Hermes agent

15:19

and it put the entire plan for this

15:21

YouTube video inside the shared folders

15:23

so that I can then go to my OpenClaw and

15:25

say, "Hey, what do you think about this?

15:27

How would we improve this YouTube

15:28

script?" And things like that.

15:30

Everything is stored in the shared space

15:32

so that they can improve each other.

15:33

This is a much better memory system than

15:36

having just a bunch of separate agents

15:38

working and not talking to each other.

15:40

This is all done in Obsidian, which is a

15:42

completely free app you can download. I

15:44

have a guide on Obsidian. I'll link to

15:46

that down below on using Obsidian with

15:48

AI agents. Make sure to check that out

15:50

right after this if you want guidance on

15:52

setting up the shared memory system as

15:54

well. Just as a side note, too, for all

15:56

of these, you can just copy and paste

15:59

this YouTube video or hit share down

16:01

below and then copy link and then give

16:03

it to your agents and say, "Hey, check

16:05

out this YouTube video and set all this

16:06

stuff up." It'll actually generate a

16:08

transcript for you, look through the

16:10

transcript, pull out all the learnings,

16:12

and set this up for you. So, super easy

16:14

to implement anything I share with you

16:16

in any of these videos. Just take the

16:17

link to the video and give it to your

16:19

OpenClaw or Hermes and it will set it up

16:20

for you. So, we talked about the planner

16:23

builder system. We talked about the kind

16:25

of hallway monitor system where Hermes

16:27

is checking in on OpenClaw, making sure

16:29

things are running well. We talked about

16:32

the backup system where if you upgrade

16:34

and one thing breaks, they can get each

16:36

other's backs. We talked about the

16:37

shared memory system. These are core

16:41

infrastructure use cases where if you

16:43

implement these, everything just gets

16:46

better and improves. Your memory stops

16:48

going to crap, your performance gets

16:50

better, you save money, things break

16:52

less, everything just improves. So,

16:54

implement these core structures into

16:57

your multi-agent system and things will

16:59

be great. I'll put links down below for

17:01

both OpenClaw and Hermes agents so you

17:03

can get them installed and use them

17:05

together. Leave a like, subscribe, and

17:07

turn notifications if you got anything

17:08

out of this. And again, I do live

17:10

bootcamps every week on Hermes and

17:12

OpenClaw. That is in the Vibe Coding

17:14

Academy. Link for that down below. Make

17:16

sure to join that now if you want to

17:17

learn a ton more about AI and the most

17:19

important cutting-edge skills on planet

17:21

Earth. I hope this was helpful and I'll

17:23

see you in the next video.

Interactive Summary

The video explains the benefits of using a two-agent AI system, specifically combining Open Claw and Hermes Agent, to enhance productivity and reliability. By using Open Claw as a main, stable agent (powered by Opus) and Hermes as a lightweight assistant, users can achieve better task distribution, cost savings, and near-zero downtime. The speaker details key workflows including using them as mutual backups, a planner-builder-checker system, a cron-job monitor, and a shared memory architecture using Obsidian.

Suggested questions

4 ready-made prompts