HomeVideos

Claude Channels Just Dropped, And It Kills OpenClaw (Again)

Now Playing

Claude Channels Just Dropped, And It Kills OpenClaw (Again)

Transcript

749 segments

0:00

So, Claude Code just released channels,

0:01

which is a Telegram and Discord

0:03

integration that lets you text your

0:04

agents the same way that you text other

0:06

human beings every day. And all I could

0:08

think about when I saw this was, "Man,

0:10

Anthropic really doesn't like Open

0:11

Claude." So, in this video, I'm going to

0:12

show you a quick demo. Then, I'm going

0:13

to run you guys through how it all works

0:14

under the hood before showing you how

0:16

you can set it up on your end. And at

0:17

the end, I'll also chat a little bit

0:19

about what I think this personally means

0:20

for the Open Claude debacle. Okay, so I

0:22

have two things on the screen here. The

0:24

first is I have my Telegram chat, and

0:26

this is actually running locally on my

0:27

computer in the exact same way that,

0:29

say, Open Claude might be running

0:31

locally on, you know, a Mac Mini or a

0:33

VPS. I just have an open chat with

0:35

Telegram right over here. And then on

0:37

the right-hand side, I actually have an

0:39

app that allows me to mirror the screen

0:41

of my iPhone, so you guys could see

0:42

everything that I'm doing in real time,

0:43

just for simplicity. So, I had a

0:45

conversation before with it, and I just

0:47

asked it to give me a big wall of text

0:49

that I could use to push up the previous

0:51

conversation, just that I could show you

0:52

guys how simple it is. If I type hey

0:55

over here on Telegram, what ends up

0:56

occurring is my Claude Code channel

0:59

plugin immediately gets a message from

1:01

my Telegram app. And then it does two

1:03

things. One, it gets the message and

1:05

accomplishes whatever feature or task

1:07

that I asked it to do. And then it also

1:09

updates the local conversation history

1:11

with just a description of what went on.

1:13

And so, on the Telegram side, you know,

1:15

I see, "Hey, hey, what's up? How's it

1:17

going?" So on and so forth. And over

1:18

here, I see that, you know, our Telegram

1:20

plugin ran. What did it do? Well, I just

1:22

replied to your Telegram message with

1:24

the incoming query of, "Hey."

1:26

And so, in this way, you actually get a

1:26

fair amount of accountability and

1:27

interpretability, which is nice. It's

1:29

not just a one-to-one one log of like

1:30

everything you said to it. Um, you also

1:32

additionally get kind of like a thinking

1:34

and reasoning layer. But anyway, let's

1:35

say I'm out and about, and, you know, I

1:37

actually have a task I want to get done,

1:38

some economically valuable work. And in

1:40

this case, you know, I'm making a big

1:41

course on Claude Code, and I saw a

1:43

thumbnail that looked like this. Well, I

1:45

have a skill that allows me to repurpose

1:47

thumbnails that I see in the wild, and

1:49

then take advantage of like the good

1:50

parts, while also inserting myself in

1:52

there and making some changes. So, I get

1:54

the URL over here. I just go on my phone

1:57

to Telegram and then I say, "Hey,

1:59

replace the man in this thumbnail with

2:00

me. Then make the following changes.

2:03

Change the text, you know, replace the

2:05

flags with the Claude logo, change the

2:06

colors, and so on and so forth."

2:08

What you see occurs locally is not only

2:10

do we have the message come in, which is

2:12

up here, we also have the skill, okay,

2:16

that it connected to, which is now

2:17

locally on my computer, I'm sort of

2:19

connected and and in that way I'm now

2:20

designing the thumbnail. Now what it's

2:22

doing is it's upscaling the thumbnails

2:24

according to my specifications in the

2:25

skill. You can see that it's now

2:26

actually sending me over each of these

2:28

thumbnails onto my phone, so I'm just

2:30

taking a look at them right now. This

2:31

one here in particular is probably the

2:32

