In this video I'll cover how to use

CloudCode as a non-coder, why I think

it's still the best tool for founders

that want to automate their business and

use it for tasks that actually have

nothing to do with coding, for example,

marketing, sales, operations, and so on.

I'll give you an overview of its most

important capabilities without going too

much into the nitty-gritty. And the goal

is that after this video you'll know

about 90% of everything there is to know

to use CloudCode effectively in just

under 20 minutes. And the reason I'm

making this video is I see a lot of

videos teaching Cloud Code on YouTube,

but it's mostly for coders. And also the

videos that are actually made for

non-coders are pretty much all outdated

because they typically show you how to

use the CLI version of CloudCode, which

is for coders. And what many don't know

is that there are actually now much more

user-friendly ways and easier ways to

use CloudCode. So, I'll get into all of

that. If you don't know who I am, my

name is Moritz. I'm a German engineer

with over 10 years experience in tech,

and I've built a software company to

over 200k in revenue, and now I help

business owners save time and scale by

building AI automations. So, let's dive

in. All right, here's an overview of

every topic I want to cover. I'll start

with the interface and setup, and then

we're going to go into what is actually

the difference between CloudCode and

some of the other tools out there. Then

I'll go into connections and tools,

which I think is the most important

thing to actually unlock CloudCode. Then

I'll go into skills and how to use them,

what they are, and so on. I'll go into

routines, which are essentially

automations. And finally, I'll go into

what are the mobile options and talk

about this a bit. Okay, so let's start

with interface and setup. And the first

thing we'll talk about here is basically

which interfaces are possible to to use

CloudCode from. And right now there are

three options, which is Cloud Desktop,

the CLI, and also through a plugin like

VS Code or Cursor or something like

that. And I'll show you each of those.

So, right now my preferred way of using

CloudCode is through the Cloud Desktop

app that you can see here. Just Google

for the Cloud Desktop app, download it,

and then you can see here, there's a

toggle between home, which is kind of

just like the normal Claude chat, and

also the integrated Claude co-working

here now. I'll go into the difference a

bit later. And then you can also switch

here to code, and uh this is how I use

my Claude code mostly now. And I'll tell

you why, but let me just show you the

other options. So, the other option here

is the CLI. So, you can see here, this

is like basically Claude code living

inside of the terminal. And as you can

see, it looks very technical already.

This is the kind of classic version of

Claude code, and this is, you know, what

gives it like this uh feeling that it's

mostly for coders. So, essentially, it's

a little program that you can open up

from your terminal, and then you can

start like typing and, you know,

chatting with it and getting it to do

stuff for you. So, this is how Claude

code was, you know, in its initial

version was being used, and how actually

a lot of people also still prefer using

it. If you're a developer, one of the

advantages of this is that it's a little

bit more lightweight, so it does feel a

bit snappier and faster. The end of day

though, the capabilities of using it

through the terminal version here

compared to the capabilities in the

desktop version are basically the same.

So, you know, the desktop version is

just a little bit more user-friendly.

Now, another way that people also like

to use it is through an IDE like Cursor

or VS Code or or something like that.

So, here you can see I've opened it up

in Cursor, and what you can do here or

what's the main difference here is that

it's inside of an IDE, you have this

view typically where it's like you can

see the folder that you're operating in.

So, you can see all of the files here.

I'm inside of the Claudia folder here,

this is just my custom folder where I

like operate all of my or most of my

Claude code sessions from. And I have

all of these files saved here, like the

the claude.md file, for example, and

when I click on it, it's opening it up

on the right side here. And then I can

switch between different files, so this

one, for example, and then it's opened

up here on the right side, and I can go

into it and, you know, do edits straight

away.

So, that's the benefit of this view. And

then you're kind of having Cloud Code

within this view as more like a Copilot

type of thing, where you can then chat

with it here. You can tag the files,

also, and it will like make edits for

you or or do whatever you want. Um so,

it's just a different way of creating

Cloud Code. The benefit here, as I

mentioned, is kind of that you basically

have the view into your files, and you

can make edits into your files a bit

more easily. Now, why do I prefer still

mostly just using it through the desktop

