HomeVideos

ClawdBot Full Tutorial for Beginners: How to Use & Set up ClawdBot (Openclaw)

Now Playing

ClawdBot Full Tutorial for Beginners: How to Use & Set up ClawdBot (Openclaw)

Transcript

387 segments

0:00

Claudebot is changing the game when it

0:02

comes to AI assistance. Most AI tools

0:05

today live in a browser. You open a tab,

0:08

you ask a question, you get an answer,

0:10

and once you close that tab, everything

0:12

just kind of disappears. They're useful,

0:14

but they don't really feel like

0:16

assistants. And that's exactly the

0:18

problem Cloudbot is trying to solve.

0:20

Unlike typical AI chat bots, Claudebot

0:22

is a self-hosted AI assistant that runs

0:25

directly on your computer. It connects

0:27

to powerful AI models like claude or

0:30

chatgypt for intelligence while the

0:32

agent itself lives locally on your PC.

0:35

And this means it can actually do things

0:36

for you like write code, create files,

0:39

browse the web, and integrate with

0:41

platforms like Telegram, Slack, and

0:43

Discord. So, in this complete beginners

0:46

tutorial, I'm going to walk you through

0:48

everything that you would need to know

0:51

about Claudebot. We'll cover what makes

0:53

it special, whether you need specific

0:55

hardware, the costs involved, and most

0:58

importantly, I'll show you exactly how

1:00

to set it up step by step from getting

1:03

your API keys to having your first

1:05

conversation through Telegram. So, by

1:07

the end of this video, you are going to

1:09

have your own local AI assistant running

1:11

on your own computer, ready to help you

1:14

with your daily tasks. So, let's go

1:15

ahead and dive in and get Cloudbot set

1:17

up together. So, what exactly is

1:20

Claudebot? Most AI tools today live in a

1:23

browser. Again, you open a tab, ask a

1:25

question, get an answer, and once you

1:27

close that tab, everything just kind of

1:29

disappears. They are useful, but they

1:31

don't really feel like assistance at

1:33

all. They feel more like tools that you

1:35

have to keep reopening over and over

1:37

again. And that's exactly the problem

1:39

Claudebot is trying to solve. Claudebot

1:42

is a self-hosted AI assistant that runs

1:44

directly on your own computer. So

1:46

instead of living inside a web

1:48

interface, it just connects to dedicated

1:50

AI models like Claude or Chat GPT for

1:53

its intelligence while the agent itself

1:55

lives locally on your PC. What makes

1:58

that interesting is what it can actually

2:00

do. And Claudebot isn't just limited to

2:03

chat only. It can connect to Telegram,

2:05

Slack, Discord, Google even, and of

2:07

course other tools depending on how you

2:09

set it up. You can use it to write code,

2:11

build applications, do research, create

2:14

lists, or handle tasks that you would

2:17

normally bounce between multiple labs

2:19

for. Because it's running locally,

2:21

everything stays on your machine. Your

2:23

conversations, your files, your context,

2:26

none of that is sitting on some random

2:28

third-party server. And that's the real

2:30

advantage here. So, with the right

2:33

configuration, Cloudbot feels way less

2:35

like a typical AI chatbot and a lot more

2:38

like an actual assistant that

2:40

understands your workflow and can

2:41

interact with your computer. You can

2:44

have it help build full projects, manage

2:47

research, or automate things in the

2:49

background all while chatting with it

2:51

through Telegram or whatever platform

2:54

that you prefer. So, what are the main

2:56

features of Cloudbot? When people hear

2:59

AI assistant, they usually imagine

3:02

something that understands their

3:04

workflow and helps behind the scenes.

3:06

[music] In reality, a lot of the tools

3:08

stop at conversation and don't go much

3:11

further than that. Once you start using

3:13

Clawbot, though, it will be very much

3:15

obvious that it's more than just a

3:18

chatbot. It's designed to actually do

3:20

things for you and not just respond to

3:23

prompts. At a basic level, Claudebot can

3:26

execute commands directly on your

3:28

computer. It can create files, write

3:31

code, and even browse the web if you've

3:33

configured it properly. And that opens

