Cloud Sessions Leave Research Preview, Bring Free Credits
Anthropic has moved Claude Code cloud sessions out of research preview and into general availability, and is using the launch to hand out promotional usage credits to existing subscribers. Pro subscribers are eligible for $100 in credits, while Max subscribers get up to $250 — but the credits apply only to work run in the cloud, not on a local machine.
Cloud sessions let Claude Code execute a coding task on Anthropic-hosted infrastructure instead of the user's own computer. Once started, the session keeps running after the user closes their laptop or goes offline, and they can return later to review, redirect, or merge the work.
Offer Details
| Attribute | Value |
|---|---|
| Feature | Claude Code cloud sessions — general availability (out of research preview) |
| Announced | September 23, 2026 |
| Pro plan credit | $100 |
| Max plan credit | $250 |
| Eligibility | Individual Pro/Max subscribers with an active subscription as of September 23, 2026 |
| Claim deadline | October 7, 2026 |
| Unused balance expires | November 4, 2026 |
| Access points | claude.ai/code, Claude mobile app (Code section), desktop app, CLI (claude --cloud) |
| Requirement | Linked GitHub account |
How It Works
Starting and running a session
Users can kick off a cloud session from claude.ai/code, the Code section of the Claude mobile app, the desktop app, or from the terminal with claude --cloud. Each --cloud invocation spins up an independent session, so multiple tasks can run in parallel. Anthropic describes the appeal plainly: "Cloud sessions run on Anthropic-hosted infrastructure, so the work keeps going even without your computer running."
Claiming and spending the credit
The promotional balance is separate from a subscriber's normal Claude usage limits and is applied automatically once a cloud session starts. According to Anthropic, hitting a local usage limit doesn't have to stop work: "If you hit a limit locally, keep going in the cloud until your credit runs out." The credit can be claimed at claude.ai/code/claim-credit/10 or by running /claim-credit inside the Claude Code CLI. Once the balance is exhausted, cloud sessions simply start counting against the subscriber's normal plan limits — there is no separate charge for the cloud container itself.
Repo access and getting work back out
Cloud sessions require a linked GitHub account because each session clones the repository at its current branch into its own container and runs on its own branch. Anthropic's implementation clones from GitHub, not from the developer's local working copy — so any uncommitted local changes need to be pushed before a cloud task starts. When a session finishes, users open a pull request from claude.ai/code or pull the work back into a local terminal session with claude --teleport.
Enterprise routing
Organizations that don't want cloud sessions running on Anthropic's shared infrastructure have an alternative: Anthropic says enterprise teams can route sessions to self-hosted runners inside their own network through partners such as Coder.
Impact Assessment
| Impact Area | Description |
|---|---|
| Individual developers | Free credit lowers the cost of trying an agentic, always-on coding workflow without committing spend up front |
| Access model change | Cloud sessions no longer require a research-preview signup — any eligible Pro/Max subscriber can use them today |
| Code and repo exposure | Repos must be pushed to GitHub and linked to Anthropic's cloud runner for a session to clone and operate on them |
| Enterprise data residency | Self-hosted runner routing (via Coder) exists as an alternative for teams that need code execution to stay inside their own network |
| Time-boxed adoption incentive | Claim window (Oct. 7) and expiry (Nov. 4) create a short runway for teams evaluating the feature before it reverts to normal billing |
Recommendations
For IT and security teams evaluating agentic coding tools
- Inventory which repositories would be linked to a cloud-session-enabled GitHub account before enabling it org-wide, and scope that account's repo access as narrowly as practical
- For code with strict data-residency or confidentiality requirements, evaluate the self-hosted runner option via Coder rather than relying on Anthropic's shared cloud infrastructure
- Treat cloud sessions the same as any other third-party CI/build runner in a vendor-risk review — they execute code and have read/write access to whatever repository is connected
For developers/subscribers
- Push local changes before starting a cloud session — the container clones from GitHub, not the local working copy, so uncommitted work will not be reflected
- Track credit usage before the November 4 expiry; unused promotional balance does not roll over or transfer once it lapses
- Remember that once the credit is exhausted, cloud session usage reverts to counting against normal plan limits, with no separate cloud-container charge
Key Takeaways
- Claude Code cloud sessions are now generally available, exiting research preview as of September 23, 2026
- Pro subscribers get $100 and Max subscribers get up to $250 in promotional credit, usable only for cloud sessions
- Credit must be claimed by October 7, 2026, and any unused balance expires November 4, 2026
- A linked GitHub account is required — cloud containers clone the repository from GitHub at the current branch, not from the local machine
- Work can be retrieved via a pull request from claude.ai/code or brought back to a terminal with
claude --teleport - Enterprise teams can route sessions to self-hosted runners through partners like Coder instead of Anthropic's shared cloud infrastructure