app is they've added a lot of

capabilities in the last few weeks,

where you can, even if you're editing

files, you can do it straight from the

app. So, let me show you. So, here, for

example, I had it create a file for me,

and then the file is linked here, and I

can click it, and it will open it up in

this kind of preview here on the right,

and then I can click this button, which

essentially allows me to also edit this

file directly inside of the Cloud

desktop app. So, that's pretty cool. And

I just think overall, using the desktop

app is kind of uh feels a bit more

user-friendly, and so I would say like

90 or 95% of my usage is through the

Cloud desktop app. Okay, next up is this

topic of working inside of a local

folder. So, what does this actually

mean? Now, the main difference between

if you use the Cloud chat in your

browser, same with ChatGPT, the chat

that you're probably used to using out

of the browser,

versus using Cloud Code is that Cloud

Code lives locally on your machine,

whereas Cloud chat, you can think of it

as basically in the internet. And so,

you can think of this like if you're

using, for example, Microsoft Word,

that's a program that is running on your

computer, and you're using that on your

computer, whereas if you're using Google

Docs, you're basically using it through

the browser, and it's, you know, living

on the internet, basically, right? So,

that's like a a simple way to explain

it. And the benefit of having Cloud Code

locally is that it basically has a bit

more power. It can take actions across

your computer, so it can do a lot of

things for you. For example, it can like

read a bunch of files and write a bunch

of files for you very quickly. So, these

are just some of the advantages there.

Now, what does this mean for you? So,

when you're using Cloud Code and you're

creating a new chat here, so when I

click on the plus, this basically opens

up a new chat, you'll see here a couple

of options. The first one is you can

select local or also you can select

something from the cloud options here. I

I won't go into that now because um we

want to just operate locally, so on your

machine, so have local selected. And

then here you can also select the folder

that it should operate from. And this

basically just means you have folders on

your machine. So, we're inside of my

home folder here. I have my finder

opened up. This is my home folder. And

then in that home folder, I have another

folder here called Claudia, which

basically is kind of like my home folder

for operating all of my or most of my

Cloud Code sessions from. When you're

starting out, it's totally fine to just

create one empty folder and just like

start from there. I kind of have it

optimized and I've set up a bunch of

files so that every time I talk to it,

it remembers things. I made another

video about this. It's called my Cloud

OS. You can check that out if you want

to do the same. But yeah, when you're

starting out, you can just create one

folder in your home folder and then just

make sure that this folder is selected

here. And um you can then start your

session, so start your chat from inside

of this folder. Now, this doesn't mean

that it's limited to this folder

necessarily. It just means that this is

the default folder that it operates the

chats out of. So, for example, if you

tell it to create a file, it will create

it inside of this folder. The file will

just like pop up inside of this folder.

But it still has the ability to look

outside of this folder. So, if I would

paste it the path to a different folder,

so for example here, I'll just go into a

different folder like coding projects

and then I'll take this one here and

copy the path, paste it into the chat.

It has the path to this different

folder. I can basically go, "Hey, go and

check out what is inside of this

folder." Hit enter and it has the

ability, even though it's kind of

starting the chat from within my Claudia

folder, it has the ability to go and

check out different folders. The other

little thing you should know about when

starting out is this topic around

permissions. So, basically they have

now, if you click here onto this button

here, just beneath the chat, you have a

couple of options and these are the

permissions. So, you can select between

manual, accept edits, plan, auto, bypass

permissions. And I would recommend to

just always have it on auto, on the auto

mode. Uh, it's one of the newer things

that they introduced a couple weeks ago,

I think, or maybe months. And this is

basically it decides when it should ask

you for permissions. Because what used

to be the problem in the past is that,

by default, I think it was manual. And

then, if you have it on manual, you

basically try to do things, for example,

read a file or write a file, and it

would always like have a pop-up here and

ask you whether it's allowed to do that.

And if you if it starts like doing that

a lot, then it gets very annoying and

slows you down. The other option here,

plan, this is more for I would say more

relevant when you're writing code. You

usually want to have a step before that

where you do like a big plan and then

execute on that plan. So, this is the