most me and that's more or less all I

2:34

really wanted from this. I just wanted

2:36

some sort of inspiration that I could

2:37

use to, you know, quickly design a

2:38

thumbnail while I'm on the go. But it

2:40

doesn't just stop at Telegram, they've

2:41

also added Discord support for all you

2:43

Gen Z'ers out there. So, now what I have

2:45

is I have the plugin Discord at Claude

2:47

Plugins Official running and then I have

2:49

on the right-hand side a Discord chat on

2:50

my phone. And let's say I want to run

2:52

another some economically valuable task,

2:54

whatever it is. I'm going to say,

2:55

"Scrape me 100 leads from Appify

2:57

dentists in California." The title

2:58

should be stuff like dentist practice

3:00

manager and so on and so on and so

3:01

forth.

3:02

What it's doing now is it's actually

3:03

going to go and then run my, you know,

3:05

Appify scraping skill. A few seconds

3:07

later, it scrapes the leads. It's now

3:09

going to do a little bit of running

3:10

through them. Looks like 98 of them have

3:12

phone numbers and now that it's created

3:13

a CSV, what it's going to do is send it

3:15

over to me so that I can open it on my

3:17

phone. I then have this CSV file open

3:19

here, which I can click on and then

3:21

depending on my own workflow, I can open

3:22

this up on a Google Sheet or whatever,

3:24

start giving people some rings. Okay, as

3:26

you guys could see, very simple and very

3:27

straightforward once you actually have

3:28

it set up. It has all of the benefits of

3:30

the usual Claude code tooling, all of

3:33

the skills that you might have set up

3:34

locally on your computer as well. And as

3:36

long as your computer doesn't go to

3:37

sleep or anything like that, which is

3:39

pretty easy to do, I can run you guys

3:40

through a couple ways to do that. Um it

3:42

will essentially always be listening on

3:44

the same sorts of apps that you just

3:45

used to talk to people every day. And,

3:47

you know, to be honest, this is the main

3:49

reason why I think that like Open Claw,

3:51

Claude Bot, Molt Bot, all these tools

3:53

like picked off so much just because

3:55

we're now talking to agents using the

3:56

exact same interfaces we talk to people,

3:58

getting some economically valuable work

3:59

done, and it's just more convenient for

4:01

us. So, let me run you through all this

4:03

stuff in a sec. So, in terms of how to

4:04

set this up, it's right over here at

4:06

code.claud.com/docs/en/channels.

4:09

And you can even communicate with their

4:10

assistant over here on the right-hand

4:12

side if you wanted to. But, uh they have

4:14

a new page set up that says push events

4:15

into a running session with channels.

4:17

And that's basically what we are doing.

4:18

You know, they're trying obviously not

4:20

to just say, "Hey, we replicated all the

4:21

functionality of open claw or whatever."

4:23

But, to be honest, that's more or less

4:25

what what we are doing here. We're

4:26

having a conversation with our agent.

4:28

It's the exact same sort of conversation

4:29

that we might be having on our computer.

4:31

It's just now we also have a stream that

4:32

we can funnel through, you know, a

4:34

messaging app and so on and so forth.

4:36

So, there are a couple right now,

4:38

Telegram and Discord being the main

4:39

ones. I should note that this came out

4:41

just a few hours ago. So, there'll

4:42

probably be significantly more over the

4:43

coming uh weeks and months. Um but, it's

4:45

pretty straightforward. Basically, on

4:46

Telegram, you just get a little access

4:47

code. You do the same thing on Discord,

4:49

although you have to you know, have to

4:50

set up an app, which I'll show you guys

4:51

how to do. And then you guys could have

4:53

a back-and-forth conversation with it in

4:54

a very straightforward way. The reason

4:56

I'm on this page is because of this

4:57

section right here, security. Now, if

4:59

you guys know, uh I've made a bunch of

5:01

videos on like open claw and then having

5:03

like phone conversation style things

5:05

