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. The change makes remote agent controls—repository scope, network access, credentials and merge review—a production concern for teams.
Anthropic announced the availability change through its Claude developer account and product documentation. BleepingComputer independently tested the launch paths, while Exame and PC Watch separately reported the credit terms and deadlines.
What Claude Code cloud sessions change
A local coding agent inherits the protections and limitations of a developer’s machine: available credentials, network routes, local tools and the point at which a laptop sleeps. A cloud session separates execution from that device. The repository is cloned into a remote workspace, the task continues asynchronously, and the developer can return later to review changes or steer the run.
That can make 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. Enabling the feature is therefore an infrastructure decision, not merely a user-interface preference.
The credits are an adoption offer
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 unused promotional balance expires on 4 November. Team and Enterprise access does not automatically mean eligibility for the individual-subscriber promotion.
The offer lowers the cost of testing remote workflows. It does not remove normal rate limits, establish permanent pricing or create an unlimited service. Teams should measure task completion, review effort and failure recovery before treating the credit as evidence of economic value.
Security review should start before the first clone
Anthropic’s documentation says each hosted session runs in an isolated virtual machine, with network access limited by default and Git credentials kept outside the sandbox behind a scoped proxy. Administrators still need to decide which repositories are eligible, who may enable outbound network access and what secrets a build can retrieve.
A prudent rollout begins 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.
| Item | Verified position |
|---|---|
| Status | Out of research preview |
| Execution | Anthropic-hosted infrastructure by default |
| Pro credit | $100 one-time credit |
| Max credit | $250 one-time credit |
| Claim deadline | 7 October 2026 |
Lapaas Voice’s Claude Cowork workspace analysis covers interface convergence, while its Claude Opus 5.5 cost review explains why model price alone is not a workload budget.
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.
Does a cloud session continue after the laptop closes?
Yes. Execution runs on hosted infrastructure, so work can continue without the local computer awake.
Is the $250 credit permanent?
No. It is a one-time promotion with a claim deadline and expiry for unused balance.
Get the day’s top stories in your inbox
One concise email. No spam, unsubscribe anytime.
