Use Claude Code on the web
> ## Documentation Index > Fetch the complete documentation index at: https://code.claude.com/docs/llms.txt > Use this file to discover all available pages before exploring further.
Overview
Documentation Index
Fetch the complete documentation index at: https://code.claude.com/docs/llms.txt Use this file to discover all available pages before exploring further.
Use Claude Code on the web
Configure cloud environments, setup scripts, network access, and Docker in Anthropic's sandbox. Move sessions between web and terminal with
--remoteand--teleport.
Claude Code on the web is in research preview for Pro, Max, and Team users, and for Enterprise users with premium seats or Chat + Claude Code seats.
Claude Code on the web runs tasks on Anthropic-managed cloud infrastructure at claude.ai/code. Sessions persist even if you close your browser, and you can monitor them from the Claude mobile app.
New to Claude Code on the web? Start with Get started to connect your GitHub account and submit your first task.
This page covers:
- GitHub authentication options: two ways to connect GitHub
- The cloud environment: what config carries over, what tools are installed, and how to configure environments
- Setup scripts and dependency management
- Network access: levels, proxies, and the default allowlist
- Move tasks between web and terminal with
--remoteand--teleport - Work with sessions: reviewing, sharing, archiving, deleting
- Auto-fix pull requests: respond automatically to CI failures and review comments
- Security and isolation: how sessions are isolated
- Limitations: rate limits and platform restrictions
GitHub authentication options
Cloud sessions need access to your GitHub repositories to clone code and push branches. You can grant access in two ways:
| Method | How it works | Best for |
|---|---|---|
| GitHub App | Install the Claude GitHub App on specific repositories during web onboarding. Access is scoped per repository. | Teams that want explicit per-repo authorization |
/web-setup | Run /web-setup in your terminal to sync your local gh CLI token to your Claude account. Access matches whatever your gh token can see. | Individual developers who already use gh |
Either method works. /schedule checks for either form of access and prompts you to run /web-setup if neither is configured. See Connect from your terminal for the /web-setup walkthrough.
The GitHub App is required for Auto-fix, which uses the App to receive PR webhooks. If you connect with /web-setup and later want Auto-fix, install the App on those repositories.
Team and Enterprise admins can disable /web-setup with the Quick web setup toggle at claude.ai/admin-settings/claude-code.
Organizations with Zero Data Retention enabled cannot use /web-setup or other cloud session features.
The cloud environment
Each session runs in a fresh Anthropic-managed VM with your repository cloned. This section covers what's available when a session starts and how to customize it.
What's available in cloud sessions
Cloud sessions start from a fresh clone of your repository. Anything committed to the repo is available. Anything you've installed or configured only on your own machine is not.
| Available in cloud sessions | Why | |
|---|---|---|
Your repo's CLAUDE.md | Yes | Part of the clone |
Your repo's .claude/settings.json hooks | Yes | Part of the clone |
Your repo's .mcp.json MCP servers | Yes | Part of the clone |
Your repo's .claude/rules/ | Yes | Part of the clone |
Your repo's .claude/skills/, .claude/agents/, .claude/commands/ | Yes | Part of the clone |
Plugins declared in .claude/settings.json | Yes | Installed at session start from the marketplace you declared. Requires network access to reach the marketplace source |
Your user ~/.claude/CLAUDE.md | No | Lives on your machine, not in the repo |
| Plugins enabled only in your user settings | No | User-scoped enabledPlugins lives in ~/.claude/settings.json. Declare them in the repo's .claude/settings.json instead |
MCP servers you added with claude mcp add | No | Those write to your local user config, not the repo. Declare the server in .mcp.json instead |
| Static API tokens and credentials | No | No dedicated secrets store exists yet. See below |
| Interactive auth like AWS SSO | No | Not supported. SSO requires browser-based login that can't run in a cloud session |
To make configuration available in cloud sessions, commit it to the repo. A dedicated secrets store is not yet available. Both environment variables and setup scripts are stored in the environment configuration, visible to anyone who can edit that environment. If you need secrets in a cloud session, add them as environment variables with that visibility in mind.
Installed tools
Cloud sessions come with common language runtimes, build tools, and databases pre-installed. The table below summarizes what's included by category.
| Category | Included |
|---|---|
| Python | Python 3.x with pip, poetry, uv, black, mypy, pytest, ruff |
| Node.js | 20, 21, and 22 via nvm, with npm, yarn, pnpm, bun¹, eslint, prettier, chromedriver |
| Ruby | 3.1, 3.2, 3.3 with gem, bundler, rbenv |
| PHP | 8.4 with Composer |
| Java | OpenJDK 21 with Maven and Gradle |
| Go | latest stable with module support |
| Rust | rustc and cargo |
| C/C++ | GCC, Clang, cmake, ninja, conan |
| Docker | docker, dockerd, docker compose |
| Databases | PostgreSQL 16, Redis 7.0 |
| Utilities | git, jq, yq, ripgrep, tmux, vim, nano |
¹ Bun is installed but has known proxy compatibility issues for package fetching.
For exact versions, ask Claude to run check-tools in a cloud session. This command only exists in cloud sessions.
Work with GitHub issues and pull requests
Cloud sessions include built-in GitHub tools that let Claude read issues, list pull requests, fetch diffs, and post comments without any setup. These tools authenticate through the GitHub proxy using whichever method you configured under GitHub authentication options, so your token never enters the container.
The gh CLI is not pre-installed. If you need a gh command the built-in tools don't cover, like gh release or gh workflow run, install and authenticate it yourself:
Add `apt update && apt install -y gh` to your [setup script](#setup-scripts).
Add a `GH_TOKEN` environment variable to your [environment settings](#configure-your-environment) with a GitHub personal access token. `gh` reads `GH_TOKEN` automatically, so no `gh auth login` step is needed.
Link artifacts back to the session
Each cloud session has a transcript URL on claude.ai, and the session can read its own ID from the CLAUDE_CODE_REMOTE_SESSION_ID environment variable. Use this to put a traceable link in PR bodies, commit messages, Slack posts, or generated reports so a reviewer can open the run that produced them.
Ask Claude to construct the link from the environment variable. The following command prints the URL:
echo "https://claude.ai/code/${CLAUDE_CODE_REMOTE_SESSION_ID}"
Run tests, start services, and add packages
Claude runs tests as part of working on a task. Ask for it in your prompt, like "fix the failing tests in tests/" or "run pytest after each change." Test runners like pytest, jest, and cargo test work out of the box since they're pre-installed.
PostgreSQL and Redis are pre-installed but not running by default. Ask Claude to start each one during the session:
service postgresql start
service redis-server start
Docker is available for running containerized services. Ask Claude to run docker compose up to start your project's services. Network access to pull images follows your environment's access level, and the Trusted defaults include Docker Hub and other common registries.
If your images are large or slow to pull, add docker compose pull or docker compose build to your setup script. The pulled images are saved in the cached environment, so each new session has them on disk. The cache stores files only, not running processes, so Claude still starts the containers each session.
To add packages that aren't pre-installed, use a setup script. The script's output is cached, so packages you install there are available at the start of every session without reinstalling each time. You can also ask Claude to install packages mid-session, but those installs don't carry over to other sessions.
Resource limits
Cloud sessions run with approximate resource ceilings that may change over time:
- 4 vCPUs
- 16 GB of RAM
- 30 GB of disk
Tasks requiring significantly more memory, such as large build jobs or memory-intensive tests, may fail or be terminated. For workloads beyond these limits, use Remote Control to run Claude Code on your own hardware.
Configure your environment
Environments control network access, environment variables, and the setup script that runs before a session starts. See Installed tools for what's available without any configuration. You can manage environments from the web interface or the terminal:
| Action | How |
|---|---|
| Add an environment | Select the current environment to open the selector, then select Add environment. The dialog includes name, network access level, environment variables, and setup script. |
| Edit an environment | Select the settings icon to the right of the environment name. |
| Archive an environment | Open the environment for editing and select Archive. Archived environments are hidden from the selector but existing sessions keep running. |
Set the default for --remote | Run /remote-env in your terminal. If you have a single environment, this command shows your current configuration. /remote-env only selects the default; add, edit, and archive environments from the web interface. |
Environment variables use .env format with one KEY=value pair per line. Don't wrap values in quotes, since quotes are stored as part of the value.
NODE_ENV=development
LOG_LEVEL=debug
DATABASE_URL=postgres://localhost:5432/myapp
Setup scripts
A setup sc