HomeVideos

Claude Dispatch Just Dropped, And It Kills OpenClaw

Now Playing

Claude Dispatch Just Dropped, And It Kills OpenClaw

Transcript

554 segments

0:00

Anthropic shipped the feature called

0:01

Claude Dispatch, which lets you

0:02

essentially run and manage an AI agent

0:04

through your phone. In this video, I'm

0:06

going to show you guys how you can use

0:07

it, why it's significantly better and

0:09

probably more preferable from a security

0:11

perspective than a lot of the

0:12

pre-existing solutions like Open Claude

0:13

et al. And then, how to set it up on

0:16

your end so you guys can run everything

0:17

that you need from the convenience of

0:19

your device. So, some of you guys will

0:20

know, I'm a big fan of using Claude Code

0:22

to do a lot of economic knowledge work

0:24

for me. This video is not trying to say

0:26

that Co-work is better than Claude Code,

0:27

but it is a different and easier

0:29

interface that a lot of less technical

0:30

people can use to get up and running.

0:32

So, in Claude Code, I have a bunch of

0:33

skills, which are essentially tasks that

0:35

I fire off one at a time. I say

0:37

something like, "Hey, scrape me 100 HVAC

0:40

leads in Texas." And this will actually

0:42

go through and then literally contact

0:44

the internet, run a bunch of scrapers,

0:46

and then return them back to me on

0:47

totally autonomously. The issue is

0:48

obviously, using my phone with a setup

0:50

like this is annoying. It's often pretty

0:52

fragile, and then it takes a fair amount

0:53

of setup. So, Claude Co-work solves all

0:55

this for us completely out of the box.

0:57

Okay, so totally hands-off demo, I have

0:59

Co-work set up with Claude Code

1:01

Dispatch. It's right over here, and uh I

1:03

just want to scrape 200 agency owners in

1:04

California with a 1 to 10-ish size. You

1:07

can see the second that I entered that

1:08

in, that was immediately reflected over

1:10

here on my screen. And the reason why is

1:12

because this is now running locally.

1:14

Now, I don't know, I'm just on the go,

1:15

right? I'm waiting for uh some train or

1:17

something like that, and I say, "Hey, I

1:19

could probably get a couple of phone

1:20

calls in." So, I launch it from here.

1:22

Immediately after we see actually see a

1:23

window open under Dispatch over here, um

1:26

as a new tab on sort of our Claude

1:28

Co-work ongoing conversations. So, what

1:31

it's doing now is it's actually running

1:32

the skill. Okay, it's doing a bunch of

1:34

the specific SOPs inside of the skill,

1:36

like generating search keywords, running

1:37

a test scrape, and so on and so forth.

1:39

And then, I'm going to see the results

1:40

back here on my phone the second that it

1:42

finishes. Okay, and then just a few

1:43

minutes later, I have all of them on my

1:45

phone here. I don't know if you guys

1:46

could see this, but um it's like data

1:48

set leads finder. I have all the phone

1:50

numbers. So, if I just wanted to, you

1:51

know, click on one of these and maybe

1:53

give them a ring, start doing some cold

1:54

calling, I could. Um I just initiated

1:57

and then completed that loop entirely

1:58

from my phone, which is pretty sweet.

1:59

But obviously that's not the only thing

2:00

that I can do. Um, I have this pretty

2:02

cool inbox cleaner flow, which I like

2:04

running. And um, what I'll do now is I'm

2:06

just going to initiate that inbox

2:07

cleaner again from my phone. So I'll

2:08

say, "Run inbox cleaner." And then my

2:11

hands are up here just so you guys could

2:12

see. Um, it's going to start a

2:14

conversation, um, go down to that tab

2:16

there. And then just like I did before,

2:17

it'll it'll run my own skills on my

2:19

computer using um, you know, Claude

2:21

co-worker. And just because I want to do

2:22

multiple things simultaneously, I'm also

2:24

going to have it run another skill.

2:26

Uh, what I'm going to do is

2:27

