Coding on the go with Claude Code

0:00Watch this. I'm going to give Claude a task, and I'm going to close my laptop. Then I'm going to open the Claude app on my phone. Claude has kept working, and now it has a question for me. I answer it, and Claude carries on even though my laptop has been asleep the whole time.

0:16This is a cloud session. In a cloud session, Claude clones your repo from GitHub into a virtual machine and works on its own branch. The session counts towards your plan's limits the same way a local session does, and there's no extra charge for the virtual machine. You can start a cloud session from the desktop app, the browser, the

0:37terminal, your phone, or Slack. Use a cloud session when a task will take longer than you'll be at your laptop, like a large refactor or a migration. For instance, you can start a task before you leave work for the day and review the result in the morning without keeping your laptop awake. You can also start a cloud session when an idea comes to you while

1:00you're away from your computer. And because each session works on its own branch, you can start several at once without managing multiple worktrees. To set up a cloud session, you will need to give Claude access to your GitHub repos so that it can clone your code and create the branches. The recommended way takes two steps.

1:19First, connect your GitHub account. That takes you to GitHub, where you approve access. Second, install the Claude GitHub App and choose which repos it can access. A private repo only shows up after the app can see it. After that, your repos are available when you start a session. By default, your session runs in a cloud environment that comes

1:42pre-installed with common language runtimes, build tools, and databases. But if you need more, you can create a custom environment. You can set its network access, add environment variables, and write a setup script that installs anything else your repo needs. And on Team and Enterprise plans, your organization can run cloud sessions on its own infrastructure.

2:07Each session starts from a fresh clone of your repo. So anything you've committed and pushed is available in the session. But anything that's only installed or configured on your own computer isn't, like your personal settings, skills, and plugins. So for work that needs your local config, tools, or environment, you can run Claude Code locally instead. To start a cloud session in the desktop app, select Cloud instead of Local,

2:36then choose the repo, the environment, and the branch to start from. As a small example, we'll fix a bug on a marketing site. The newsletter sign-up form accepts an invalid email address, and the request fails on the server. A while later, I open the Claude app on my phone and go to the Code tab. I can start a completely new task from here or continue the

2:58one I started on my laptop. Claude has a question. I can answer it or steer the session in a new direction, and then Claude carries on. A cloud session doesn't need your computer to stay on. That's what makes it different from Remote Control, which connects the Claude app to a Claude Code session running on your local computer.

3:19When Claude is done, I can review the changes on my phone. Any comments I leave go back to Claude with my next message. The diff looks right, so I can tap Create PR and open the pull request on GitHub. After that, I can have Claude watch the pull request and respond to failing checks and review comments. And if you'd rather work in the terminal, you can run claude with the teleport

3:42flag to bring the cloud session onto your computer and then continue it from there. So the next time you want to hand a task off or keep one going while you're away from your computer, start a cloud session. Give Claude the task, close your laptop, and check in when you're ready. To learn more, read the docs linked below.