Claude Code Web: Cloud Sandboxes with Dev Tools & Teleport
Run Claude Code in browser cloud sessions with preloaded Python/Node/Ruby/Java/Go/Rust/Docker/DBs; configure networks/setup scripts; teleport tasks between web/terminal via --remote/--teleport for seamless local-cloud workflow.
Preloaded Tooling and Repo Fidelity in Cloud Sessions
Cloud sessions clone your repo fully, including CLAUDE.md, .claude/settings.json hooks, .mcp.json MCP servers, .claude/rules/, skills/agents/commands/. Plugins from repo settings.json install automatically if network reaches marketplace. User-local files like ~/.claude/CLAUDE.md or claude mcp add servers unavailable—declare them repo-wide instead. No static secrets or interactive auth like AWS SSO yet.
Sessions ship with extensive tools: Python 3.x (pip/poetry/uv/black/mypy/pytest/ruff), Node 20/21/22 (nvm/npm/yarn/pnpm/bun/eslint/prettier/chromedriver), Ruby 3.1-3.3 (gem/bundler/rbenv), PHP 8.4 (Composer), OpenJDK 21 (Maven/Gradle), latest Go/Rust, GCC/Clang/cmake/ninja/conan for C/C++, Docker/dockerd/compose, PostgreSQL 16, Redis 7.0, plus git/jq/yq/ripgrep/tmux/vim/nano. Run check-tools to verify.
Work GitHub issues/PRs via gh CLI: install with apt update && apt install -y gh in setup script, set GH_TOKEN env var, or gh auth login. Link artifacts back with echo "https://claude.ai/code/${CLAUDE_CODE_REMOTE_SESSION_ID}". Start services (service postgresql start, docker compose up/pull/build), run tests from tests/, add packages dynamically.
GitHub Auth and Environment Configuration
Authenticate via GitHub App (install per-repo during web onboarding for scoped access) or /web-setup (syncs local gh CLI token matching its scopes, ideal for individuals). Use /schedule for cron-like tasks.
Configure environments via web UI: add with name/network/env vars/setup script; edit/archive per env. Set default for --remote with /remote-env. Load .env files or set vars like NODE_ENV=development, DATABASE_URL=postgres://localhost:5432/myapp. Setup scripts run pre-launch (e.g., #!/bin/bash; apt update && apt install -y gh || true), cache environments to skip on resume. Prefer repo-attached SessionStart hooks in .claude/settings.json for cross-local/cloud dependency installs (e.g., npm install; pip install -r requirements.txt if CLAUDE_CODE_REMOTE==true), as they run post-launch every time.
Network levels: None (isolated), Trusted (allowlisted: Anthropic/GitHub/registries/cloud SDKs/package managers like pypi.org/npmjs.com/etc.), Full (any domain), Custom (your list + defaults). GitHub/security proxies available; defaults cover * .gcr.io, AWS/Azure/GCP, PyPI/NPM/Rubygems/Crates.io/etc., Linux repos, dev tools.
Seamless Web-Terminal Task Mobility
From terminal to web: claude --remote "Fix bug" bundles repo (force with CCR_FORCE_BUNDLE=1 for non-GitHub), launches cloud session. Use --permission-mode plan for reviews, chain tasks via /tasks, run non-interactive like migrations/refactors/tests. Tips: separate cloud for CPU-heavy (e.g., claude --remote "Execute migration").
From web to terminal: /teleport or /tp outputs claude --teleport
Session Control and PR Automation
Manage context: /compact (e.g., /compact keep test output) frees tokens; /context shows window; no /clear—new session via sidebar. Set CLAUDE_AUTOCOMPACT_PCT_OVERRIDE=70 or CLAUDE_CODE_AUTO_COMPACT_WINDOW. Review diffs (+42 -18 style). Share Pro/Max/Team sessions; archive/delete via UI.
Auto-fix PRs: /autofix-pr on gh issue_comment triggers Claude response. Troubleshoot: session fails? Check gh auth (/web-setup); expired remote? /login; env expired? Fresh session auto-creates. Limits: resource caps, no outbound if None, prompt length errors.