hypothetically, let's say I have found a

2:29

YouTube thumbnail that I really like and

2:31

I have a video that's coming up soon.

2:33

So, you know, let me just make this a

2:34

little bit bigger. Okay, there's this

2:35

awesome one here from um, I don't know,

2:38

uh, "Don't Create an LLC." It's by

2:40

Jasmine Dilucci. She's this person that

2:42

uh, I don't know, creates content all

2:43

about accounting and stuff like that. So

2:45

what I'm going to do is I'm just going

2:46

to share this. I'll copy the link and

2:48

then I'm also going to feed this

2:50

directly into Claude

2:52

um, Dispatch and I'm going to say, "Hey,

2:55

recreate this thumbnail

2:57

but with my face."

3:00

Then I'm going to paste in the link and

3:01

now we should also pass the next uh,

3:05

message in queue.

3:06

And what this is going to do is it'll

3:07

launch an additional Dispatch

3:09

conversation that uh, will allow us to

3:12

run multiple of these things. Okay, and

3:13

then if you see here, we're running all

3:15

three accounts in parallel, fetching,

3:16

classifying, then marking read for each.

3:19

Over here, we're actually reproducing a

3:21

thumbnail using my thumbnail generation

3:23

skill with which has some face swapping

3:25

uh, functionality built in. And I'm

3:26

going to get it on my phone in just a

3:27

few seconds. Now in my case, I didn't

3:29

uh, realize but one of these skills

3:31

actually required a little piece of

3:33

access from my computer that I hadn't

3:34

given it ahead of time. And so when that

3:36

occurred, I just had a little window

3:37

that popped up at the bottom of my

3:39

Claude Dispatch and it said, "Hey, you

3:40

know, we're trying to reach XYZ. Uh, do

3:42

you want to allow this request?" So I'm

3:44

the one that just instantiated the

3:45

request, obviously I'm allowing it. This

3:46

sort of like security and then allow

3:48

listing style permissions is what makes

3:50

this 10x more safe, uh, you know,

3:53

secure, and then scalable for business

3:55

and then enterprise applications than

3:56

something like open claw. Okay, and then

3:58

in this case it's now created a bunch of

4:00

files. I don't think this is the best or

4:02

most realistic look that I've ever had

4:04

before, but still not pretty bad and you

4:07

know, we initiated this from my phone.

4:08

And it's not just available over there,

4:10

it's also available over here. So

4:11

dispatch is reporting back right now

4:13

letting it know that you know, it just

4:14

finished the thumbnail thing. And now

4:16

it's asking me to allow it permissions

4:18

to go and grab those thumbnails which I

4:20

will do in a second. And now it's

4:22

actually showing them to me all on my

4:23

phone. So you know, I have them right

4:24

over here too, right? I can actually

4:26

take a look at them and then okay, I

4:28

guess I can't scroll through them, but I

4:30

don't know. That's another one right

4:31

over there. That's another one right

4:32

over there. And so I just generated all

4:33

these from my phone basically through

4:35

like an app, right? This app, but I

4:37

didn't actually have to like whip up an

4:38

app for it. I could just wrote this to

4:39

my computer, which is pretty sweet. And

4:41

then the inbox cleaner also finished and

4:42

in my case basically what this does is

4:44

it just automatically marks as read

4:45

anything that

4:47

I would consider to be some form of

4:48

spam, some people soliciting me, that

4:49

sort of thing. And then if there is any

4:52

like important email or whatever, it

4:53

goes through and then it pre-drafts a

4:55

reply based off of a bunch of old

4:57

replies that I've sent. And then it just

4:59

allows me to QA and sort of human in the

5:00

loop. So I then go through my inbox, but

5:02

I basically save like 90% of my time.

5:05

So that's pretty neat, right? Like it's

5:06

done my personal Gmail, it's done a

5:08

couple of other things.

5:09

Simple systems like this essentially

5:10

allow me to save two or three hours a

5:12

day. And before I was constrained with

5:13

doing all this stuff on my computer. I