3:36

the door to automating tasks and

3:38

handling real work instead of just

3:40

getting text responses. [music]

3:42

It also integrates with messaging

3:44

platforms like Telegram and Slack and

3:47

Discord. So, you're not locked in to a

3:49

single interface. You can talk to it

3:52

from the tools you already use every

3:54

day, which makes it feel a lot more

3:56

natural to work with. One of the more

3:58

powerful features is memory. Claudebot

4:01

can remember past conversations and your

4:04

preferences over time. So, the more that

4:06

you use it, the better it starts to

4:08

understand how you work and what you

4:10

usually need help with. On top of that,

4:13

there's a web dashboard that gives you a

4:16

full view of your chat history, the bot

4:18

status, and all of your settings. So you

4:20

don't need to dig through config files

4:23

unless you actually want to. Everything

4:25

important is visible in one place.

4:28

Cloudbot also supports multiple AI

4:30

models. So if you have API keys for both

4:33

cloud and chat GBT, you can just switch

4:35

between them depending on what you need

4:37

at the moment, which is great if you

4:40

prefer one model for certain tasks over

4:42

another. And finally, file creation is a

4:45

big one here. Cloudbot can generate

4:47

documents, spreadsheets, and

4:49

presentations and other files too,

4:51

directly from your requests without you

4:53

having to open a single application. Do

4:56

you need a Mac Mini or a Mac device? A

4:59

question that comes up a lot is whether

5:01

you need a Mac Mini or even a Mac at all

5:03

to run Cloudbot. And the short answer is

5:06

nope. You can run Claudebot or Multibbot

5:09

on pretty much any modern device,

5:11

whether you're on a Mac, Windows, or

5:13

Linux even. There's no special hardware

5:16

requirements and no need to dedicate a

5:18

machine just for this. It also doesn't

5:21

use a ton of system resources because

5:23

you're not running a full language model

5:25

locally. Claudebot just connects to

5:27

existing AI models from providers like

5:29

Anthropic or OpenAI. So your computer is

5:33

mainly just running the agent itself.

5:35

Are there costs involved? So when it

5:38

comes to cost, Cloudbot itself is

5:40

completely free all to use. You're not

5:42

paying for the software or the agent.

5:44

What you do need though is an API key

5:47

from an AI provider like Anthropic or

5:49

OpenAI. And that is where any cost comes

5:52

from. How much you end up paying really

5:55

does depend on how often you use it and

5:58

which model you choose as your default.

6:00

More powerful or newer models of course

6:03

will cost more per request, but they

6:05

also tend to give better results. So

6:07

there is a trade-off there. Lower tier

6:10

models are cheaper, but the experience

6:12

can feel a bit more limited. On top of

6:14

that, some of Cloudbot's advanced

6:16

features really do rely on additional

6:18

thirdparty services, which means extra

6:21

API keys and potentially extra cost. So,

6:24

while Cloudbot itself is free, the total

6:26

cost can vary quite a bit depending on

6:28

how you configure it and how heavily you

6:30

use it. So, how difficult is it to set

6:33

up Cloudbot? So, let's be real here. The

6:35

setup isn't completely plugandplay.

6:38

Sorry. Especially if you're not used to

6:40

working with the terminal or dealing

6:41

with API keys. There are a few moving

6:44

parts and it can feel a bit intimidating

6:46

at first. You'll need to install things

6:48

like Node.js, add your API keys, and set

6:51

up whichever messaging platform you want

6:53

to use, like creating a Telegram bot.

6:56

Some of that involves running terminal

6:59

commands and in a few cases editing JSON

7:02

files, which can be unfamiliar territory

7:04

if you're not a developer. The good

7:07

news, though, is that once everything is

7:09

configured properly, Cloudbot runs very

7:11

smoothly, and you rarely need to touch

7:13

the settings again. It's mostly just a

7:16

one-time setup. The documentation

7:18

definitely helps, but you may still run

7:20

into a few bugs or some rough edges

7:22

along the way, especially around API

7:25

keys and gateway tokens. But if you're

7:28

comfortable following guides and using

7:30

basic terminal commands, well, you

7:33