with agents before. And usually there's

5:07

some glaring security issues as a result

5:09

of it. Um the way that this plugin works

5:11

is obviously we already have the

5:12

built-in Claude code tooling, which has

5:13

some security out of the box. But, every

5:16

approved channel plugin has what's

5:17

called a sender allow list. So, only

5:19

specific IDs that you have already added

5:21

ahead of time can push messages.

5:23

Everything else gets silently dropped.

5:25

Um in this way, you still get access to,

5:27

as mentioned, all of your own tooling.

5:28

You don't have to like set all this

5:29

stuff up again. Um but, you also get to

5:31

do this at the exact same level of

5:32

security you previously had in Claude

5:34

code, which was hopefully quite high

5:35

already. So, that's it. No real magic

5:37

here. Let me show you how to get this on

5:38

your phone. Um just like before, I'm

5:39

going to be doing this on my iPhone

5:41

mirroring app, but everything that I do

5:42

there is the exact same as what you will

5:44

see on your device, whether it's an

5:46

Android or an iPhone. Okay, so first to

5:48

start, head over to Telegram. And what

5:49

you'll have to do is you'll have to send

5:50

a message to this person here called Bot

5:53

Father. Bot Father is basically the de

5:56

facto app that allows you to create new

5:58

apps anytime you want. And if you just

5:59

click that open button, you'll be taken

6:01

to page that looks like this. You can

6:02

see that I've set up a couple of Claude

6:04

bots already. This is when I was testing

6:06

out Nemo Claude, which I thought would

6:08

have been a pretty good competitor to

6:09

this, but in reality, I think this is

6:11

way better. This is the chat that we

6:13

were just having a conversation with a

6:15

moment ago. Then just go over to create

6:16

a new bot, and then you can just add,

6:18

you know, whatever details you want

6:19

here. So, Claude

6:21

demo bot. And then I'll just call it

6:23

Claude demo bot. You have to make sure

6:25

that whatever you're creating is

6:26

appended with the three-letter word bot.

6:29

Okay, you can also add a profile picture

6:30

and stuff like that. I'm not really

6:31

super worried about that, so it's not a

6:32

big deal.

6:33

Here you'll also have this little

6:35

invisible, you know, hidden text

6:37

feature. I'm just going to click copy.

6:39

And now basically what I have is I have

6:40

my bot token, which is required in order

6:42

for me to set up the next step. Once

6:43

you're done with that at any time, you

6:44

can just go {slash} my bots to actually

6:47

get the list of bots that you have, and

6:49

then you can just click on the specific

6:50

one.

6:51

When you click on it, a little {slash}

6:52

start window will be opened just like

6:54

that. And now you sort of have a

6:55

conversation window open. I should note

6:57

that if you send it a message at this

6:58

point, nothing will happen. We actually

6:59

have to set up the plugin on the Claude

7:01

code end as well. So, from there, I'm

7:02

going to open up Claude code inside of

7:04

Anti-Gravity, which is my preferred sort

7:06

of development interface. If you guys

7:08

don't know anything about Anti-Gravity

7:10

or never seen the screen before, it's

7:11

actually really easy to figure out, and

7:13

I walk you all through it through a

7:14

four-hour in-depth tutorial. I'll show

7:16

you guys like the buttons and what

7:17

literally every little section of this

7:19

screen means. Just check that link that

7:21

I posted in the top right-hand corner a

7:22

second ago. Now, in order for us to set

7:24

this plugin up, we'll have to go {slash}

7:26

terminal, and so actually open Claude in

7:28

the terminal. Um some of you guys may

7:29

already have this set up, but obviously

7:31

I use the GUI just for demo versions.

7:33

I'm going to click maximize panel size

7:35

in the right-hand side. And now what I

7:36

need to do is I need to install the

7:37

plugin for Telegram. So, that's pretty

7:39

easy you do. You just have to go {slash}

7:42

plugin install telegram at

7:44

claw-plugins-official.