plan mode. I don't use it that much

anymore unless I'm, you know, coding big

features. But, since this video is more

about, you know, just using it for

everyday tasks in my business, I don't

really use that much. And then there's

also bypass permissions, which kind of

was what I was using before there was

auto mode. But, now that there's auto

mode, you can basically just put it on

auto and that ought to be the the better

and and easier way to go here. Okay, and

finally, just to get like all of the

basics out of the way is also your model

and context settings, which you can see

down here. So, here, if you press on

this button here, you can see you can

select between the models. Right now, as

of filming this, I usually just have it

on Opus 4.8 and have the fast mode here

enabled. Now, if I want to ask just like

some very basic questions or have it do

something really quickly, I will

sometimes also select Sonnet 5 or Haiku

because those are faster, they use less

tokens, but mostly I kind of just have

it on Opus 4.8 and have the fast mode

here. Fable 5, which is the new model

that they have, is very intelligent,

but, you know, for most of the things

that I'm doing with it, I really don't

need Fable 5, unless I'm doing something

that's like super con- complex or I want

it to like work by itself for a really

long time. And then the other selection

that you can make here is how much

effort it should be putting in. So, if

you don't need that much effort, you can

slide it here to low and then all the

way up. So, it just basically determines

how long it will think and how much

effort it will put into the task that

you're giving it. And I usually have it

somewhere in the middle here. When I

feel like it's something more important

that I want it to do, where I want to

make sure that the results should be

really good, then I'll just like

increase the effort a bit. And if it's

something less important, I um decrease

it, but usually I just have it here on

high. This seems to be like between high

and extra seems to be like the sweet

spot between it still being intelligent,

but still being fast enough for me to

operate on our tasks. Okay, and these

are pretty much the basics here. So, now

you can basically just start a new

session, which is just a new chat, and

you can start chatting with it here. And

it will go ahead and do things for you.

Let's jump into the next topic here.

Okay, next up, let's talk about this

topic briefly, which is something people

often ask and I think what uh gets

people confused is kind of like what is

it actually the difference between

Claude Code and some of the other tools

out there. And I think when you

understand this, you'll, you know,

understand much better like what Claude

Code actually is and how to use it. So,

the first one that people bring up is

what is the difference between Claude

Code and Claude Co-work and also just

the normal Claude Chat. So, let's start

with Claude Chat. Claude Chat is

essentially just, if I switch here into

the chat mode on the home tab, I can

just chat with it and I'll get answers

back. Okay, so that's essentially the

Claude Chat mode. And then there is

Co-work, which kind of is I can chat

with it and it can go and do things for

me. And, you know, in the co-work mode I

can also select like kind of this folder

for the context, and I can also connect

it to tools and so on, so it can do

things across those tools. So, it's

actually very similar to Claude Code,

but the main difference is that Claude

Code work, more or less, you can still

think of it as in a closed environment.

Basically, you can think of it like it's

in the cloud. Both of these are in the

cloud. Claude Chat is in the cloud.

Claude Code work is kind of also in the

cloud, more or less. You can add folders

for context that are local, and it can

write files locally. But, the main

difference is kind of that it's it's a

so-called sandboxed, which just means

it's kind of more closed off versus

Claude Code is it has like less shackles

around it. It's really just like on your

machine and basically do a lot of things

across your machine. So, I'd say Claude

Code is a bit more powerful. I will say

that as it is with software, like they

start out with one feature and then kind

of they add other features on top. I do

think that everything at some point is

kind of going to just become one, and

all of the capabilities will kind of

just merged, and it will be made easier

for the user to understand what what is.

Now, there's kind of this split between

the three different modes, and it's kind

of confusing. But, as of filming this

right now, my personal preference is to

just use Claude Code for most things

because it's still the most powerful.

But, I do think in the future, probably,

there will just be like one normal way

to use Claude, and there doesn't really

need to be like a difference between all

of these modes, and it can just do all

of the things for you. So, it's kind of

a bit of a temporary thing, but yeah,

right now, I think using Claude Code is

the best. Okay, and then you might ask,

"What is the difference between Claude

Code and Codex?" So, basically, Codex is