should be able to get everything up and

7:35

running in about 30 to 60 minutes. The

7:38

hardest part here is usually just

7:40

getting all the keys set up correctly

7:42

and making sure your messaging platform

7:45

connects properly. So, before we install

7:48

anything, we do need to decide which AI

7:50

model Claudebot is going to use. To do

7:52

that, we'll need an API key from an AI

7:55

provider. I'm going to use Claude, but

7:57

you can follow the same process with

7:59

other supported providers if you do

8:01

prefer. Claudebot supports multiple

8:04

providers. So, if you'd rather use, say,

8:06

OpenAI instead, you can just grab an API

8:09

key from OpenAI and follow along with

8:11

that. And if you're going with Claude,

8:13

then head over to platform.claw.com

8:17

and choose the option to get an API key.

8:19

From here, you'll be asked to give the

8:21

key a name. And once it's created, all

8:23

you got to do is just copy it. We'll be

8:25

pasting this into Cloudbot during the

8:27

setup in the next step. Now that we've

8:29

got our API key, the next step is

8:31

actually just installing Claudebot. And

8:34

the process itself is pretty

8:35

straightforward. On the CloudBot website

8:38

here, you'll see a single line install

8:40

command. Just copy that, open up your

8:42

terminal, and paste it in. Once you run

8:45

it, the installation will start

8:46

automatically. And at this point, you

8:48

just let it do its thing. If Node.js JS

8:51

or Git isn't already installed on your

8:53

system, the installer will take care of

8:55

that for you. In my case here, I already

8:58

had everything set up since I am a bit

9:00

of a developing developer, if you could

9:02

say that. So, it's really just

9:03

installing CloudBot itself. And once

9:05

that's done, you just wait for the

9:07

installation to finish before moving on

9:08

to the configuration steps. Once the

9:11

installation finishes, Claudebot will

9:13

automatically jump straight into the

9:15

configuration process. Here, you don't

9:18

have to manually start anything. It just

9:20

picks up right where the install leaves

9:22

off. Early on, you'll see a prompt that

9:24

says something along the lines of, "I

9:27

understand this is powerful and

9:29

inherently risky. Continue." So, go

9:31

ahead and say yes here so you can move

9:34

forward with the setup. Next, you'll be

9:36

asked to choose an onboarding mode. So,

9:38

for this setup in this video, go with

9:40

quick start. It's the fastest and the

9:42

easiest option and lets you get

9:44

everything up and running without having

9:46

to tweak a bunch of settings right away.

9:49

After that, you're going to be asked to

9:51

choose your AI provider. This is where

9:53

you decide which model Claudebot will

9:56

use for its intelligence. Since we

9:58

grabbed a Claude API key earlier, I'm

10:01

going to select Anthropic here. Just

10:03

keep in mind this isn't a permanent

10:05

decision. You can use any supported

10:07

provider that you want and it really

10:09

comes down to personal preference. After

10:12

selecting Enthropic, choose Enthropic

10:14

API key and paste in the key you copied

10:17

earlier. After that's set, Cladbot will

10:19

ask you to pick a default model. There

10:22

are quite a few models available, so

10:24

this part is really about balance. In my

10:27

case, I went with Sonnet 4.0 because

10:29

it's efficient and still has a fairly

10:31

recent knowledge base. More powerful or

10:34

newer models will generally give better

10:36

results, but they will also burn through

10:38

your credits a lot faster, and that's

10:40

something to keep in mind here. The good

10:43

thing is you're not locked into this

10:45

choice. You can always switch models

10:47

later if you just want to. Just be aware

10:50

that each model has its own personality,

10:52

so to speak. So, if you change it down

10:54

the line, the responses might be a

10:56

little different. So, after that initial

10:58

setup in the terminal, the next step is

11:00

moving the conversation over to

11:02

Telegram. Open up the Telegram bot that

11:04

we just created and send the

11:06

forward/start command to kick things

11:08

off. After a short moment, Claudebot

11:11

should respond, letting you know that

11:13

the connection is working and that it's

11:15

ready to chat with you. Once you see

11:17

that message, you're officially talking

11:20

