Claude Code on the Web

0:15 Claude Code on the web runs Claude Code tasks on virtual machines that Anthropic manages: you open claude.ai/code, pick a GitHub repository and describe the task, and Claude clones the code, does the work and pushes a branch you can turn into a pull request, while your own computer can be closed (Use Claude Code in the cloud). Anthropic now calls these "cloud sessions". They are available on Pro, Max, Ultra and Team plans and to Enterprise users with premium seats or Chat + Claude Code seats, count toward the plan's ordinary usage limits, and carry no separate charge for the machine. The same sessions start from the Code tab of the Claude mobile app, from the desktop app and from the terminal with claude --cloud. Anthropic launched the feature in beta on Oct 20, 2025 and made it generally available on Sep 23, 2026.

Quick facts

Sources: Use Claude Code in the cloud, Configure cloud environments, Claude Code on the web, read Nov 6, 2026.

What are cloud sessions for?

0:41 A cloud session is the same Claude Code agent with the same tools, run on a fresh machine instead of your laptop. It suits work that takes a while and needs no hands on your keyboard: fixing a flaky test, updating documentation, a refactor across many files, a bug report pasted from an issue. Because each session is its own machine, several can run in parallel without touching each other or your working copy, and they keep going if you close the browser or the lid (Use Claude Code in the cloud). The trade is access: a cloud session sees only what is committed to the repository and what its environment allows, not the files, tools and logins on your own computer. For steering a session that runs on your own machine from your phone, Anthropic offers Remote Control instead (Remote Control).

How to start a cloud session

1. Sign in at claude.ai/code with a plan that includes cloud sessions.
2. Connect GitHub. The usual way is to authorize the Claude GitHub App during onboarding; developers who already use GitHub's gh tool can instead run /web-setup in a local Claude Code session to send its token to their Claude account.
3. Pick a repository and an environment (onboarding creates one named Default).
4. Describe the task and choose a permission mode: Accept edits, Plan or Auto.
5. Watch, answer questions, or leave. When Claude has pushed its changes, the Changes card shows the lines added and removed, such as +42 -18; click it to review the diff, comment on lines, and create the pull request.

Sources: Use Claude Code in the cloud, Claude Code Desktop, read Nov 6, 2026.

1:09 The GitHub App reaches public repositories and the private ones it is installed on; /web-setup reaches whatever your gh token can. Auto-fix and Claude Code's projects need the app installed. Either way, in Anthropic's hosted environments your GitHub credentials stay on Anthropic's servers and a proxy attaches them to git operations, so they never enter the session's machine.

Starting from the terminal or the phone

From a repository on your own machine, claude --cloud "Fix the authentication bug in src/auth/login.ts" starts a new cloud session. It clones the branch from GitHub, not your local copy, so unpushed commits are missing until you push (Use Claude Code in the cloud). A repository with no GitHub remote, or one the GitHub App is not installed on, is uploaded instead as a git bundle under 100 MB, untracked files left out; on macOS, Linux and WSL, uncommitted changes to files such as .env and private keys are held back, but on native Windows they upload as they are. Anthropic's suggested pattern is to plan locally in plan mode, commit the plan, then send the execution to the cloud. claude -p "message" --cloud <session-id> posts a follow-up into a running session from any machine.

2:51 On a phone, the Code tab of the Claude app starts and steers the same sessions; Anthropic is explicit that Claude Code has no separate mobile app and that no code runs on the phone (Claude Code on mobile).

How do I move a cloud session to my terminal?

3:37 Run claude --teleport for a list of your cloud sessions, or claude --teleport <session-id> for one; inside Claude Code, /teleport (or /tp) does the same (Use Claude Code in the cloud). Teleport checks four things first: a clean working directory (it offers to stash), a checkout of the same repository rather than a fork, a session branch that was pushed, and the same claude.ai account. It then fetches the branch and loads the conversation. The terminal gets its own copy, so later work there does not appear in the cloud session. Teleport needs a claude.ai sign-in: with an API key or a Console account it fails with "Unable to get organization UUID" until you run claude auth login. Handoff from the CLI runs one way only; a terminal session cannot be pushed to the cloud, though the desktop app's Open in menu can send one of its local sessions there.

Cloud environments

1:39 Every session runs in an environment, a saved setup with three parts: network access, environment variables and a setup script (Configure cloud environments). Network access has four levels:

Source: Configure cloud environments, read Nov 6, 2026.

