At a glance
WHAT IT’S REALLY ABOUT
Cloud sessions keep Claude Code running after you close your laptop
- The video demonstrates Claude Code “cloud sessions,” where Claude continues working in a cloud VM even after your laptop is closed, and you can check in from the Claude phone app.
- A cloud session clones your GitHub repository into a fresh environment, works on its own branch, and counts toward the same plan limits as local sessions with no extra VM charge.
- You can start cloud sessions from multiple surfaces (desktop, browser, terminal, phone, Slack) and use them for long tasks or ideas that arise while you’re away from your computer.
- Setting up requires connecting GitHub and installing the Claude GitHub app with repo permissions, after which you can choose repos, environments, and branches when starting sessions.
- The workflow supports mobile diff review and PR creation, PR monitoring for checks and review feedback, and an optional “teleport” mode to pull the cloud session into your local terminal.
IDEAS WORTH REMEMBERING
5 ideasCloud sessions let Claude keep coding while your computer is off.
A cloud session runs Claude Code in a hosted virtual machine that clones your GitHub repo and works on its own branch, so work continues even if your laptop is closed or asleep.
Use cloud sessions for long-running or “away-from-laptop” work.
They’re best for longer tasks (refactors, migrations) or whenever you’re away from your computer; you can start work before leaving and review results later, including from your phone.
Parallel work is easier because every session gets its own branch.
Because each session operates on its own branch, you can run multiple tasks in parallel without juggling local worktrees or keeping multiple environments running.
GitHub access is required so Claude can clone and create branches/PRs.
Setup requires connecting your GitHub account and installing the Claude GitHub app with repo permissions; private repos only appear once the app has access.
Environments are configurable—from prebuilt defaults to custom and self-hosted.
Sessions start with a standard cloud environment (common runtimes/tools/databases), but you can define custom environments with network access, env vars, and setup scripts; Team/Enterprise can run on their own infrastructure.
WORDS WORTH SAVING
5 quotesWatch 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 he has a question for me. I answer it, and Claude carries on, even though my laptop has been asleep the whole time. This is a cloud session.
— Unknown
In a cloud session, Claude clones your repo from GitHub into a virtual machine and works on its own branch.
— Unknown
Use a cloud session when a task will take longer than you'll be at your laptop, like a large refactor or a migration.
— Unknown
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.
— Unknown
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.
— Unknown
High quality AI-generated summary created from speaker-labeled transcript.
