CHAPTERS
- 0:00 – 0:18
Hands-off coding demo: Claude keeps working after you close your laptop
The video opens with a quick demonstration: you give Claude a coding task, shut your laptop, and later pick up the conversation on your phone. Claude continues working in the background and can pause to ask clarifying questions that you answer from mobile.
- •Start a task on laptop, then put the laptop to sleep/close it
- •Continue the same coding session from the Claude phone app
- •Claude can ask questions mid-task and proceed after you respond
- •Sets up the concept of “cloud sessions” as the enabler
- 0:18 – 0:30
What a cloud session is (VM + GitHub clone + separate branch)
A cloud session runs Claude Code in a hosted virtual machine. Claude clones your GitHub repository and performs work on its own branch, with usage counting the same as a local session and no additional VM fee.
- •Repo is cloned from GitHub into a virtual machine
- •Work happens on a dedicated branch per session
- •Counts toward plan limits like local sessions
- •No extra charge for the VM
- 0:30 – 0:41
Where you can start cloud sessions and why they’re useful
Cloud sessions can be initiated from multiple surfaces and are best for tasks that outlast your time at your laptop. They let you kick off long-running work and return later without keeping a machine awake.
- •Start from desktop app, browser, terminal, phone, or Slack
- •Ideal for large refactors, migrations, and longer tasks
- •Start before leaving work and review results later
- •Useful when ideas strike away from your computer
- 0:41 – 1:01
Parallelizing work safely: multiple sessions without worktrees
Because each cloud session operates on its own branch, you can run several tasks in parallel. This reduces overhead compared to juggling multiple local worktrees or branches manually.
- •Each session uses its own branch isolation
- •Run multiple sessions concurrently
- •Avoid managing multiple worktrees locally
- •Helps delegate/queue multiple changes at once
- 1:01 – 1:31
Connecting GitHub: account link + Claude GitHub app permissions
To enable cloud sessions, Claude needs access to clone repositories and create branches. The setup involves connecting your GitHub account and installing the Claude GitHub app with repo-level access selection.
- •Cloud sessions require GitHub access to clone and branch
- •Step 1: connect your GitHub account and approve access
- •Step 2: install Claude GitHub app and choose accessible repos
- •Private repos appear only after the app has permission
- 1:31 – 2:01
Environments: default tooling vs custom setup and enterprise infrastructure
Sessions run in a default cloud environment with common runtimes and tools, but you can define a custom environment when needed. Teams and enterprises can also run cloud sessions on their own infrastructure.
- •Default environment includes common runtimes, build tools, databases
- •Custom environments can add network access rules and env vars
- •Setup scripts can install additional dependencies
- •Team/Enterprise can host sessions on organization infrastructure
- 2:01 – 2:32
What carries over (git state) vs what doesn’t (local machine config)
Each session starts from a fresh clone, so pushed commits are available immediately. However, machine-specific configuration like personal settings, plugins, or locally installed tools won’t exist in the cloud VM, making local Claude Code preferable for tasks that depend on them.
- •Fresh clone means committed/pushed work is available
- •Local-only installs/config (settings, skills, plugins) aren’t present
- •Choose local sessions when you need your local environment
- •Cloud sessions are designed for reproducible repo-based work
- 2:32 – 2:50
Starting a cloud session in the desktop app + example bug to fix
The walkthrough shows how to start a cloud session by selecting Cloud and choosing repo, environment, and starting branch. The example task is fixing a newsletter signup bug where invalid emails are accepted and the server request fails.
- •In desktop app: select Cloud (not Local)
- •Pick the repo, environment, and base branch
- •Example: marketing site newsletter form bug
- •Problem: invalid email passes client side, fails server request
- 2:50 – 3:02
Continuing from your phone: Code tab, answer questions, redirect work
Later, the same session is accessed on mobile via the Code tab. You can start a new task or continue the existing one, answer Claude’s questions, or steer the work in a different direction—without needing the laptop running.
- •Open Claude mobile app → Code tab
- •Continue an existing cloud session or start a new one
- •Respond to Claude’s clarifying questions
- •Steer or redirect the session and let it continue
- 3:02 – 3:19
Cloud session vs remote control: work continues without your computer
The video clarifies that cloud sessions don’t depend on your computer staying on. This is contrasted with remote control, which relies on a Claude Code session running locally and being connected remotely.
- •Cloud sessions keep running even if your computer is off/asleep
- •Not the same as remote control
- •Remote control depends on a local session running on your machine
- •Cloud sessions are fully hosted execution
- 3:19 – 3:32
Reviewing changes on mobile and creating a PR
When Claude finishes, you can review the diff on your phone and leave comments that feed into the next message to Claude. If everything looks good, you can create a pull request and open it on GitHub directly from mobile.
- •Review diffs from your phone
- •Comments you leave are passed back to Claude
- •Tap “Create PR” to open a pull request on GitHub
- •Mobile-first workflow for final verification and submission
- 3:32
After the PR: monitoring checks, responding to reviews, and teleporting to terminal
Post-PR, Claude can watch the pull request and help address failing checks and review feedback. If you prefer terminal workflows, you can “teleport” the cloud session onto your computer to continue locally.
- •Claude can monitor PR checks and review comments
- •Helps respond to failures and requested changes
- •Use terminal option: run Claude with the teleport flag
- •Teleport brings the cloud session onto your computer to continue
Wrap-up: when to hand off work to the cloud and where to learn more
The closing reinforces the core use case: hand a task off so it keeps progressing while you’re away. The viewer is prompted to start a cloud session, check in later, and consult the linked documentation for details.
- •Use cloud sessions to keep tasks running while you’re away
- •Start the task, close the laptop, check in when ready
- •Designed for asynchronous progress and handoffs
- •Docs linked for further guidance