to your own local AI through Telegram.

11:22

And from here, you can start having real

11:25

conversations with it. I'm going to ask

11:27

it a few questions, bring up some

11:30

general topics, and then give it more

11:32

information about myself and what I do.

11:34

And you can see that it responds

11:36

properly and keeps the context of the

11:38

conversation. This part is actually

11:40

pretty important because the more you

11:42

talk to Claudebot and give it context

11:45

about how you work, the better it gets

11:47

at understanding you. And just like with

11:49

training AI models, giving it more

11:52

information over time helps it build

11:54

better memory and respond in a way that

11:56

fits your workflow. Also, let's go into

12:00

the Claudebot dashboard here where you

12:02

can see the chat history showing up in

12:05

real time. Now, that's a good way to

12:07

confirm that everything is connected

12:09

correctly and that's all working as

12:11

expected. After setting everything up

12:13

and chatting with Cloudbot just for a

12:15

little bit, you might start wondering,

12:17

huh, what else can it actually do? Well,

12:20

Telegram is a great starting point, but

12:21

it's really just the beginning here.

12:24

Cloudbot isn't limited to Telegram only.

12:26

It can also integrate with other

12:28

platforms like Slack, Discord, and

12:30

additional messaging tools. You just

12:32

need to configure them in the settings.

12:34

Once set up, you can interact with the

12:37

same local AI from multiple places. It

12:40

can also interact directly with your

12:42

computer. Cloudbot can run bash

12:44

commands, create files, and help

12:46

automate tasks, which makes it

12:48

especially useful for things like

12:50

coding, file management, or repetitive

12:53

workflows. So, if you connect a web

12:55

search provider like say Brave Search,

12:58

Cloudbot can pull in up-to-date

13:00

information from the web instead of

13:02

relying only on its training data.

13:04

That's really useful when you need

13:06

current information or just some quick

13:08

research. Memory is another big part of

13:10

how Cloudbot works. It remembers past

13:13

conversations and can reference them

13:16

later. So, the more you do actually talk

13:18

to it, the better it understands your

13:20

preferences and how you work. On top of

13:22

all of that, it can also write and run

13:25

code directly. Why not? Of course,

13:26

[music] generate documents,

13:28

spreadsheets, presentations, and manage

13:30

files, all from chat. You can ask it to

13:33

create reports, organize your data, or

13:35

draft documents without opening any

13:37

other apps. You can also customize how

13:39

Cloudbot behaves, what it calls itself,

13:42

and how it responds. So, it does feel

13:44

more tailored to your workflow instead

13:47

of a generic assistant. Also, there's a

13:50

built-in web dashboard at localhost

13:52

col18789

13:54

where you can see your full chat

13:55

history, monitor the bot status, and

13:58

manage settings without ever touching

14:00

configuration files. And finally,

14:02

everything is privacy focused. Because

14:05

CloudBot runs locally on your machine

14:07

only and connects directly to the AI

14:09

provers API, there's no routing your

14:12

conversations through third-party

14:14

servers. At the end of the day,

14:16

Claudebot is basically your own local AI

14:19

powerhouse. Something that you can talk

14:21

to from your phone or your desktop, but

14:24

that actually lives on your machine and

14:26

works the way you want it to. And that's

14:30

pretty much it. That's CloudBot in a

14:32

nutshell. It's a local AI assistant that

14:34

actually works with you, not just talks

14:37

to you. We focused on the core setup

14:39

here so you can get up and running

14:40

without over complicating things. But

14:43

there is a lot more you can build on top

14:45

of this once you are comfortable. Thanks

14:48

for watching and investing your time

14:49

with me today. I'll see you at the next

14:51

one.

Interactive Summary

This video serves as a comprehensive beginner's guide to Claudebot, a self-hosted, privacy-focused AI assistant that runs locally on your computer. The tutorial explains how Claudebot differs from browser-based AI tools by executing local commands, managing files, and integrating with platforms like Telegram, Slack, and Discord. It also outlines the hardware compatibility, API costs, setup difficulty, and the step-by-step configuration process to get your own local AI assistant up and running.

Suggested questions

4 ready-made prompts