Claude Code's cloud sessions received an official field guide on October 6, 2026: Anthropic published a long post on the claude.dev blog laying out how cloud sessions work, which tasks they suit, and how to connect GitHub, all in one place. For subscribers who have not yet claimed their bonus credit, the guide also carries a deadline — the one-time cloud-session credit for Pro and Max users (100 and 250 dollars respectively) must be claimed by October 7, and it expires on November 4.
The fundamental difference from local sessions: the machine is its own
Run Claude Code locally and the session is tied to your computer: it shares one working tree, so two sessions editing the same repository fight each other; it runs with your machine's credentials; and when the computer sleeps or the network drops, the task stops. A cloud session separates all three: each task gets a fresh virtual machine, the repository is cloned onto a new branch, and the environment is set up in advance; when the work is done, it sits on the branch for you to decide whether it becomes a pull request.
Sessions can be started from more than the terminal: claude.ai/code, the Claude mobile app, the desktop app, a terminal, and Slack all work, with progress followable from a browser, a phone, or the desktop. The guide's author tested parallelism against a sample repository: three cloud sessions started within 16 seconds of each other, tackling an intermittently failing test, an outdated document, and a piece of logging code, all advancing at once on separate machines without interfering — locally, those three tasks would have queued, or needed a human watching that they did not step on each other.
Cost and activation: included in the plan, but an organization may need to flip a switch
Cloud sessions are included in Pro, Max, Team, and Enterprise plans; the cloud machine carries no separate charge, and sessions draw on the same usage allowance as local Claude Code. Two easy traps: first, Team and Enterprise may require an organization owner to enable cloud sessions in settings first — one person being enabled does not mean everyone is; second, the bonus credit does not apply to Projects or Routines, and anything unspent by November 4 is gone.
Which tasks belong in the cloud, and which do not
The guide's decision framework is pragmatic. Good candidates for the cloud are independent tasks that can run in parallel, long jobs that do not need watching, and changes where risk isolation matters — each task owns its machine and branch, so a bad run is discarded by dropping the branch. Tasks needing frequent interactive confirmation, or depending on a special local environment or intranet resources, stay smoother locally. The guide also spends real attention on letting a session verify its own work: give it test commands and checks, and the branch it hands back is closer to "ready to review" instead of shifting the verification cost onto the reviewer. Connecting GitHub is the biggest first-run hurdle, and a full section walks through the authorization flow and common errors — the most useful part for team administrators.
Cloud coding sessions are not an Anthropic-only move. This site previously reported Codex launching its cloud environment; what both share is freeing "writing code" from a single personal computer — tasks run in parallel in the cloud, and the human role shifts toward assigning work, reviewing, and deciding. The difference is in the details: Claude has put its bonus credit, shared usage pool, and organization switch all on the table. For teams already using Claude Code, this guide's value is not novelty — it is a prompt to settle branch discipline, verification habits, and allowance rules before parallel delegation becomes daily routine.
