Claude Code on the Web — 5 ways to run remote
This is the one that made everyone gasp. Claude Code stops running on your laptop and runs on Anthropic’s machines instead — in a ready-made sandbox. You can fire off ten tasks at once, drive it from your phone, or just tag @claude on a GitHub issue and walk away.
Sandboxing (13.2) kept things on your machine. Now we cut the cord. This approach goes by several names — remote execution, Claude Code on the Web — but the idea is one thing: the work happens somewhere else, already sandboxed, on Anthropic’s infrastructure.
01The big idea: a managed cloud sandbox
“Managed” means Anthropic runs and babysits the box; “cloud sandbox” means it is remote and isolated. You send a task; a fresh Claude Code spins up out there, does the work, and reports back. Two things make this genuinely exciting:
Ten tasks at once
Like pressing the “+” button to run many Claudes — except they run on Anthropic’s boxes, not yours. Your laptop stays idle.
Work on the move
Punch an instruction into your phone, it runs in the cloud, and you pick up on your laptop when you get home. Your whole conversation context travels with the task.
Because the cloud box needs your code, everything is organised through GitHub: your work must be committed and pushed. The cloud Claude clones the repo, works on it, and pushes a branch back for you to review as a Pull Request.
02One-time setup: connect GitHub
There is a little plumbing the first time. Do it once and forget it. (Anthropic tweaks this flow often — always check the course resources for the current steps.)
Connect Claude to GitHub
Go to claude.ai/code → Connect to GitHub → authorise. Then Connect repositories and install the Claude Code GitHub app into the repo(s) you choose (only-selected, or all — your call).
Install the GitHub CLI
Back in Claude Code, run /install-github-app. It will complain if gh is missing and hand you the exact install command for Mac, Windows or Linux. Install it, then gh auth login and complete the browser + one-time-code flow.
Commit your code
git add . then git commit so git status is clean. The cloud needs your work pushed.
Install the workflows
Run /install-github-app again, pick the repo, and when prompted tick both GitHub workflows (space-bar toggles). Choose the long-lived token that comes with your Claude subscription, authorise, and let it open GitHub.
Merge the setup PR
GitHub shows a Pull Request that adds the workflow files. Create pull request → Merge → Confirm.
You added two YAML files — .github/workflows/claude.yml and claude-code-review.yml — to your repo. These are the bridge that lets you tag Claude on an issue and have it take over. Setup complete.
03Five ways to run remotely
With the bridge in place, here are all five doors into the cloud. Some may be briefly flaky (it is a research preview) — try each so you know they exist.
| # | How | What you do |
|---|---|---|
| 1 | Ampersand prefix | In a normal Claude Code session, put & before your instruction. It doesn’t run locally — the whole conversation is shipped to the cloud and runs there. |
| 2 | Command line | From your terminal: claude --remote "…your task…". Off it goes to a remote session. |
| 3 | Browser | Go to claude.ai/code, pick your repo, type a task. A little Claude Code runs in the cloud and pushes a PR. |
| 4 | Mobile app | Claude app → Code tab → New session. Exactly the browser experience, from your phone. Fire off features over dinner. |
| 5 | GitHub issue | Open an issue, describe the task, tag @claude. Anthropic spins up Claude in the cloud to do it. ⭐ the star of the show. |
# way 1 — inside a Claude Code session: > & redo my README and write a fresh architecture doc # runs in the cloud; use /tasks to see everything running remotely # way 2 — straight from PowerShell / bash: claude --remote "read planning/*.md then design the market-data backend"
/tasks is your control towerKick off several remote jobs, then run /tasks to see them all — the cloud equivalent of having many terminals open. They run in parallel while your machine does nothing.
04The star: an issue tagged @claude
This is the workflow to fall in love with. You write a GitHub issue like any ticket, add @claude, press create — and seconds later Claude Bot posts a to-do list and starts working. It reads your planning docs, writes code, runs tests, and opens a PR. You did nothing but describe the work.
Remember setting up Jira tickets? Picture that, but every ticket becomes a tagged GitHub issue and Claude clears them in the cloud while you sleep. That is the workflow this whole setup was worth it for.
05Honest notes (it’s a research preview)
- Slower than local. Writing a document might take ~10 minutes in the cloud. Be patient.
- A little flaky. A session can stop early — just ask again and wait. It is labelled a research preview for a reason, and will steadily stabilise.
- Full context travels. When you kick a job to the cloud, the entire conversation so far is sent along, so it continues seamlessly.
- Always review the PR. The cloud does the typing; you decide what merges.
✓ Key takeaways
- Managed cloud = Anthropic runs Claude Code for you in a remote sandbox; it’s tied to GitHub.
- Set up once: connect GitHub, install the app +
ghCLI, tick the two workflows, merge the setup PR. - Five ways in:
&prefix,claude --remote, browser, mobile, and@claudeon an issue. - The
@claudeissue flow returns a reviewable PR — raise many issues for parallel work. - It’s a preview: a bit slow and flaky, but the full conversation context travels with each job.