by OpenAI, and you know, it's a similar

story there. They they basically have

these like three different products,

which essentially, at the end of the

day, will all become the same thing, I

think. But, Codex was basically the

Claude Code version by OpenAI. And, what

they've done recently is they've

released this new desktop app, where you

can also select between ChatGPT work and

Codex. And they're basically the same

thing. Like they can do the same things

now. And within ChatGPT work, you can

now also just chat, which is kind of

just for like simple questions and

answers. So, this is like the classic

ChatGPT chat. And then the ChatGPT work

is now basically like you can, you know,

have it work for you and do stuff for

you across tools. Then Codex is

basically the same thing, but it's more

meant for coding, I guess. But again, I

think everything will just basically

become the same thing. Okay, now what is

the difference between tools like

CloudCode and tools like OpenClaw,

Hermes, and Victor? So, the main

difference is that tools like CloudCode,

you basically use it like this through

this application, and then you can chat

with it directly, and it will go and,

you know, do things for you right here.

You know, it's like the work that it's

doing is very close to where you're

actually chatting with it. Whereas, if

you use something like Victor, and I'll

show you how it looks like there. So,

when you use Victor, and it's pretty

much the same thing with OpenClaw and

Hermes, is that you're using it through

a chat application. So, in this case, I

would be using it through Slack. And the

way I interact with Victor, it's like

it's a bot inside of my Slack. So, I can

just say, "Hey." And then I'll tag

Victor. And once I do that, it will then

answer and, you know, see the message

and answer to that message. And then you

also have this like command center here

where you can go in and like manage

things like which tools it is connected

to, and you can also create skills and

so on. But the main difference is that

you're accessing it from a

communications platform like Slack,

Discord, Telegram, WhatsApp, and so on.

Okay, now and what is the difference

between CloudCode and automation tools

like n8n and Make? Okay, so n8n is an

automation tool. So, you can see here,

for example, it has this like a canvas

where you can like drop in modules, and

you can like configure these modules.

But I would say that tools like n8n and

Make are pretty much outdated by now

because all of the automations that you

can build here, you can build that also

with Cloud Code and you can do it in a

faster way. Whereas, you know, building

these like classic workflows just takes

much longer now. So, I think these are

pretty much outdated and if you want to

automate something, you can do it in

Cloud Code now. Okay, let's go into the

next topic of connections and tools. So,

basically what makes Cloud Code powerful

is that you can connect it to other

software tools and then have it do work

across those tools. So, easiest way to

do that is just basically through the

Cloud built-in marketplace. So, if you

click here on customize, it will open up

this window here. You can click on

connectors and then you'll see here

there are like a bunch of tools that

I've already connected and if you want

to add a new one, you basically just

click here browse connectors. And this

is the marketplace of all of tools that

are available that you can connect to

Cloud Code. Now, technically when you

connect these here, they're connected to

your Cloud

Cloud account, which has the benefit

that, you know, through if you're using

Co Work for example, these tools are

also connected. There are different ways

to make connections. This is just one of

them and I think this is the easiest

one. So, just stick to that for the

beginning. And the way it works is super

simple. So, let's say I want to connect

my Figma account. If I click here into

Figma, I can first like read through

what capabilities are. I can go here

into tools and I can see tools this

particular connection has. So, here you

can see it can generate diagrams, it can

get design contracts. So, here you can

get an idea of what this tool is capable

of doing or basically what this

connection is capable of of doing in the

tool that you're connecting. And then

when you want to connect it, you can

click on connect here and that will

usually open up the, you know, in this

case Figma, your Figma account and

you'll have to log into your account and

then it will be connected. Now, there's

also something called a custom

connector. If the tool is not inside of

this marketplace that I showed you just

now. It just means it's like not if in

the official marketplace, but it doesn't

necessarily mean that you cannot connect

it. So, for example, here you can see

from my list of the tools that I've

connected, there is Beehiiv here, which

is not in the marketplace, at least it

wasn't when I connected it.

But, if I go here into Google and type

Beehiiv MCP, the company actually does

have an MCP. Just the way to connect it.

And, you know, for for other companies

that also have an MCP, this will be a