5:15

had to lug around my big fat laptop with

5:17

me. But now you know, I could set up my

5:18

laptop or I could set up another

5:20

computer or some sort of Mac mini in the

5:21

corner and then I could just like sort

5:22

of port in, run whatever skills, run

5:25

whatever workflows I need even while I'm

5:26

over here. And then you know, naturally

5:28

I receive and then can send additional

5:30

data, follow-ups and everything like

5:31

that from here. Well, that's still super

5:33

secure. So in my mind this has solved

5:34

everything. I'm sure we're just a few

5:36

stones throws away from having this sort

5:38

of stuff in Telegram. Let me show you

5:39

guys how this all works under the hood.

5:42

So if it isn't clear, I think that most

5:43

of these autonomous agent tools are

5:46

pretty broken. And they're broken for a

5:47

couple of reasons. The first is these

5:49

open claw and DIY agent stacks, which I

5:52

think everybody and their mom is going

5:53

to try and tell you is like the future

5:54

and stuff like that. Um they are

5:56

terrible from a security perspective.

5:58

We've had tens of thousands of API keys

6:00

leaked. Uh very elementary sort of

6:02

security errors here have hit news

6:04

headlines over and over and over again.

6:05

It got so bad they had to change their

6:07

name multiple times and stuff like that.

6:09

And I mean like their core functionality

6:10

is pretty cool, right? Which is that I

6:12

get to text my model basically from my

6:14

phone and then have it do economically

6:15

valuable tasks for me. And the reason

6:17

why beginners and you know, people that

6:18

aren't very tech uh super into this sort

6:20

of tech love it is because it's like,

6:21

"Hey, I you know, I talk to my friend in

6:23

Telegram and then immediately underneath

6:24

I have my Claude bot in Telegram and

6:26

that's awesome."

6:27

Right? It's just like good from a user

6:28

experience perspective. But all of that

6:30

isn't really worth risking, you know,

6:31

your API keys, your credentials, your

6:33

credit card numbers, your identity,

6:34

right?

6:35

In addition to obviously massive

6:36

security issues, there's also like a

6:37

context explosion issue where you are

6:39

paying for the most part using your um

6:42

API pricing instead of like a monthly

6:45

recurring subscription, which Anthropic

6:47

subsidizes heavily and tends to be

6:48

somewhere between like four to eight X

6:50

cheaper. What I mean by this is you are

6:52

doing direct API calls to their back

6:55

end. And every single time you make an

6:56

API call, um it bills you usage twice.

6:58

Like that's, you know, every message 50

7:00

cents, you know, every time a skill

7:02

runs, that's $2. Every single moment

7:05

that you're having a conversation with

7:06

um models on, you know, Open Claw and

7:07

whatever, unless they're running locally

7:09

or running using something like Nemo

7:10

Tron.

7:11

What you're really doing is you're just

7:12

constantly like

7:14

burning your money in the background.

7:15

And then, you know, ultimately this pay

7:17

per token plus the security problems, in

7:19

my view, makes this like a non-starter.

7:21

You know, if I'm using this in a serious

7:22

business application, I'm basically

7:24

never going to recommend something like

7:25

Open Claw or whatever. And so, when this

7:27

came out, you know, I made a bunch of

7:28

videos talking about how horrific it was

7:29

and all of the API keys that got leaked.

7:31

And I was like, "You know, I bet it'll

7:32

just take a couple of months before

7:34

Anthropic launches a native feature that

7:35

does all this stuff." Um and that's what

7:36

Claude Dispatch is. So, with Claude

7:38

Dispatch, you basically connect

7:40

automatically to whatever your desktop

7:41

is, your computer. Um so your skills,

7:43

you know, all of the pre-existing MCP

7:45

connectors and all of your files. Uh but

7:46

it's also sandbox and local. And I mean

7:48

like, you know, if there's a company

7:50

that I trust to understand how to rein

7:53

in, you know, the downsides of like AI

7:55

agent flexibility, it's the companies

