Claude Code in the cloud: cloud sessions explained
Claude Code cloud sessions explained: how to start one with --cloud or claude.ai/code, what config it loads from your repo, teleport, auto-fix, and limits.
You start a large migration at 6 p.m., then realize it will take an hour and you need to leave. In a terminal session, closing the laptop stops it. In a cloud session, it keeps running, and you check on it from your phone on the train.
This guide covers what cloud sessions are, how to start one, what they load from your repository, and their limits, from Anthropic's cloud sessions documentation and cloud environments documentation, checked on 16 November 2026.
What a cloud session is
A cloud session is a Claude Code session that runs on cloud infrastructure rather than your machine. By default that's an isolated VM Anthropic manages, or your organization's self-hosted environment if it routes sessions there. It keeps running after you close the laptop, and it counts toward the same usage limits as your other Claude use.
It's different from Remote Control, which lets you steer a session still running on your own machine from another device.
Starting one
| Surface | How |
|---|---|
| Browser | claude.ai/code |
| Phone | The Code tab in the Claude app |
| Desktop app | Pick an environment under Cloud when starting a session |
| Terminal | claude --cloud "task" |
| Scheduled runs | Cloud scheduled tasks each run as a cloud session |
From a terminal:
claude --cloud "Fix the flaky test in auth.spec.ts"
The VM clones your GitHub remote at your current branch, not your local working copy, so push first. Each --cloud command starts a separate session, so you can run several tasks in parallel.
Anthropic's docs suggest a pattern for bigger work: plan locally in plan mode, commit the plan to the repository, then claude --cloud "Execute the plan in docs/migration-plan.md".
What it loads from your repository
A cloud session only sees what's in the clone. From the cloud environments docs:
| Configuration | Loaded? |
|---|---|
Repo CLAUDE.md | Yes |
Repo .claude/skills/, .claude/agents/, .claude/commands/ | Yes |
Repo .claude/settings.json hooks and permission rules | Yes, in a session with one repository |
Repo .mcp.json | Yes, in a session with one repository |
| Plugins enabled in repo settings | No |
Your ~/.claude/CLAUDE.md | No |
Your ~/.claude/skills/ and other user files | No |
| MCP servers added at local or user scope | No |
The fix for anything missing is the same: commit it to the repository. Add MCP servers with claude mcp add --scope project so they land in .mcp.json, and move personal skills you need into .claude/skills/. Skills you enable on claude.ai also load automatically.
Cloud environments
Every session runs in a cloud environment: a saved configuration for network access, environment variables, and setup scripts. Your first one is a Default environment with Limited network access. Change what sessions can reach, or add a setup script that installs dependencies, in the environment settings.
Moving work between cloud and terminal
Pull a cloud session into your terminal with:
claude --teleport
It opens a picker; claude --teleport <session-id> goes to one directly. Teleport checks you're in the same repository, fetches and checks out the session's branch, and loads the conversation. Your working directory must be clean.
The handoff is one-way from the CLI: you can bring cloud sessions to a terminal, but not send an existing terminal session to the cloud. See how to resume a Claude Code session for the other options.
Auto-fix pull requests
With the Claude GitHub App installed, a cloud session can watch a pull request and respond to CI failures and review comments. When a fix is clear, Claude pushes it; when a comment is ambiguous or architecturally significant, it asks you first. Start it with /autofix-pr from a terminal on the PR's branch, or from the session's Changes card.
Anthropic's docs warn that Claude's replies post under your GitHub account, labeled as coming from Claude Code, which can trigger comment-driven automation such as Atlantis. Review that before turning it on.
Security and limits
- Isolation: each session runs in its own VM, with network access limited by default.
- Credentials: in Anthropic-hosted environments, GitHub credentials stay outside the VM, and a proxy attaches them server-side.
- GitHub only for cloning: other hosts can be sent as a local bundle, with limits.
- Shared rate limits: parallel sessions use your account's limits proportionately.
- Availability: Pro, Max, Ultra, and Team plans, and Enterprise users with the right seats. Organizations with Zero Data Retention, the HIPAA configuration, or customer-managed encryption keys can't use cloud sessions.
Where Lockstep fits
Lockstep briefs Claude Code sessions on the team's approved decisions that apply to the work, captured from PRDs, Slack, and pull requests. Its briefing runs through hooks and a login token that comes from an interactive sign-in on your machine, so it's built for local sessions; we haven't verified it inside cloud sessions. For cloud work, run lockstep brief locally and paste the brief into the task prompt.
See how it works.
Sources checked 16 November 2026
- https://code.claude.com/docs/en/claude-code-on-the-web
- https://code.claude.com/docs/en/cloud-environments
Related reading
For the desktop app's cloud option, see Claude Code desktop vs CLI vs VS Code. For running Claude in CI instead, see Claude Code GitHub Actions. For parallel local work, see Claude Code worktrees. For steering a local session instead, see Claude Code Remote Control.
Frequently asked questions
- What is a Claude Code cloud session?
- A Claude Code session that runs on cloud infrastructure instead of your machine, by default in an isolated VM Anthropic manages. It keeps running after you close your laptop, and you can check on it or steer it from a browser, the Claude app, or the desktop app.
- How do I start a Claude Code cloud session?
- At claude.ai/code, in the Code tab of the Claude mobile app, by choosing a Cloud environment in the desktop app, or from a terminal with claude --cloud followed by the task. The session clones your repository's GitHub remote at the current branch, so push local commits first.
- Do cloud sessions use my CLAUDE.md and skills?
- They use what's committed to the repository: CLAUDE.md, .claude/skills, .claude/agents, .claude/commands, and, for a session with one repository, .claude/settings.json hooks and permissions and .mcp.json. They don't use your user-level ~/.claude files or MCP servers added at local or user scope.
- Can I move a cloud session to my terminal?
- Yes, with claude --teleport, which opens a picker of your cloud sessions, or claude --teleport with a session ID. You need a clean working directory, a checkout of the same repository, and the session's branch pushed. You can't push an existing terminal session to the cloud.
- Who can use Claude Code cloud sessions?
- Pro, Max, Ultra, and Team plans, and Enterprise users with premium or Chat plus Claude Code seats. Cloned repositories need GitHub. Organizations with Zero Data Retention, the HIPAA configuration, or customer-managed encryption keys can't use them.
Keep reading