Claude Code on the Web: How to Use It at claude.ai/code

Claude Code on the web runs coding tasks in the cloud from claude.ai/code. How to connect GitHub, set up environments, move sessions and open pull requests.

Josh Pocock8 min read

Claude Code web cover

AI Coding

Claude Code web

Stride AI Academy

Claude Code on the web is Claude Code running in a cloud virtual machine that you control from your browser at claude.ai/code. You connect GitHub, pick a repository, describe a task, and Claude clones the repo, makes the changes, runs tests and pushes a branch you can turn into a pull request. The session keeps running after you close your laptop, and it's included on the Pro, Max, Ultra and Team plans, plus Enterprise users with premium seats or Chat + Claude Code seats.

This guide covers setup, tasks, environments, network access, teleporting, pull requests and limits. Everything here was checked against Anthropic's Claude Code in the cloud docs, the cloud quickstart and the cloud environments docs on November 18, 2026. Anthropic now mostly calls these "cloud sessions", and you can start one from the browser, the Claude mobile app, the Desktop app or the terminal.

Who can use it and what it costs

Where claude.ai/code, the Code tab in the Claude app, the Desktop app, claude --cloud
Plans Pro, Max, Ultra, Team, and Enterprise premium or Chat + Claude Code seats
Cost Counts toward your plan's usage limits, no separate charge for the VM
Code host GitHub (GitHub Enterprise Server on Team and Enterprise)
Not available Organizations with Zero Data Retention, the HIPAA configuration or customer-managed encryption keys

Running several tasks at once uses your limits faster, since cloud sessions share rate limits with the rest of your Claude usage. Our Claude Code pricing guide explains how plan usage works.

How to set up Claude Code on the web

  1. Go to claude.ai/code and sign in with your claude.ai account.
  2. Connect GitHub. Follow the prompt to GitHub's authorization page and approve it.
  3. Install the Claude GitHub App on each account or organization whose private repositories you want to use. Without it, sessions can clone public repos only. Installing it also turns on auto-fix for pull requests.
  4. Get a Default environment. On Pro, Max and Ultra it's created for you. On Team and Enterprise, onboarding shows a Create your first cloud environment form: keep the defaults and click Create & finish.

On Team and Enterprise, an Owner must first turn on the GitHub connector at Organization settings > Connectors.

Connect from your terminal instead

If you already use the GitHub CLI, you can skip the browser step:

Terminal
gh auth login

Then, inside Claude Code (signed in with your claude.ai account, not an API key), run:

/web-setup

This stores your gh token, encrypted, with your Claude account, so cloud sessions reach any repository that token can. On Team and Enterprise, it's hidden until an Owner turns on Quick setup. Disconnect GitHub at claude.ai/customize/connectors to remove it. More in our guide to Claude Code with GitHub.

How to start a task

  1. Pick a repository in the selector under the message box. You can add more than one, and change the branch in the control next to it.
  2. Pick a permission mode. Cloud sessions offer Auto (a classifier reviews each action), Accept edits (Claude edits and pushes without stopping) and Plan (Claude proposes an approach and waits for your approval). Manual and bypass modes aren't available. Our plan mode guide explains when planning first pays off.
  3. Describe the task and press Enter. Name the file or function, paste error output, and say what should happen.

Each task gets its own session and branch, and closing the tab doesn't stop it.

What happens when you submit a task

  1. 1You submit a task at claude.ai/code
  2. 2Repo is cloned into a cloud VMSetup script runs if you have one
  3. 3Claude edits, runs tests and checks its work
  4. 4Branch is pushed for you to review

Cloud environments and setup scripts

Every session runs in a cloud environment: a saved configuration of network access, environment variables and a setup script. The Default environment has Limited network access and nothing else configured.

Add or edit environments from the selector under the message box on the new-session screen. The image already includes Python 3 with pip, uv and pytest, and Node.js 20, 21 and 22 with npm, yarn, pnpm and bun, among other toolchains.

Setup scripts. A Bash script that runs as root on Ubuntu 24.04 before Claude starts. Use it for tools that aren't pre-installed:

Terminal
#!/bin/bash
apt update && apt install -y shellcheck

Rules for setup scripts:

  • It must exit zero, or the session fails to start or starts without what failed. Add || true to non-critical lines.
  • Keep it under roughly five minutes. Then the filesystem is snapshotted and reused, so later sessions skip the script. Slower scripts aren't cached.
  • The environment's variables aren't set yet when it runs.
  • The cache rebuilds when you change the script or allowed hosts, and after roughly seven days.

For project setup that should also run locally, like npm install, Anthropic suggests a SessionStart hook in the repo's .claude/settings.json instead. Our hooks tutorial covers those.

Environment variables use .env format, one KEY=value per line. Anyone who uses the environment can read them, so don't put secrets there. Store API keys as network secrets, which are attached to matching requests after they leave the session, so Claude never sees them.