7:46

Now, it's going to ask you where you

7:47

want to install it. In my case, I want

7:49

to install for me the user scope. The

7:51

user scope essentially means all

7:53

workspaces across all different projects

7:55

on my computer are going to have access

7:57

to telegram if I need to.

7:59

Once we're done, we just go reload

8:00

plugins. Then we're basically now we

8:02

we've now activated it, which is cool.

8:04

Okay, after you're done with that, just

8:05

exit out of the session. You can just

8:07

hold control C and just press that a

8:09

couple times. I'm just going to clear so

8:11

that we could see this full screen.

8:12

Okay, after that, you can just type

8:14

{slash} clear to get you back up to the

8:15

very top. And then I'm just going to

8:17

paste in {slash} telegram

8:19

colon configure.

8:21

This is going to look purple, which

8:23

means that it's now being recognized as

8:24

an actual command. And then over here,

8:26

you're just going to insert that token

8:27

that you copied from Bot Father earlier.

8:29

If it doesn't appear purple, you may

8:31

just have to restart Claude Code in

8:32

order for the plugin library to

8:34

initialize.

8:35

Once you're done with that, the

8:36

configuration script will basically

8:37

create a new channel allow list or

8:40

policy. And now what you can do is you

8:41

can just turn this off and then turn

8:43

this back on again. So, I'm going to use

8:45

control C and I'll press that twice.

8:48

And now I'm actually out of my Claude

8:50

and I'm back in like my terminal. And

8:52

there's a different set of commands

8:53

here, but if you just type clear,

8:55

they'll basically bump you all the way

8:56

up to the top. You'll have a little bit

8:57

more room and then we can continue.

8:58

Okay, last but not least, we actually

9:00

just need to launch this. And the way

9:01

you do so with Claude Code's channel

9:03

plugin is you use Claude space {dash}

9:06

{dash} channels space plugin colon

9:09

telegram at claw-plugins-official.

9:12

So, when you do this, you'll actually be

9:14

connected now to your bot from a moment

9:16

ago. And the last thing we have to do is

9:18

we just have to send a brief message

9:20

over to our bot to 100% verify that the

9:23

connection is started. So, I'm going to

9:24

go back here.

9:25

I'm just going to type in hey.

9:27

When I do this, as you guys could see,

9:29

we now actually have the message coming

9:30

through on this side. So, boom. Hey,

9:32

what's up? How's it going?

9:34

Awesome. Run my scrape

9:37

no Appify lead skill for 50 HVAC people

9:41

in Texas. And now we're having a

9:43

conversation with it, just like you

9:44

would have with anything else. Okay,

9:45

Discord is pretty straightforward as

9:47

well. So, I actually already have this

9:49

app set up. I'm just going to create a

9:50

new one. Head over to

9:51

discord.com/developers/applications

9:53

and just type new app. And then, what

9:55

you're going to want to do is, I don't

9:56

know, I'll just say

9:59

not genuine app. It'll ask you to

10:01

confirm you are not a robot.

10:03

And now, what we have is you just you

10:04

just created an app, basically, um

10:06

somewhere. It's not that big of a deal.

10:08

You don't need to worry about what this

10:09

thing looks like, but it'll take you to

10:10

a relatively complicated looking page.

10:12

And we can just skip all that and go

10:13

straight to bot down here. Once you're

10:15

at bot, just scroll down to where it

10:17

says message content intent. Then you

10:20

need to click this button. And once

10:21

you're done, scroll back up to where it

10:23

says token, click reset token. Yes, do

10:25

it. You'll have to enter your password,

10:27

obviously, so I'm going to do so here.

10:28

And now, this is the token, just like we

10:30

had earlier, that allows us to

10:31

communicate with our bot. The last thing

10:33

we have to do is head over to OAuth2.

10:35

And then, down at the very bottom, add

10:37

these permissions. First, click bot, and

10:40

that'll open up a bunch more bot

10:42

