fullauto.online

Harnesses

Claude Code cloud sessions: How Anthropic's generally available release changes team workflows

Anthropic moved Claude Code cloud sessions out of research preview on September 23 2026, offering $100/$250 credits and enabling browser-based coding tasks with isolated sandboxes and GitHub proxy. What it means for teams, security, and DevOps.

Published
07 Oct 2026
Reading
9 min
Class
harnesses

half-life 60dfrom 07 Oct 2026

On 23 September 2026, Anthropic announced that Claude Code cloud sessions—previously known as Claude Code on the web—are now generally available for Pro, Max, and Team subscribers, as well as Enterprise users with premium seats or Chat + Claude Code seats. The feature lets developers run Claude Code agent sessions on Anthropic-hosted infrastructure, so work continues even when the local device is offline or closed.

Each cloud session runs in an isolated virtual machine with 4 vCPUs, 16 GB RAM, and 30 GB of disk space. The session clones the connected GitHub repository onto a dedicated branch, performs the requested coding task, and pushes the branch back to GitHub for review via a pull request. Anthropic manages the virtual machine by default, though organisations can route sessions to self‑hosted environments if preferred.

Access is possible through four entry points: the browser at claude.ai/code, the Code tab in the Claude mobile app, the desktop app (selecting “Cloud” instead of “Local”), or the terminal using the claude --cloud flag. A connected GitHub account is required to clone repositories and push results.

To encourage trial, Anthropic is offering a one‑time credit: $100 for Pro subscribers and $250 for Max subscribers. The credit must be claimed by 7 October 2026 via the /claim-credit command in the Claude Code CLI or through the claim link at claude.ai/code/claim-credit. Any unused balance expires on 4 November 2026. After the credit is exhausted, cloud‑session usage counts against the subscriber’s normal weekly allowance.

Security and privacy are built in: network access is limited by default, and GitHub credentials are stored outside the sandboxed environment, where a scoped‑credential proxy authenticates on the session’s behalf. Sessions share the same rate limits as other Claude and Claude Code usage on the account—there is no separate compute charge for the underlying virtual machine beyond that allowance.

The move to general availability shifts the control plane from local terminals to centralized cloud, affecting team onboarding, security policies, and the balance between agent autonomy and oversight. Teams can now hand off long‑running coding tasks to Claude Code without requiring engineers to keep their laptops open or maintain complex local‑development environments.

Why it matters to the audience

  • Cloud sessions remove the friction of local setup, letting anyone with a Claude Code subscription start coding agents from any device.
  • The isolated sandbox and credential proxy reduce the risk of leaking secrets or exposing internal networks during agent‑generated code changes.
  • For engineering managers, the feature provides a clearer audit trail: every cloud session creates a GitHub branch and pull request, making it easier to review and approve agent‑generated changes.
  • The $100/$250 credit lowers the barrier to experiment with unattended agent work, though teams should evaluate whether ongoing cloud‑session usage fits within their existing rate‑limit budgets.

Sources