7:57

that have developed the best AI agents

7:59

out there. Um like Anthropic, they've

8:01

spent, you know, hundreds of millions

8:02

and not billions of dollars doing this

8:04

exact thing. So I trust them to, you

8:05

know, sandbox and make things pretty

8:07

local. Um it's also uh like a flat

8:10

monthly charge because it's technically

8:11

used as part of your subscription. Now

8:12

they're talking about how they're going

8:13

to make this available to pro plans

8:15

pretty quick. I think right now, as of

8:16

the time of this recording, it's on max

8:17

plans, but they're they're going to want

8:18

to try and get everybody on it. And so

8:20

what that means is instead of paying,

8:21

you know, I don't know, like it really

8:22

depends on your usage and I don't want

8:23

to pretend like I know exactly how much

8:25

you're using, using, but when I tried to

8:27

open Claude, I spent like a hundred

8:28

bucks or so in just my first few days

8:30

and then I was like, okay, now I turn

8:30

this off. Instead of spending that, you

8:32

know, you'll you'll probably just spend

8:33

20 to whatever the the the subscription

8:36

amount is. And it's going to be heavily

8:38

subsidized.

8:39

And then, you know, it's the same power

8:41

here, but I want you guys to know,

8:43

realistically speaking, you're probably

8:44

going to get significantly more usage

8:46

out of co-work because

8:48

out of Claude dispatch because they're

8:49

just going to like build in more and

8:50

more and better functionality. This is a

8:52

company that has access to basically all

8:54

of the information on planet Earth at

8:55

this point. Um I trust that they're

8:57

going to do a much better job with this

8:58

sort of infrastructure and architecture

8:59

than some random third party. In terms

9:01

of how dispatch specifically works, um

9:03

it's sort of like a multi-layer system.

9:05

You know, down at the bottom, its brain

9:07

is Claude co-work. And uh you know, I

9:09

usually make videos not on co-work

9:11

because that's the non-tech version of

9:14

this intelligence and an agent tech

9:15

model. Um I make more videos on Claude

9:17

code, but Claude co-work and Claude code

9:19

are basically, you know, the exact same

9:20

thing. It's just like support for a

9:22

wrapper that wraps around skills and

9:24

then, you know, pre-established SOPs. So

9:26

basically what happens is um Claude

9:27

co-work, which is your base sort of

9:29

agent here, has access to your skills

9:31

library and a bunch of MCP services to

9:33

do things for you. Dispatch on your

9:34

phone basically just um it communicates

9:37

through layers with, you know, your MCP

9:38

servers, your skills, back to Cloud

9:40

CoWork. Cloud CoWork does something, and

9:42

then it kind of communicates back up the

9:43

ladder to Dispatch. And that's what I

9:44

was talking about with um, you know, the

9:46

fact that this is like an agentic thing.

9:47

You're you're launching an agent. Those

9:49

agents can launch sub agents, and and so

9:51

on and so forth. All right, so I'm going

9:52

to show you guys how you guys could set

9:53

up uh Cloud Dispatch in just 5 minutes.

9:55

It's really easy. We're just going to

9:56

update Cloud Desktop, or just reinstall.

9:59

We're then going to update the Cloud

10:00

mobile app. We see Dispatch in the

10:02

sidebar. We're good to go. We can

10:03

actually enable it and then turn all

10:05

stuff on right now. If not, you know,

10:07

we're just going to restart our

10:08

computers until we see, you know,

10:09

whatever the the update logic is. Um

10:11

this is literally It's probably not even

10:12

going to take 5 full minutes. Let me

10:13

show you guys how all this stuff works.

10:15

In terms of how to set this up, this is

10:17

a pretty new feature. It was launched

10:18

sometime in the last 24 hours or so. And

10:21

so, many of you will not have this

10:23

Dispatch tab added to your Cloud CoWork.

10:26

That's okay. If you don't already have

10:28

this, what you need to do is you need to

10:30

update the application. So, just for all

10:32

intents and purposes, in case you don't