permissions down here. You're going to

10:43

want to do uh view channels, send

10:46

messages, send messages in threads,

10:50

uh

10:51

read messages,

10:53

read message history, I think, and then

10:55

attach files, which I'm going to just

10:57

hold command and F and then press that,

11:00

and then do the same thing for add

11:02

reactions right over here. Okay, great.

11:04

Once that's up, it'll say integration

11:06

type guild install, and you'll get a

11:07

generated URL. You may be wondering,

11:09

what the heck does that mean, Nick? It's

11:11

pretty straightforward. Um this is

11:12

basically just going to allow you to

11:13

invite this to uh you know, one of your

11:15

servers.

11:16

Okay, and now you have not genuine app

11:18

wants to access your Discord account

11:19

signed in as Nick. And then, the server

11:21

you're going to want is whatever your

11:22

own individual, you know, Discord server

11:24

is. To be clear, you do need a Discord

11:26

server in order to have this all set up.

11:27

Uh you can create one for free really

11:29

easily. If you've never done that

11:30

before, just head over to Discord and

11:31

then click this little button. Um click

11:33

create my own, and then just do it for

11:35

me and my friends. Name it whatever the

11:37

heck you want. Okay, from there you just

11:38

click continue.

11:39

And now basically it has all of these

11:41

permissions. You can click authorize. Uh

11:43

obviously I am

11:44

not a human, as we both know, and many

11:46

of my YouTube comments routinely accuse

11:48

me. Next up, head back over to Claude,

11:50

and what you're going to want to do is

11:51

launch another instance of Claude. And

11:53

then paste in this command, {slash}

11:55

plugin install

11:56

discord@claude-plugins-official.

11:59

Same thing for me, so I'm installing for

12:01

myself across everything, and then you

12:03

can run reload-plugins to activate.

12:05

You'll see we now have two plugins, and

12:07

you can see that if you just go

12:08

{slash}plugins, over to the right here,

12:10

it says we have That's Claude mem, which

12:12

is currently disabled, Discord, which is

12:14

enabled, Telegram, which is enabled.

12:16

Then I also have a couple of other ones,

12:17

Chrome dev tools, Chrome stealth. Once

12:19

you're done with that, you're just going

12:20

to want to type {slash}discord. Once

12:22

you're done with that, type

12:23

{slash}discord:configure,

12:26

and then go grab that token that we just

12:27

had a second ago. In my case, it's going

12:28

to be right here. Okay, once we're done,

12:30

I'm going to have to exit out of Claude

12:32

code, and then bring it back in. So,

12:34

I'll then go Claude.

12:37

The reason why we had to do that is

12:38

because we have to pump in the token,

12:39

and then we also have to go

12:41

{slash}discord:configure,

12:44

like this. This will turn purple, and

12:46

then we can press enter. And now what

12:47

we're doing is we're basically doing the

12:48

same thing we did a moment ago with

12:49

Telegram. Um we're configuring this.

12:51

We're actually setting it up.

12:53

Okay, so now what we need to do is just

12:54

DM the bot on Discord. And then once

12:56

you're done with that, you can head back

12:57

over to your Claude code, and what you

12:59

want is I'm just cycling through a bunch

13:00

of old commands. Claude--channels

13:03

plugin:discord@claude-plugins-official.

13:07

So, now it's going to be listening for

13:08

channel messages from my plugin. So,

13:10

I'll open up Discord, you know, see that

13:13

there's a new conversation with Not

13:14

Genuine App.

13:15

There's a conversate This is something I

13:16

sent it a moment ago before I actually

13:18

set it up. Um but now it's saying hello,

13:20

and we're actually routed in directly,

13:21

just like we were before. And so, now I

13:23

can have a conversation with uh my agent

13:25

anywhere I want. Okay, so hopefully you

13:27

guys seen, it's pretty straightforward

13:28

to do this setup. Um but uh I think

13:30

probably the logical question a lot of

13:32

