Claude Code cloud sessions are now generally available, moving long-running coding work from a developer’s laptop into an Anthropic-hosted environment that can continue after the computer closes. Existing Pro and Max subscribers can also claim a one-time cloud-session credit of $100 or $250 respectively by 7 October, but the durable change is operational: teams now need to govern remote agent execution as production infrastructure.
Anthropic’s Claude developer account announced the availability change and promotion. Its product documentation supplies the more important control details. BleepingComputer independently tested the launch paths, while Exame and PC Watch separately confirmed the credit levels, eligibility and deadlines.
What Claude Code cloud sessions change
A local coding agent inherits the limits and protections of the developer’s machine: local credentials, network routes, available tools and the moment the laptop sleeps. A cloud session separates execution from that machine. The repository is cloned into a remote workspace, the task continues asynchronously, and the developer can return later to inspect changes or steer the run.
That makes long test suites, migrations and multi-file refactors easier to hand off. It also changes the trust boundary. Source code and task context move into a hosted environment, while repository access is mediated through Anthropic’s GitHub connection. Teams should therefore treat enabling cloud sessions as an infrastructure decision, not merely a user-interface preference.
The credits are an adoption offer, not the control model
The announced credit is $100 for eligible existing Pro subscribers and $250 for eligible existing Max subscribers. It applies only to cloud sessions, is spent before normal plan usage and must be claimed by 7 October. BleepingComputer reports that unused promotional balance expires on 4 November. Team and Enterprise users can have feature access without being included in this individual-subscriber offer.
Those limits matter because the headline “up to $250 free” can obscure how usage works after the balance ends. The promotion lowers the cost of testing remote workflows. It does not remove normal rate limits, create an unlimited service or establish future pricing. Buyers should measure task completion, review effort and failure recovery before using the credit as evidence of economic value.
Security review should start before the first repository clone
Anthropic’s documentation says each hosted session runs in an isolated virtual machine, network access is limited by default and Git credentials remain outside the sandbox behind a scoped proxy. Those are useful boundaries, but administrators still need to decide which repositories are eligible, who may enable outbound network access and what secrets a build can retrieve.
The safest rollout starts with low-sensitivity repositories and deterministic checks. Require branch protection, peer review and CI before merge. Keep deployment credentials and signing keys outside the agent workspace. Log who launched the session, which repository and branch it used, which network permissions were granted, and what files changed.
Verified launch facts
| Item | Verified position |
|---|---|
| Status | Out of research preview |
| Execution | Anthropic-hosted infrastructure by default |
| Launch points | Web, mobile, desktop and CLI |
| Pro credit | $100 one-time cloud-session credit |
| Max credit | $250 one-time cloud-session credit |
| Claim deadline | 7 October 2026 |
The release fits a broader shift from chat windows toward persistent work environments. Lapaas Voice’s Claude Cowork workspace analysis covers the interface convergence, while the Claude Opus 5.5 cost review shows why model price alone is not a workload budget. The Anthropic pacing plan provides the governance backdrop for increasingly autonomous systems.
Claude Code cloud sessions remove the laptop as the execution anchor. That convenience makes repository policy, network boundaries, credential isolation and merge review more—not less—important.
Frequently asked questions
Who can claim the promotional credit?
The announcement names eligible existing Pro and Max subscribers, with one credit per account. Feature access for Team and Enterprise does not automatically imply promotional credit.
Does a cloud session continue after the laptop closes?
Yes. Execution runs on hosted infrastructure, so the task can continue without the local computer remaining awake.
Is the $250 credit permanent?
No. It is a one-time cloud-session promotion for eligible Max subscribers, with a claim deadline and an expiry for unused balance.
What should enterprises verify first?
Repository eligibility, network policy, credential boundaries, audit logs and mandatory review gates should be defined before broad rollout.
Get the day’s top stories in your inbox
One concise email. No spam, unsubscribe anytime.
