Now, when working with Claude Code, you can run it in a loop.
You can work on it manually as we did throughout this course,
but you can also offload tasks from your local machine
to the cloud. For example, let's say that instead of this blue in all
these places in my app, I want to use a purple color.
Because it's an app built with AI, of course, it must be
purple. But for some reason, I don't want to implement this change
locally because I need to leave my computer or anything like that.
If that code lives in a GitHub repository, which it does, I pushed
it there, I can also hand that task off to
Claude Code in the cloud. Now, to do that, at the point of
time where I'm recording this, you'll need a Pro, Max, Teams,
or Enterprise subscription, and then you can head to
claude.ai/code, and you'll end up on a screen
that probably looks something like this, and you'll need to connect
Claude, your Claude account to GitHub
so that it can access your GitHub repositories. And I'll do that here.
Now, of course, it won't have access to all your
instead, you need to connect the repositories
on. So in my case, I'll select this Claude Code
course repository and authorize access to that.
Once you did that, you need to create a cloud
environment, and I'll keep the name default here,
choose the Trusted setup here regarding network
access. If you give it full internet access, you,
maximum flexibility, and you might need that if your app, for
example, needs to send API requests and you want
all tests to run on that cloud environment, but, of course,
with full internet access, you also have all the full
internet threat, so to say. So I'll use the Trusted one here.
And now with that set up, you can either use Claude
Code in the cloud from this web interface or also from your local
client. I'll get back to that in a second.
Here, I'll first choose my repository.
I got one branch there, which I pushed to it yet at this point in
time. Choose the environment, only got one, and then you could describe
your task here. You can also choose the model that should
handle this task, you can add an image just as you can use
kick off a task here. So, for example, I could say change the main color
from blue to an elegant purple, but we can also do
this from our local client instead.
You can run /remoteenv to choose the remote
environment you want to use, and once you did that, you
can write a prompt as you always did, like this, for
example, change the main color from blue to an
components across all pages. Now, this would run
locally, but you can change this by adding an
front of it, and you'll see it switches to this
means in the cloud. And you can also run multiple tasks in the
by describing another task here. Now, these
tasks will run in parallel in the cloud, so not one task, but
multiple tasks running in parallel.
Of course, you could also just kick them off one
You can also alternatively run
claude--remote and pass your prompt
here. With this flag added, it would not
execute this task locally, but instead send it to the cloud right
away. So as you see here, it now created a remote session
to change this color from blue to purple, and I can click this
link to see that session, also get
notifications if I want to. And now it's working just
as it did locally, but now in the cloud, and what it does behind the scenes is that
it checks out that repository, that branch, works
on the code. It can also run tests there in the cloud
and once it's done, it will create a new Git commit
So it will not just push to your main branch, you probably wouldn't want
that, instead, it creates a new branch and opens a pull request
so that you can then review and merge those changes.
Now whilst it's working, it's also worth noting that you can also
combine various features from different modes.
For example, let's say we want to add a confirmation
public sharing in the app. Maybe we want to start in plan
mode. Plan mode, of course, is something we have to do locally because
need to answer some questions. So we can start
this task locally in plan mode or in any other mode
for that matter, but plan mode is something you typically want to do
have to do locally, and we can then hand that task off to
the cloud once we're done planning, for example.
So, for example, here where it's now done planning,
plan, I can continue, but then I'll hit
Escape to interrupt Claude Code, and then I can use the
ampersand symbol again and say implement the plan, but
now it will do so in the background, so in the cloud.
Now I'm getting an error here that this is not a Git repository, which is
wrong. It is. Might not occur for you anymore.
What I can, of course, do is I can use
claude--remote-c to continue that last
conversation, that is what -c does, and say
implement_the_plan, and this
will now start a remote task because this is working for me
here. For you, using this ampersand symbol might work
should. Now I will say that this Claude Code in the cloud
feature is not just a bit hard to pronounce, but has also been a bit
buggy for me, at least when trying to work with it from my local
Claude Code installation. When starting sessions from in here,
web-based interface, it worked fine, but it's absolutely
possible that it might not work the way it should right now
because it's still in beta or in research preview at the point of
time where I'm recording this, but, of course,
for you. It is, of course, a powerful feature because being able to
tasks to the cloud and offload them to the cloud can be
useful. Here, for example, it did now finish changing the main color
from blue to purple, and I could evaluate the changes
here or create a pull request. It might also do that in the future
automatically. Here, I'll do it manually,
and, of course, doing so allows me to then review those
changes and merge the pull request if I'm happy with it.
So we can take a look at the commit and see that it essentially
changed some Tailwind colors, which, of course, makes sense.
Now I'll not merge this here, but that is how you could use Claude
Code in the web.