similar way to do this. You basically

search for the MCP of that company. And,

in this case, okay, search for the

documentation on how to connect the MCP.

Usually, you know, the tools will have

something like that. And then, you want

to find a URL. So, in this case, for

Beehiiv, it's basically this URL here.

And then, you can just go into your

Cloud's code here and click on add

custom connector. And then, type in

Beehiiv. And then, you can paste the URL

here. And this way, you can add the

connection. And after that, it will show

up here. And then, again, you can click

on it and click connect. And then, it

will prompt you to to the login page.

And then, you can connect it to your

account. So, as I said, there are

different ways to connect tools. There's

also through CLI tools or just through

the API directly. But, I think when

you're starting out, the really easiest

way is to just do it through the MCP.

Another thing I want to mention here as

well is basically the ability for Cloud

Code to use the browser for you. Because

if certain tools that you want to

connect and have Cloud Code take actions

for you on those tools, if they don't

have an MCP or any other way to connect

to it, then you can still default to

basically just having Cloud Code use the

browser for you. And the classic way of

doing that was, if you go here to

connectors again, you can you see this

like Cloud in Chrome. And it's basically

a Chrome extension that you can install.

And once that's installed and connected,

you can basically say things like, "Hey,

open up YouTube on my browser in

Chrome." And so, you can see here now

it's saying I'll use Cloud in Chrome to

open YouTube. And if I switch here to my

browser, you can see it's opening up

YouTube. And here obviously you can then

have it take other actions for you. And

these can be, you know, full workflows.

For example, I have this like particular

workflow where I wanted to open up

YouTube for me, go into my account, view

my channel, and then attach a comment on

one of my videos. But I do think that

this method is also becoming obsolete

soon because just a few days ago, they

now released the browser directly inside

of the Cloud Desktop apps. So if I click

here to open up the browser, I can

actually also open up websites just

inside of this browser here, and it

should then be able to basically, like

you can you can also log into your

accounts there, and have those accounts

like be persisted the login, so that it

will, you know, across other chats, it

will still stay logged into your

account. And you know, it just has

access to the browser directly here. So

I think this will be even easier way to

do this other than installing this

Chrome extension. Okay, and finally, I

do want to also mention Meta Connector

Tools. And these are basically, you can

think of them like as a tool that's kind

of like a third-party marketplace to

connect a bunch of other tools. And one

of the most famous tools here is called

Composio. So if I go into my Composio

account here, you can basically see I

can connect Composio once, and then

within my Composio account, I can

connect all of these other tools. So for

example, I have my Gmail here that I can

connect it to my Google Docs and so on.

And the benefit here is that, first of

all, sometimes these connections are

more capable than the connections that

you can do directly through your

marketplace inside of the Cloud Desktop

app. So one example here is, if I look

for Google Drive, Google Drive exists

here in the Cloud Desktop app, and it

has a couple of tools available like

create file and so on.

But if I want to interact with like

Google Sheets files, the Google Sheets

connector actually does not exist here.

But in Composio, there is a Google

Sheets integration. And basically, it's

kind of like a pre-built, I guess, you

know, integration that access the API

directly. You know, you don't have to

know the technical details here, but

essentially, what I'm trying to say is

there is like sometimes you can find

some capabilities that are possible

through the connections that you can

make here through Composure that do not

exist on the Cloud Desktop app. The

other benefit of using a meta connector

tool like this is that if you ever want

to migrate all of your connections, so

for example, you you know, you're using

Cloud Desktop and then you want to

migrate it to using it through the Open

AI ecosystem, then you only need to

migrate this one connection and

basically bring all of your other

connections with you. So, that makes the

migration easier. That's one of the

benefits as well. Okay, next up is this

topic of skills. So, what are skills?

Skills basically just you can think of

them as a saved prompt. That's the

easiest way to think about this. How do

you create skills? Well, the easiest way

to do that is you open up a new chat and

you say what you want the skill to be

about. So, for example, I want you to

create a skill. It should and then you

do two and so on. And you just describe

what it should do. Step one, it should

go into my um tool which records my

meetings, fetch the transcript. Step