10:34

have Cloud Desktop set up, it's as easy

10:36

as heading to cloud.com/download,

10:39

then going from Desktop over here,

10:41

selecting your operating system, and

10:43

then choosing either Mac OS, Windows, or

10:45

Windows arm 64. You'll also have to pair

10:48

with the desktop app on your mobile, so

10:51

choose iOS or Android here. Once you're

10:53

done on desktop, you'll have an

10:54

interface that looks like this. Now, I

10:56

should note that there's actually three

10:58

different sections to Cloud Desktop.

11:00

There's chat, CoWork, and code. And for

11:02

this feature, you're going to need

11:03

CoWork, which you can also use hot keys

11:05

to bump to, in my case command two.

11:07

Now, once you're done, head down to this

11:09

Dispatch feature, and it'll say

11:11

something like CoWorking on the go. In

11:13

order to get this started, it walks you

11:15

through sort of the functionality, which

11:17

is that your phone is like a

11:18

walkie-talkie that can communicate with

11:20

Cloud and your computer. You just send

11:22

Cloud a message, and it'll work on tasks

11:24

locally using your computer. Um the one

11:26

caveat to this is you do need to

11:28

remember to keep your computer awake. Uh

11:30

this is a big thing that a lot of people

11:32

were doing with open claw. They would

11:33

purchase specific computers like Mac

11:35

minis or whatever, plug them in and just

11:37

have them working 24/7. This is the

11:39

exact same thing. You just have, you

11:41

know, your computer where you want to do

11:42

these tasks awake and then Claude

11:44

Dispatcher can take care of the rest of

11:46

it for you. Anyway, all you do is you

11:47

click get started and then you have to

11:49

pair with the Claude mobile app. So,

11:51

I've already downloaded the Claude

11:53

mobile app. All I'm going to do is open

11:54

this puppy up. Now, it looks like I'm

11:56

already signed in to my phone, so I have

11:58

the Claude desktop app open right over

11:59

here. It has a chat window um ready to

12:02

to talk to Sonic 4.6.

12:05

Next up, it'll ask, "Hey, can I give

12:06

Claude access to your files?" So, it'll

12:08

ask me when I click finish, "Should I

12:10

keep this computer awake?" which you're

12:12

going to want to click yes to, otherwise

12:13

dispatch is going to run into some

12:15

problems. Um give it the ability to use

12:17

Chrome and then ensure that all

12:19

connectors are on, okay?

12:21

Then just click finish setup. It'll ask

12:23

to access files in your desktop and

12:25

documents and so on and so forth. You're

12:27

going to have to click this button a

12:28

bunch of times.

12:29

And now you have the ability to

12:30

communicate with your phone and Claude.

12:34

Now, on my phone's end, all I need to do

12:37

is in my Claude app, scroll down to

12:39

where it says dispatch, click the

12:41

button, and then I'll get something that

12:43

looks like this. And as you can see, the

12:45

UX and stuff like that is very similar

12:46

to what we just did. So, all I need to

12:48

do is click pair with your desktop and

12:51

then it'll connect automatically with

12:53

the conversation that's in this window.

12:55

So much so that my hands are off the

12:57

computer now. All I'm going to do is

12:58

type, "Hey."

13:00

And I want you guys to see how this

13:01

immediately pops up on my computer as

13:03

well. And so, I'm actually having a

13:05

conversation with Claude uh co-work

13:07

through dispatch right now. It's fully

13:08

managed for me and then I obviously have

13:10

like a contiguous conversation history,

13:12

which is really sweet. And here is where

13:13

I could start by, I don't know, running

13:15

some skills. So, I'll say, "Run the lead

13:18

scraper skill. Get me some leads for, I

13:21

don't know, HVAC in Texas."

13:24

Let's just do 100 to start. I'm now

13:26

going to send it the message, and it's

13:28

going to go through the process of

13:29

connecting to the skill, which is in my

13:32

Cowerk instance, and finding all the

13:34

session information and stuff like that,