you were probably asking is like, "Hey

13:33

Nick, now that I have it set up, like

13:35

what do I do? Like where do I take

13:36

this?" And realistically, this is

13:38

running locally on your computer. So, if

13:40

you only have one computer, okay, if you

13:42

want to have this ongoing 24/7, you're

13:44

going to need to find a way to basically

13:46

have your computer not like lock, not

13:48

have all these processes at run scale.

13:50

And so, there are different ways to do

13:51

that. On like a Mac OS, for instance,

13:53

it's pretty straightforward. There's

13:54

actually really simple easy way to do

13:55

that. You just go to your terminal and

13:57

then just type caffeinate and then, you

13:59

know, if you press caffeinate {dash} t

14:01

for whatever period of time. Basically,

14:04

what this does is this just um turns

14:05

your computer and keeps your computer

14:07

screen on for however long you specify

14:09

here. And so, this is in seconds. Uh in

14:11

this case, it's 60 seconds in a minute,

14:13

so 60 * 60 is about an hour, 3,600

14:15

seconds. But obviously, you could set

14:16

that up for as long as you want. Um

14:18

likewise, you could also go down to

14:20

settings on Mac and then in settings,

14:22

you'll have two different things that

14:24

you can touch. First is the lock screen

14:26

setting, so just head over to lock

14:27

screen. And then where it says turn

14:28

display off when on battery and power

14:30

adapter when inactive, you could just

14:32

say never. And so now, basically what's

14:33

what's going to occur is it doesn't

14:35

matter how long it takes, the computer

14:37

will just never turn the display off.

14:38

So, the display will always be on. And

14:40

then I think you can go over to battery

14:41

settings as well. And then basically, if

14:44

you go to options here, uh you could

14:46

prevent automatic sleeping on power

14:48

adapter when the display is off. So, I

14:50

click this and what that means is

14:51

basically, even when the display would

14:53

have been off, this is just on all the

14:54

time. Then where it says put hard disks

14:56

to sleep when possible, you just leave

14:58

this on. Awake for network access would

15:00

just be always. Then click done, and

15:02

then you're good to go. Uh Windows is

15:03

very very similar. There are just a

15:04

bunch of features out there that allow

15:05

you to just keep it on 24/7. And so, in

15:07

this way, you now have like a you now

15:09

have a server, basically, whether it's

15:10

this computer or something else that is

15:12

just always running in the background,

15:13

meaning no matter where you are what

15:14

you're doing, you'll always just be able

15:15

to have a conversation with it. Now, if

15:17

you wanted to take this further, what

15:18

you do is you get something like a Mac

15:19

mini or some sort of server, you know,

15:21

that you put somewhere in your computer.

15:23

Maybe something that doesn't even have a

15:24

screen. Obviously, you should get

15:25

something that doesn't have a screen,

15:26

it's way simpler. And then you would um

15:28

connect it to whatever the repo or

15:30

folder is that runs most of the uh you

15:32

know, Claude Code skills and stuff like

15:33

that that you have in your computer. In

15:35

my case, I'm doing that using a really

15:37

interesting tool called Syncthing. This

15:39

basically allows me to have two

15:41

computers running side by side, so

15:43

there's my main Mac, which I'm currently

15:44

operating on, and then there's like uh

15:46

another one. I actually have a second

15:47

MacBook, which is just sitting in the

15:48

corner. And what we're doing is we're

15:50

just syncing the same like business

15:52

folder workspace, the one that I

15:53

typically run most of my Claude Code

15:54

skills on. Such that, you know, I

15:56

basically have like a totally seamless

15:58

experience. My Telegram interface, my

16:01

Discord interface, those are

16:02

communicating with my second MacBook,

16:03

which is sitting around, um which just

16:05

did all the things that I showed you a

16:06

moment ago. And then that's syncing with

16:08

this computer, so anytime I need to like

16:10

log in and do work on my desktop, I can

16:12

do that as well. So, we sort of have