two, it should go through that

transcript and summarize it and so on.

Okay, where are skills stored? If you

create the skill like the way I showed

you just now in Cloud Code, they will be

stored locally in a folder. So, inside

of this uh folder that you're operating

your Cloud from, in my case it's

Claudia, and then there will be a folder

here called dot cloud. It's a hidden

folder, so you need to press the

keyboard shortcut shift command dot to

show you the hidden folders in here. You

click into this dot cloud folder and

then there will be a folder here called

skills. And this is where all of the

skills are saved. So, you can see

they're kind of just like uh if you look

have a look at this this skill here,

it's like a folder called proposal

builder, which is the name of the skill.

And inside of that folder, there's a

skill.md file. And here is where the

logic of the skill lives. And it's just

plain text English, right? That

describes what the skill should do. Now,

if you create skills in the desktop app,

and this is by default if you create it

from co-work, and admittedly, that's

kind of confusing now, but that's just

just the way it is. It will be saving it

inside of You can imagine it like being

saved in the cloud, basically, your

skill. And it's like tied to your cloud

account, whereas the other skill that

you're creating is locally on your

machine. But yeah, the ones that you

create through co-work are living in

here, and so you can see the skills here

in this list. I basically like kind of

just copied all of my local ones into

here as well, so I can use the same ones

on co-work if I wanted to. And yeah,

that's just like the different places

where they live. I think this is like

one of the topics where as time goes on,

Anthropic will probably like find a way

to make the management of these skills a

bit easier, but that's kind of the way

that it is right now. If you do it

through code, they will by default be

saved locally. And if you do it through

co-work, they're saved like basically,

you can access them here through the

desktop app. Now, there's also this

topic of plugins, which is, you know,

one thing that people ask when it comes

to this topic of skills. And I don't

want to make it too confusing, but

basically, plugins in the Anthropic

ecosystem is essentially a package of

skills and tools. So, you can see here

through the plugin marketplace, if I go

into this like this is the productivity

plugin that was created by Anthropic.

And you can also, you know, create

custom plugins for your own company or,

you know, other companies like here,

Carta has created plugins that are also

featured here officially in this

directory. But essentially, what it is,

you click into it, and it is like a

bundle of skills and also a bundle of

tools that you can connect. Okay, so, I

don't want to go too much into detail

here, but yeah, that's basically what it

is. What makes it kind of confusing is

that if you go into the Open AI

ecosystem, when they talk about plugins,

it's basically just the direct

connection. And so, uh you know, this

all makes it slightly confusing, but uh

yeah. Personally, I just have like

skills and connected tools. For me,

that's enough, and I don't use that many

plugins, but uh you know, they might

become useful. If you're doing a

specific function very often, or you

know, you want to create like a bundle

of skills and tools for your company,

then uh this might come useful. And the

final which is actually the reason why

they're so useful is that after you've

saved this prompt, basically, you can

just very easily just trigger it. And

you do that by typing forward slash, and

then let's say I want to trigger my

YouTube upload skill, and then I can

just select it and basically hit enter,

and it will go ahead and trigger it for

me and and run that prompt, basically.

Okay, next up, let's talk about this

feature here called routines. So, first,

what are routines? Basically, if I click

into it, you'll see these are

essentially automations, and they're

just defined by a trigger, and then the

thing that it should do when it

triggers. So, you can see here if I want

to define it, it will have

a trigger of the schedule, so I can

select like manually, hourly, daily,

weekly, and so on, or custom, and then

just the things that it should do when

it triggers. So, how do you create them?

Easy way is clicking here into the

routines tab, and then here you can

click on new routine. You can select

between local and cloud. I'll go into

that later. If you then select local,

you can define like the things that you

do here, and then just hit create.

Another even easier way to do it is also

just inside of the chat. I want you to

create a test routine. Okay, so now it's

said basically it just like created a

Telegram ping test routine. And now if I

go into my routines tab here, you'll see

it created this test Telegram ping

routine. And that's also, you know, you

can just create your routines through

the chat. Now, what is this difference

between local and cloud routines? So,

essentially, local is, as the name said,

it runs locally, which means it will