Even at None, Claude Code still talks to Anthropic's API, which Anthropic notes could carry data out. A setup script runs as root on Ubuntu 24.04, so apt install works; when it finishes in about five minutes, Anthropic snapshots the result and later sessions start from it. API keys can be stored as network secrets, which a proxy adds to requests for the hosts you name without the session ever seeing them. Each machine has 4 vCPUs, 16 GB of RAM and 30 GB of disk and comes with Python, Node.js 20 to 22, Ruby, PHP 8.3, Java 21, Go, Rust, C and C++ toolchains, Docker, PostgreSQL 16, Redis 7.0 and Chrome for Testing. Toolchains outside that list, such as .NET, need the setup script.

What carries over from your own setup is only what is committed: the repository's CLAUDE.md, .claude/ rules, skills, agents and commands, and, for a single repository, its hooks, permission rules and .mcp.json. Your personal ~/.claude/CLAUDE.md, your own skills and MCP servers added at user scope stay on your machine, and plugins are not installed (Configure cloud environments).

Auto-fix, scheduled tasks and projects

With the Claude GitHub App installed, Claude can watch a pull request and respond to failed CI checks and review comments, pushing a fix when one is clear and asking when a comment is ambiguous; turn it on from the pull request's menu in the Changes card or run /autofix-pr in the terminal (Use Claude Code in the cloud). Its replies on GitHub appear under your account, labeled as written by Claude Code, and Anthropic warns that they can set off comment-triggered automation such as Atlantis. Cloud scheduled tasks, formerly called routines, run a saved prompt as a cloud session hourly, nightly, weekly, from an API call or on a GitHub event, up to 100 scheduled runs an hour per account. Projects, in public beta on Pro, Max and Ultra, let one conversation start and track a thread per task (Projects).

Limits and known problems

• GitHub only for cloning and pull requests. GitLab, Bitbucket and other hosts can be sent as an upload with CCR_FORCE_BUNDLE=1, but the session cannot push back (Use Claude Code in the cloud).
• Shared usage. Parallel sessions draw on the same five-hour and weekly limits as everything else on the plan (Claude Usage Limits).
• Idle machines are reclaimed. A session pauses after a few minutes without activity and its machine may later be reclaimed; reopening restores the conversation but not running commands, subagents or /loop tasks.
• Not for every organization. Organizations with Zero Data Retention, the HIPAA configuration or customer-managed encryption keys cannot use cloud sessions, and an organization IP allowlist blocks them unless Anthropic support grants an exemption.
• No interactive logins. Browser sign-ins such as AWS SSO cannot run in a session (Configure cloud environments).
• Fewer commands. Commands that only work in the terminal interface, such as /plugin and /resume, are not available.

Frequently asked questions

Is Claude Code on the web free? No. Claude Code cloud sessions need a Pro, Max, Ultra or Team plan or an eligible Enterprise seat, and they use the plan's normal usage with no extra charge for the cloud machine.

Does Claude Code on the web work with GitLab? Only partly. Claude Code cloud sessions clone and open pull requests on GitHub alone; a GitLab or Bitbucket repository can be uploaded as a bundle, but the session cannot push results back to it.

Can I use Claude Code on my phone? Yes. The Code tab in the Claude app for iOS and Android starts and steers Claude Code cloud sessions and Remote Control sessions, but the code runs in the cloud or on your computer, not on the phone.

What is the difference between --cloud and Remote Control? claude --cloud starts a new Claude Code session on Anthropic's machines, while Remote Control lets claude.ai or the phone app steer a session that keeps running on your own computer.

Can a Claude Code cloud session reach the internet? By default a Claude Code cloud session reaches only Trusted domains such as package registries and GitHub; an environment can be set to None, Full or a Custom list of domains.

Was Claude Code on the web renamed? Yes. Anthropic's Sep 23, 2026 update calls Claude Code on the web "cloud sessions"; the address is still claude.ai/code.

Sources

• Use Claude Code in the cloud, Claude Code Docs, read Nov 6, 2026
• Configure cloud environments, Claude Code Docs, read Nov 6, 2026
• Claude Code on mobile, Claude Code Docs, read Nov 6, 2026
• Continue local sessions from any device with Remote Control, Claude Code Docs, read Nov 6, 2026
• Automate work with scheduled tasks, Claude Code Docs, read Nov 6, 2026
• Let Claude coordinate ongoing work with Projects, Claude Code Docs, read Nov 6, 2026
• Desktop application, Claude Code Docs, read Nov 6, 2026
• Claude Code on the web, Anthropic, Oct 20, 2025, updated Sep 23, 2026
• Coding on the go with Claude Code, Claude, Oct 13, 2026 (video)