Claude Code makes cloud sessions generally available

• Claude Code cloud sessions have left research preview and keep an agent working on Anthropic-hosted infrastructure after the laptop is closed, according to ClaudeDevs’ cloud-session announcement.
• Sessions can begin from the web, desktop app, Claude mobile app, or the CLI, where the ClaudeDevs thread lists claude --cloud as an entry point.
• Existing Pro subscribers get a one-time $100 cloud-session credit and Max subscribers get $250, while ClaudeDevs’ clarification says the credit spends before normal plan usage.

Anthropic’s cloud-session documentation includes --teleport, which moves a session between the web and terminal. Its web quickstart describes the remote workspace as an isolated VM that turns a connected GitHub repository into a branch for review. The company’s long-run playbook also asks users to set a finish line and check-in point before handing over a task.

Cloud sessions now run at claude.ai/code on Anthropic-managed infrastructure and persist after the browser closes, as ClaudeDevs’ rollout thread describes. The same thread names four launch surfaces:

• Claude Code on the web
• The Code tab in the Claude mobile app
• The desktop app
• The CLI with claude --cloud

The CLI reference defines claude --cloud "Fix the login bug" as creating a new web session. The cloud docs say a running task can be monitored from the mobile app, while --teleport moves work between the terminal and web.

A GitHub connection is required to start a cloud session, the claim instructions state. The quickstart lays out the handoff in three steps:

1. Connect a GitHub repository and submit a task.
2. Claude clones the repository into an isolated virtual machine and makes the changes.
3. Claude pushes a branch for review.

The remote environment is configurable with setup scripts, Docker, and network access under the cloud-environment documentation. That makes the remote run a repository workflow, not merely a browser view of a terminal.

The promotional balance is separate from a plan’s ordinary usage limit, but it does not replace the plan. ClaudeDevs’ follow-up says cloud sessions use Pro or Max subscription access as usual; the one-time credit is consumed first, then sessions draw from the account’s normal rate limits.

The offer is one credit per account, for cloud sessions only. ClaudeDevs’ promotion says it can be claimed from the linked flow or with /claim-credit in the CLI, provided GitHub is connected; the attached terms set an October 7 claim deadline and a November 4 expiry.

Anthropic’s first-session guidance for Opus 5.5 gives cloud work a clear shape:

• Hand over a whole task, with a definition of done and a check-in point.
• Skip “think carefully,” because the model reasons before responding.
• After a long run, ask what it needs to continue.

One early workflow is deliberately mundane: jenny_wen described using a bot to spin up a cloud agent for small simplifications between meetings. It is the kind of task that gains value from persistence without requiring someone to keep a development machine awake.