have the same capabilities as when

you're just running a prompt locally.

So, you can think of it like you're just

defining a trigger, and when that

trigger happens, so for example, every

morning at 9:00, it will just

essentially create a new cloud code chat

and just paste your instructions as the

prompt. That's it, basically. That's how

local works. Now, the big downside to

that, obviously, is that this only works

when your cursor is on and when your

cloud desktop app is on. So, if you want

something to just constantly run without

you having to have your cloud desktop

app on, this may not be the best thing

to do. Although, if you look at my

routines, since, you know, I use cloud

desktop every day, most of my routines

are local routines. And it's just the

easiest way to do this, because you

don't need to set anything else up. You

just create your routine, and that's it.

And since my cloud desktop app is on all

the time anyways, they will just trigger

when the time comes. The other way to do

this is through the cloud, and this you

can really think of as you're basically

creating like this set of rules, and

then you're hosting it somewhere in the

cloud, and every time the trigger

happens, it will basically just run this

thing, but it will run it in the cloud

instance. So, it won't run it on your

computer. The downside is it takes a

little bit longer to set up, because you

need to create a repository for it and

then host it and so on. You can define

also like which tools it is allowed to

connect to. And these are, by the way,

all of the tools that you've connected

through your customize, so you can

define which ones it should have access

to in this particular routine. Then,

when the time comes, it just basically

triggers that. So, if you want

automations that really should just be

constantly running, like every day or

something like that, then this is the

way to do that. And you can compare

these with basically N8N or Make

automations. You can, you know,

essentially just like write your logic

here, have it create this automation and

put it in the cloud and it will just

constantly run. Okay, now the last topic

here is mobile options and I have to

admit that there are some options right

now for you to be able to use cloud code

on your phone, but they're not great

yet. And if your usage really is heavy

on your phone, then maybe using a tool

like you know, open claw, Hermes or or

Victor is the better option for you. But

you know, if your usage is heavy just on

your laptop, then I I think cloud code

is a very good option for you. Having

said that, there are a couple ways to

access cloud code on your phone. And the

first way is basically this feature

remote control. You can go into settings

and then if you go here into the cloud

code settings, you can activate this

setting here which is called enable

remote control by default. And what this

does is that every time I create a new

chat, it will by default activate this

remote control, which essentially means

if I click here, you'll see here I have

this is it says remote control is active

on this one. And it just means that this

chat that I'm creating here is also

automatically accessible from my cloud

mobile app and I can continue the chat

there. The downside is that since this

is a local session, I cannot create the

local session from my phone. I can only

create it here from my laptop and then

continue it on my phone. If it's a cloud

session, then it's possible. But yeah,

in in my case I'm using this locally, so

it's you know, it's useful for

continuing conversations, but other than

that, it's not super useful. The other

way is then through a feature called

dispatch. Now, this is actually a

feature that was only developed for

co-work initially and then later it was

expanded to be able to used in cloud

code. And I can click here into

dispatch. You can think of it just like

one chat that you can have as like one

channel that they created that is

accessible for you on your local desktop

here, but then also on your phone. And

then there's this little trick here,

which [clears throat] is if you want

your dispatch to always just have access

to cloud code, you can go into your

co-work instructions here and basically

just type in the instructions here to

say "Every time I use dispatch, just

have it access my cloud code" or

something like that. I used to have

this. I don't know why this prompt got

deleted for some reason, but yeah, this

is like one little trick how you can

kind of force your dispatch usage to be

just using cloud code instead of

co-work. All right, that's it. So, these

are pretty much all of the things you

need to know to be using cloud code on

like a near professional level without

going too much into the details,

although I think I went over 20 minutes,

but yeah, that's it. I appreciate you

watching till the end. And if you want

to see more of these kinds of videos,

then feel free to subscribe to my

channel. And if you want to get help to

automate your business, then go check

out joinagentos.com. This is where you

can work with me and you can book a call

with me, and then we can have a look at

your business and see which parts of it

we can automate so that you get to work

faster, that you get more done, and

ultimately have better margins and make

more profit. All right, thanks for

watching. See you in the next video.

Bye-bye.