13:36

and then actually launching it. And then

13:38

I will have all of the information and

13:39

everything I need uh popping up on my

13:42

phone as well. And you can see when I

13:44

actually kick off a skill execution, I

13:46

create a new tab here that is prepended

13:49

with the words dispatch. In this case,

13:51

it's scrape HVAC leads Texas.

13:53

Uh that actually opens this up. And then

13:55

you can see the progress bar on the top

13:57

right-hand corner, just cuz this is a

13:58

pre-installed skill that I, you know, I

13:59

put together a while back. Um it'll go

14:01

through the debugging and everything

14:03

else it needs to. And you know, I'm I'm

14:04

not actually going to see a message back

14:06

like on my phone until this thing is

14:08

done and it delivers the results. In

14:10

this way, essentially what it's doing is

14:11

it's like spinning up new Cowerk

14:13

instances, uh new Cowerk conversations

14:15

almost as like sub-agents, going doing

14:17

the task, and then reporting back the

14:18

results of said task to me. Also,

14:20

hypothetically, if you were using

14:22

something like Cloud Code, and you

14:23

wanted this one-shot skill run

14:25

functionality from your phone, really

14:27

simple and easy way to do it is you

14:28

basically just get all your skills from

14:29

whatever your IDE or your Cloud Code

14:32

instantiation is storing them. So, in my

14:34

case, it's right over here. And then, in

14:36

my case, I just duplicated them to this

14:38

new folder, which is .cloud/skills. And

14:40

then I just said, "Hey, I want you to

14:41

add them all to Cowerk." It then goes

14:43

through, sends you a couple of brief

14:45

little requests. Then after all this

14:46

stuff is said and done, um you just get

14:48

a big list of skills that you can just

14:49

copy over to Cloud Cowerk. Uh and this

14:51

is going to allow it to work with

14:53

dispatch really easily. So, I'm just

14:54

going to click copy to my skills.

14:55

Actually, this one I think is already

14:56

part of it. I would just did this as a

14:58

demo, so this one should be good. That's

15:00

actually going to like add auto research

15:01

diagrams directly over to the system.

15:04

The next one, face variants for

15:05

instance, and so on and so forth. Then

15:07

you'll get this copied to your skills

15:08

message at the top, and now you can

15:09

access it in dispatch really easily.

15:11

Okay, hopefully you guys appreciated

15:12

this video. Um dispatch is really cool.

15:14

This is, honestly, a stand-in

15:15

replacement for 80 to 90% of all the

15:17

features that Open Claw and other

15:19

extraordinarily insecure implementations

15:21

of autonomous decentralized agents uh

15:22

provide for you. So, I'm using this

15:24

thing all the time now, and it's not

15:26

just because I'm like, I love Big Daddy

15:28

Anthropic, although I do, it's because I

15:30

just think this is a much safer and

15:31

better solution than something like,

15:33

you know, what most most other people on

15:35

on Twitter and X are probably shilling

15:37

you. If you guys like this sort of

15:38

video, please sub to the channel. Around

15:39

70% of you guys aren't for whatever

15:41

reason, so you'd be doing me a big

15:42

solid. Like and then comment down below

15:44

with whatever the heck you want me to

15:45

make videos on. I really make videos

15:47

based off of audience feedback at this

15:49

point. So, if you guys want anything in

15:50

particular you want me to record or

15:51

cover, let me know. I'm more than happy

15:53

to do it for you. Have a lovely rest of

15:54

the day. Catch all y'all in the next

15:55

video.

Interactive Summary

This video introduces 'Claude Dispatch,' a new feature by Anthropic that allows users to run and manage AI agent workflows directly from their phone. The host demonstrates how it connects to local computer instances (using Claude Co-work/Claude Code) to perform tasks like web scraping, image generation, and inbox management autonomously. The host emphasizes that this solution is significantly more secure and cost-effective than third-party alternatives, which often suffer from API key leaks and expensive token-based pricing models.

Suggested questions

3 ready-made prompts