Claude Code (web)

What it is

Claude Code on the web is the browser version of Claude’s agentic coding tool. Sessions run at claude.ai/code on Anthropic-managed cloud infrastructure — or on your organisation’s self-hosted environment when it routes them there. You connect a GitHub repo, write a prompt, and Claude works on it in an isolated VM. Sessions persist after you close the browser, you can monitor them from the Claude mobile app, and you can pull one into your terminal with claude --teleport.

It’s in research preview.

Where to find it

On the web

claude.ai/code opens straight onto a Prompt box with a Send button. Directly above it sit the cloud-environment pill — reading Default until you make another — and an Add repository picker.
Under the prompt box: the permission-mode control, which reads Auto; a model selector; an effort control; a dictation button (Press and hold to record) with its own Dictation settings; and a usage readout.
Your sessions are listed in the sidebar. Routines — saved configurations that run on a schedule, an API call, or a GitHub event — are created and managed at claude.ai/code/routines according to Anthropic’s docs, and each routine also has a detail route of its own.
Each session shows a diff indicator such as +42 -18. Open it to read the diff and leave inline comments on specific lines, which go to Claude with your next message.

How to use it

First-time setup

Visit claude.ai/code.
Connect GitHub one of two ways:
- Authorise the Claude GitHub App during browser onboarding. It reaches any public repo plus the private repos it’s installed on, and it’s what Auto-fix needs.
- Run /web-setup in your terminal to send your local gh CLI token to your Claude account. That reaches anything your gh token can, App or no App. On Team and Enterprise plans this is hidden until an Owner turns on Quick web setup at Admin settings → Claude Code.
Onboarding sets up a Default cloud environment with Trusted network access. An environment controls network access, environment variables, and a setup script; you can add more and pick per session.

Start a session from the web

Pick a repository with Add repository, and check the environment pill next to it is the one you want.
Write your prompt and press Send.
Adjust the permission mode from the mode control if you don’t want the Auto default — you can change it while the session runs.
Watch Claude work. Leave inline comments on the diff to steer it, then open a pull request when it’s done.

Start from your terminal

claude --cloud "your prompt" creates a cloud session for the current repository. Each call is independent, so you can run several in parallel. (--remote still works as a deprecated alias.) The VM clones your GitHub remote at your current branch, so push local commits first.
claude -p "your message" --cloud <session-id> queues a follow-up into a running session from any machine you’re signed in on.
/tasks lists your background sessions; press t to teleport into one.
claude --teleport pulls a cloud session down to your terminal, or /teleport (/tp) inside an existing session does the same without restarting. From the web, Open in → Terminal in the session menu copies the command for you.

Good to know

Sessions start in Auto mode. On Pro, Max, and Team plans the built-in starting permission mode is auto: rather than prompting you, a classifier model checks each tool call for risky actions and prompt injection, runs the ones it assesses as lower-risk, and blocks the rest. The mode that puts every action in front of you is called Manual.
Branch push rules. Claude always pushes to branches prefixed claude/. If your prompt sends it to a different branch, the push is rejected when that branch is protected on GitHub, when someone else has an open pull request from it, or when it carries commits authored by someone other than you.
Auto-fix pull requests. Claude can watch a PR and respond to CI failures and review comments. Turn it on with Auto-fix in the CI status bar of a web session, with /autofix-pr from the terminal while on the PR’s branch, or by pasting any PR URL into a session and asking. It needs the Claude GitHub App. Claude may reply to review threads using your GitHub account — each reply is labelled as coming from Claude Code — so check for comment-triggered automation before enabling it.
Session sharing. Pro and Max accounts share as Private or Public, and repository-access verification is off by default, so check a session for credentials before you share it. Team and Enterprise accounts share as Private or Team, with repository-access verification on by default. Change either under Settings → Claude Code → Sharing settings.
Archiving and deleting. Hover a session in the sidebar for the archive icon; deleting is permanent and is done from the archived filter or the session’s own menu.
Context. /compact and /context work in cloud sessions, and auto-compaction runs on its own. /clear doesn’t — start a new session instead. Commands that open a terminal picker, such as /model and /effort, take the value as an argument here.
Isolation. Each Anthropic-hosted session runs in its own VM with network access limited by default, and git credentials and signing keys stay outside the sandbox behind an authenticating proxy.
Rate limits are shared with the rest of your Claude and Claude Code usage, and running tasks in parallel consumes them proportionately. There’s no separate compute charge for the VM.
GitHub is required for cloning and pull requests; GitHub Enterprise Server is supported on Team and Enterprise plans. You can send a GitLab or Bitbucket repo up as a local bundle with CCR_FORCE_BUNDLE=1, but the session can’t push results back to it.
Organisations with Zero Data Retention can’t use cloud sessions, and organisations using IP allowlisting will find every Anthropic-hosted session fails authentication until Anthropic support exempts the service.
Routines are the scheduled and event-driven version of all this, at claude.ai/code/routines or via /schedule in the CLI. See Scheduled tasks.

What’s changed recently

2026-09-13 — Auto is now the default permission mode on Pro, Max, and Team, per Anthropic’s permission-modes documentation: a classifier screens each tool call instead of prompting you, and the review-everything mode is now called Manual. The landing page’s chrome is documented for the first time — the environment pill, the Add repository picker, the Prompt box, and the dictation and usage controls beneath it.
2026-09-13 — Rewritten from the current docs. --cloud has replaced --remote, and you can now queue a follow-up into a running session with claude -p "…" --cloud <session-id>. Sessions can be routed to an organisation’s self-hosted environment instead of Anthropic’s. The branch rule is documented differently: rather than an Allow unrestricted branch pushes per-repo setting, pushes outside claude/ are rejected only when the branch is protected, carries someone else’s open PR, or has commits by another author — so we’ve removed the old setting, which no current doc mentions. Sharing defaults differ by plan tier: repository-access verification is on by default for Team and Enterprise and off for Pro and Max. Removed as unsupported: the per-session vCPU/RAM/disk ceilings, the Side chat panel, the tile/split workspace controls, and the default-model reading — none appear in the current documentation, and none is on the claude.ai/code landing page. They described an open session, which a sweep can’t enter without opening somebody’s work, so treat them as undocumented rather than proven gone.