16:13

like a two-way sync. Any new file that's

16:15

created on one end, even through my

16:16

Telegram, is ported over here, and then

16:18

the same thing goes in the other

16:19

direction. And uh the only downside with

16:21

that is if you're using Git Commit and

16:22

you happen to try and commit two things

16:24

at the same time on both, so locally and

16:26

over there, you can run into some

16:28

conflicts. In my case, it's not a really

16:29

big part of my workflow. I'm not

16:30

committing every 5 seconds, so doesn't

16:32

really make too much sense for me.

16:34

Okay, and I just wanted to leave you

16:36

guys with a couple of mentions on Open

16:37

Claw. You know, as you guys know, Open

16:39

Claw, uh which used to be called Claude

16:40

Bot and was then called Mole Bot, and

16:42

it'll probably be called something else

16:43

just given PR reasons. Um you know, it

16:45

came out like a few months ago, and the

16:47

entire internet went freaking wild over

16:48

it. And you know, when I saw it as an

16:51

avid and relatively competent Claude

16:53

Code user, in my head I was just like,

16:55

oh, is this like an additional piece of

16:57

like functionality? Is this like

16:58

additional intelligence on top of what

17:00

Claude Code natively offers me as

17:01

somebody that uses it for business and

17:02

for

17:03

uh you know, programming stuff. And I

17:04

was really trying hard to see whether or

17:06

not there was. And I just kept on

17:08

running into a wall where it was like,

17:09

oh, this doesn't actually do anything

17:10

different. It's just basically an

17:12

interface layer where I can communicate

17:13

with Claude through Telegram. In my head

17:16

I was like, well, the reason why this is

17:18

probably growing so popular is because

17:19

we text people, like friends of ours,

17:22

family members, and stuff like that,

17:23

through these messaging apps. So, you

17:25

know, we're texting humans, and now we

17:26

can text an agent as well using the

17:28

exact same sort of UX. That's going to

17:30

seem pretty cool, especially so if

17:31

you're not super technically competent.

17:33

And so, I was like, all right, maybe

17:34

that's why it's blowing up. But anyway,

17:36

it turns out there were a couple of

17:37

other reasons why OpenCloud grew so

17:38

quickly and became like the number one

17:40

most starred repo on freaking planet

17:41

Earth, basically.

17:43

And this isn't a knock against that, or,

17:44

you know, the developer, cuz I

17:45

definitely did some knocking on my my

17:47

old video where I was like, CloudBot

17:49

sucks. So, basically, right around the

17:50

time that all this stuff was happening,

17:52

there was a shitcoin launched, basically

17:54

some some big rug pull where a bunch of

17:56

people decided to blast the message

17:59

like, CloudBot's insane, and stuff like

18:01

that, all over the internet to pump up a

18:02

coin. And so, that's called astro

18:04

turfing, where you try and synthetically

18:06

generate like a large amount of volume

18:08

to make something look really big, and

18:09

it's a common tactic used in marketing.

18:10

It's kind of like a gray hat black hat

18:12

technique, and not really, obviously,

18:14

morally about it. It involves the

18:15

creation of a bunch of accounts and

18:16

stuff like that. Maybe the a bunch of

18:18

GitHub stars, who knows.

18:20

Uh that wasn't the only thing though.

18:22

Right around the time, obviously, you

18:23

had a bunch of creators start making

18:25

videos on this stuff, and then the

18:27

creators saw a bunch of clicks and a

18:28

bunch of interest because they were

18:29

riding that wave of like astro turfing.

18:32

And so, this thing, which might have

18:33

been previously mostly like

18:35

synthetically generated, or maybe

18:36

initially even had like a cool demo that

18:38

was later pushed, became like amplified

18:40

by a bunch of people on YouTube talking

18:42

about how incredible and amazing it was.

18:44

And you know, a few of these people had

18:45

a lot of success with um you know, this

18:47

CloudBot stuff, and so, every single

