OmniscioGuidesClaude Code on the web
Claude Code on the web: run a session in the cloud
The useful thing about a cloud session is that it does not need your laptop. You describe a task, the work happens on a machine you never see, and you check on it from a browser tab, a phone, or a terminal — whichever is in front of you.
This page covers where to start one, what it clones, how to pull it back to your terminal, and the errors that stop it — including the one that catches almost everybody on the first try.
Last checked against Anthropic's Claude Code documentation on November 18, 2026. By the Omniscio team. Updated .
What a cloud session is
A cloud session is a Claude Code session that runs on cloud infrastructure instead of your machine. By default that is infrastructure Anthropic manages; an organization can route it to a self-hosted environment instead. It keeps running after you close your laptop, and you can check on it or steer it from any device.
It is not a second product with a second bill. It counts toward your plan's usage limits alongside the rest of your Claude usage, and there is no separate charge for the cloud VM.
Every session runs inside a cloud environment: a saved configuration that decides what the VM can reach on the network, which environment variables it gets, and which setup script runs before Claude starts working. If you have none yet, onboarding creates a Default environment with limited network access — which is why a build that needs to fetch packages is a question about the environment, not about the task.
Source: the introduction of Anthropic's cloud sessions page, read November 18, 2026.
What it needs first
- A plan that includes cloud sessions: Pro, Max, Ultra or Team, and on Enterprise a premium seat or a Chat + Claude Code seat. Where custom roles govern access, the role needs the cloud-sessions permission.
- GitHub connected, so a session can clone your code and push branches. Either the Claude GitHub App during web onboarding, or
/web-setupin your terminal, which sends your localghCLI token to your account. - A claude.ai sign-in. Cloud sessions are not available through third-party providers, so an API key or Console sign-in is not enough —
claude auth loginfixes it.
The two GitHub roads differ in reach: the GitHub App reaches any public repository plus the private ones it is installed on, and installing it also enables Auto-fix on those pull requests. /web-setup reaches any repository your gh token can, whether or not the App is installed.
Sources: the plan note, "GitHub authentication options" and "Unable to get organization UUID" in Anthropic's cloud sessions page, read November 18, 2026.
Four places to start one
- Browser: claude.ai/code, also called Claude Code on the web.
- Mobile: the Code tab in the Claude app.
- Desktop app: select an environment under Cloud in the environment selector.
- Terminal:
claude --cloud "Fix the authentication bug in src/auth/login.ts". The older--remotespelling still works as a deprecated alias.
Cloud scheduled tasks also run as cloud sessions, so a routine you set up is the same kind of thing as one you started by hand.
From the terminal, the CLI shows a live checklist while the container starts — cloning, running your setup script — and queues anything you type during provisioning, sending it once the session is ready.
Sources: the surfaces list and "Start a cloud session from your terminal" in Anthropic's cloud sessions page, read November 18, 2026.
The branch it actually clones
This is the one that surprises people. The cloud VM clones your current directory's GitHub remote at your current branch — not your local checkout. Local commits you never pushed, and uncommitted changes, are not in the session.
So push first. When it cannot use your branch, claude --cloud starts anyway and prints a line beginning Branch <name> is not on GitHub, naming where the session actually starts instead: a pushed commit from your branch's history, or the repository's default branch. If that starting point has what the task needs, carry on; if not, push the branch and start a new session.
There is a second road, and it is the one people miss. When you run claude --cloud from a repository with no git remote, or from a github.com repository the Claude GitHub App is not installed on, Claude Code bundles your local repository and uploads it directly. A full bundle carries the history of all branches plus uncommitted changes to tracked files, so this is the way to start from work that was never pushed — and the way to send a GitLab or Bitbucket repository, by setting CCR_FORCE_BUNDLE=1. A session started from a non-GitHub bundle cannot push results back to that remote.
One scope note: --cloud runs against a single repository at a time.
Source: "Start a cloud session from your terminal" and "Branch is not on GitHub" in Anthropic's cloud sessions page, read November 18, 2026.
Working on the session
Sessions appear in the sidebar at claude.ai/code. From there the ordinary moves work: pick a permission mode from the dropdown when you create the task or while it runs, review the changes, share the session with a teammate, archive finished work, or delete sessions permanently.
Two habits make a cloud session better. Plan locally, then execute in the cloud: work through the approach in plan mode, save the plan into the repository, commit and push, then start a cloud session that executes it. And if Claude asks a question and the session sits idle, you can still answer when you come back — up to the point the environment expires — and the session continues from your answer.
If your organization has the Claude GitHub App installed, Auto-fix also runs: it responds to pull request activity on that repository.
Sources: "Work with sessions", "Tips for cloud tasks" and "Auto-fix pull requests" in Anthropic's cloud sessions page, read November 18, 2026.
Pulling it into your terminal
Five roads lead to the same place:
claude --teleportfor an interactive picker, orclaude --teleport <session-id>to go straight to one./teleportor/tpinside an existing CLI session, which opens the same picker without restarting./tasks, thentto teleport into a background session.- Open in → Terminal from the session menu on claude.ai/code, which copies the command for you.
/teleporttyped inside the cloud session itself, which replies with the exact command to run.
Four requirements stand between you and a resumed session: a clean git state (it offers to stash), a checkout of the same repository rather than a fork, the session's branch pushed to the remote, and the same claude.ai account.
Two details matter once it lands. The terminal gets its own copy: work you do there stays local and does not appear in the cloud session, so start /remote-control in the local session if you still want to steer from a phone. And if the cloud session had compacted, the summarized messages are not copied — Claude continues from the summary, and the originals are still readable on claude.ai.
From the CLI the handoff is one-way: --teleport pulls a cloud session down, and no command pushes an existing terminal session up. The Desktop app is the exception — a local session in its Code tab can be sent to the cloud from the Open in menu. With --cloud plus -p and a session id or URL, you are instead queueing a message into that existing session.
Sources: "Continue a cloud session in your terminal", "Teleport requirements" and the handoff note under "Move tasks between terminal and cloud" in Anthropic's cloud sessions page, read November 18, 2026.
Isolation, in one list
Each cloud session is separated from your machine and from other sessions by five layers:
- An isolated VM, managed by Anthropic — or your organization's own infrastructure in a self-hosted environment, where isolation is your deployment's job.
- Network access controls, limited by default and disableable. With network access off, Claude Code can still talk to the Anthropic API, which may allow data to leave the VM.
- Credential protection, in Anthropic-hosted environments: git credentials and signing keys stay outside the sandbox, and a proxy authenticates on the session's behalf with scoped credentials. A self-hosted environment supplies its own git credentials.
- Network secrets added to a cloud environment stay outside the sandbox too, attached to matching requests after they leave the session.
- Analysis inside the sandbox: code is analyzed and modified within the isolated environment before a pull request is created.
Source: "Security and isolation" in Anthropic's cloud sessions page, read November 18, 2026.
When it will not start
- Session creation failed, or provisioning stalls. Claude Code could not allocate a VM. Check status.claude.com, retry after a minute — capacity is provisioned on demand — and confirm the GitHub connection can reach the repository.
- Your new session couldn't start. Your prompt is back in the box: either the connection dropped, so check the network and any VPN or proxy, or the server erred and a retry usually works.
- Unable to get organization UUID. You are signed in with an API key or a Console account, or the stored details are stale. Run
claude auth login, or/logininside a session, and retry. - Cloud sessions are disabled by your organization's policy. An Owner has not enabled them; the message says so and names the path to ask.
- Environment expired. The VM is reclaimed after inactivity. Reopening restores the conversation history but not the background work: shell commands and subagents that were running stop and Claude is told which ones, while session-scoped scheduled tasks and a waiting
/loopdo not carry over.
One more error is worth knowing because it looks like a network problem: Couldn't verify your organization's policy for cloud sessions means Claude Code has not finished loading your organization's policy, so it refuses the send rather than assume cloud sessions are allowed.
Sources: "Troubleshooting" and "Errors when sending to a cloud session" in Anthropic's cloud sessions page, read November 18, 2026.
What it cannot do
- Share rate limits. Cloud sessions share rate limits with all other Claude and Claude Code usage on the account, and parallel tasks consume more proportionately.
- Push to a non-GitHub remote. Cloning in Anthropic-hosted environments and pull request creation need GitHub. A GitLab, Bitbucket or other repository can be sent as a local bundle, but the session cannot push results back to that remote.
- Arrive from a terminal session. The handoff is one-way, as above.
- Keep running forever. Commands and SessionStart hooks have default timeouts, a setup script is cached only when it finishes in roughly five minutes, and an idle environment expires.
Source: "Limitations" in Anthropic's cloud sessions page, read November 18, 2026.
Where these answers come from
- Everything on this page: Use Claude Code in the cloud, read November 18, 2026.
- The first-run walkthrough: Get started with cloud sessions.
- What the environment allows: Cloud environments.
- Steering a local session from another device instead: Remote Control.
- Running several cloud sessions at once: many coding agents at once.
Common questions
Does a cloud session keep running when I close my laptop?
Yes. It runs on cloud infrastructure, not your machine, so you can close the laptop and check on it later from a browser, the Claude app or a terminal.
Can I push a terminal session into the cloud?
No. --teleport pulls a cloud session down; nothing pushes an existing terminal session up. --cloud starts a new cloud session for the current repository.
Where does a cloud session get my code?
By default from your repository's GitHub remote at your current branch, so unpushed commits and uncommitted changes are not there — push first. When there is no git remote, or the Claude GitHub App is not installed on the repository, Claude Code bundles and uploads your local copy instead, including uncommitted changes to tracked files.
Is there a separate charge for the cloud VM?
No. The session counts toward your plan's usage limits, with no separate VM charge.