Network access settings

Level What sessions can reach
None No outbound network access. Package installs fail.
Limited (default) Package registries, GitHub and cloud SDKs when Allow package managers is checked, plus domains you list
Full Any domain

To let a session reach your own API or a client's site, choose Limited and list one domain per line under Allowed domains. A leading *. matches every subdomain. Even at None, Claude Code can still talk to the Anthropic API.

Move a session between web and terminal

You need the Claude Code CLI signed in to the same claude.ai account. If you haven't installed it, see how to install Claude Code.

Terminal to cloud. Start a new cloud session for your current repo:

Terminal
claude --cloud "Fix the authentication bug in src/auth/login.ts"

It clones your GitHub remote at your current branch, not your local files, so push first. --remote still works as an older alias. You can't push an existing terminal session to the cloud from the CLI, though the Desktop app can send one from its Open in menu.

Cloud to terminal. This is called teleporting:

Terminal
claude --teleport
claude --teleport <session-id>

Without an ID you get a picker. Inside Claude Code, /teleport or /tp does the same, and on claude.ai/code, Open in > Terminal copies the command. Teleport needs a clean working tree, a checkout of the same repository (not a fork), the session's branch pushed, and the same account. After that, the terminal has its own copy: new work there doesn't show up in the cloud session.

Review changes and create a pull request

When Claude pushes its branch, the Changes card beside the chat shows lines added and removed, such as +42 -18. Click the counts to open the diff.

  • Comment on lines. Hover a line, click +, and type. Comments are sent with your next message, so Claude knows exactly where the problem is.
  • Compare branches. The diff compares against the base branch by default. Use Compare against to pick another.
  • Open the PR. Click Create PR for a pull request with a generated title and description. Right-click it and choose Create draft PR for a draft.

The session stays live after the PR exists. Paste CI failures or reviewer comments and ask for fixes, or turn on Auto-fix from the PR's menu in the Changes card. Claude then watches for failed checks and review comments and pushes clear fixes. It can't see merge conflicts on its own, so ask it to rebase. Auto-fix replies on GitHub appear under your username, labeled as Claude Code, which can trigger comment-driven automation in your repo.

For automated reviews on every PR, see Claude Code review. For work on a schedule rather than on demand, Claude routines run as cloud sessions too.

Limits and security

  • GitHub only for cloning and PRs. GitLab or Bitbucket repos can be sent as a bundle with CCR_FORCE_BUNDLE=1 claude --cloud "...", but results can't be pushed back.
  • Your local setup doesn't come along. User-level settings and MCP servers added at local or user scope stay on your machine. Commit project-level config such as .mcp.json to the repo.
  • Idle sessions pause. After a few minutes without activity the VM pauses, and it can later be reclaimed. Reopening restores the conversation but not running background work.
  • Isolation. Each session runs in its own Anthropic-managed VM. Your GitHub credentials stay encrypted on Anthropic's servers and never enter the VM: a proxy adds them to GitHub requests.
  • Sharing. Pro, Max and Ultra sessions can be made Public to any logged-in claude.ai user, so check for code and credentials first. Team and Enterprise get Private and Team visibility.

Learn to build with Claude Code

The Stride AI Coding course teaches Claude Code and Codex for building client tools, written for non-programmers, with weekly live calls to review your builds. Many of the free guides cover Claude Code setups, and the Claude Code community is where members compare theirs.

FAQ

What is Claude Code on the web?

It's Claude Code running in an Anthropic-managed cloud VM that you use from claude.ai/code. Claude clones your GitHub repository, works on your task and pushes a branch for review, and the session keeps going after you close the tab.

Is Claude Code on the web free?

Anthropic's docs list it for paid plans only: Pro, Max, Ultra and Team, and for Enterprise users with premium or Chat + Claude Code seats. Sessions count toward your plan's usage limits with no separate charge for the VM.

How do I connect GitHub to Claude Code on the web?

Sign in at claude.ai/code and follow the prompt to authorize GitHub, then install the Claude GitHub App on accounts with private repos. If you use the GitHub CLI, you can run /web-setup inside Claude Code instead.

How do I move a web session to my terminal?

Run claude --teleport for a picker or claude --teleport <session-id> for a specific session, from a clean checkout of the same repository. Inside Claude Code, /teleport or /tp does the same.

Can Claude Code on the web access the internet?

It depends on the environment's network level. The default, Limited, allows package registries, GitHub, cloud SDKs and domains you add. You can switch an environment to None or Full.

Does Claude Code on the web work with GitLab?

Not fully. Cloning and pull requests need GitHub. You can upload a GitLab or Bitbucket repo as a bundle with CCR_FORCE_BUNDLE=1, but the session can't push changes back to that remote.

Build it with us in Stride AI Academy

Four courses, weekly live calls and a community of people building and selling AI. Or start with 310+ free guides.

Keep reading

Free AI Coding guides