18:49

time they put it in the title and it

18:51

gets them a bunch of views, what are

18:52

they going to do the next time?

18:53

Obviously, they're going to do the same

18:54

thing, right?

18:55

And so, became this like

18:56

self-perpetuating feedback loop. And

18:58

then to top it off, there were a couple

18:59

of really forward-thinking companies out

19:01

there, um which did VPS hosting, and so,

19:04

essentially, these VPS hosting companies

19:05

started reaching out to a bunch of

19:06

creators seeing an opportunity saying,

19:08

"Hey, we'll happily pay you $5 to

19:10

$10,000 if you want to pop a video out

19:12

on this stuff really quickly talking

19:13

about how easy it is to host using our

19:14

software. And so, these three factors

19:16

basically all culminated in this massive

19:18

explosion of interest for something that

19:19

ultimately speaking was like basically a

19:21

Telegram wrapper with with with Claude

19:24

which is like some heartbeat features

19:25

and then some memory. But for anybody

19:26

that didn't watch the video, one of my

19:27

points was why wouldn't Anthropic just

19:30

do something way better and then way

19:31

more secure as well because you know,

19:33

they obviously have access to the models

19:34

that are the ones that trained the

19:35

models. They obviously understand risks

19:37

like prompt injection, exfiltration and

19:39

stuff. They've got the best. And I was

19:40

just like I don't it doesn't really make

19:41

sense to jump all over, you know, a a

19:43

Claude bot if you're just going to be

19:44

using it for freaking, you know,

19:45

Telegram essentially, a glorified

19:47

messenger. And so, I know a bunch of

19:48

people are like really a big fan of this

19:50

stuff and by all means like you you can

19:52

be it. There's nothing wrong with the

19:53

idea of like decentralized agents that

19:55

are running in the cloud and stuff like

19:56

that. But the vast majority of the use

19:58

cases that most people are like using

20:00

open Claude and Claude bot and stuff

20:01

like that for, they are effectively

20:03

covered by this update and then the

20:04

update that happened a few days ago

20:05

where Anthropic dropped Claude dispatch

20:07

for co-work. And you know, I I I just

20:09

think that it's a much more secure and

20:10

it's a much more scalable solution that

20:12

actually works like off of your stuff.

20:13

You don't have it in the the cloud

20:15

unsecure. It's not maintained by like

20:17

random developers. It's like maintained

20:18

by one of the biggest companies on

20:19

planet Earth uh realistically when it

20:21

comes to AI and probably one of the most

20:23

competent ones as well. And just given

20:24

the recent values differences between,

20:26

you know, Anthropic and then a couple of

20:28

other very major actors in the world uh

20:30

and their commitment to holding firm in

20:32

principles, like I feel a lot more

20:34

comfortable with my data in their hands

20:35

than I do, you know, some some random

20:37

bloke on GitHub or whatever.

20:38

Okay, so those are my thoughts on

20:40

hopefully you guys appreciated the video

20:41

and you know, learned something new

20:42

about uh how to set the stuff up and you

20:45

guys can keep on chatting with Claude

20:46

whether it's through your Telegram, your

20:48

Discord, your computer like I mentioned

20:50

or some other way. If you guys like this

20:51

sort of thing, please subscribe to the

20:53

channel. Really helps me out. Like,

20:54

comment with something else you want to

20:56

see me record a video on and I'll catch

20:57

y'all y'all on the next video. See you.

Interactive Summary

This video provides a comprehensive tutorial on setting up Claude Code's new channels feature, which allows users to integrate Claude with messaging platforms like Telegram and Discord. The presenter demonstrates how to configure these integrations for task automation, highlights the improved security compared to third-party 'Open Claude' bots, and explains how to maintain persistent connections. Finally, the presenter discusses why official solutions from Anthropic are superior to third-party wrappers, citing security, reliability, and the history of astroturfing associated with unofficial alternatives.

Suggested questions

3 ready-made prompts