Anthropic Officially Launches Claude Code Cloud Sessions with Up to $250 in One-Time Credits for Pro and Max Subscribers

On September 23, 2026, Anthropic officially transitioned 'Cloud sessions' for its terminal-based coding assistant, Claude Code, from research preview into General Availability (GA).

Image source: Oikon (@oikon48) / X

The general release decouples agentic coding workflows from local developer hardware. Sessions can now run on Anthropic-managed cloud infrastructure or within an organization's self-hosted setup, allowing long-running refactoring tasks, builds, and test sweeps to progress continuously in the background even if a developer closes their laptop lid or their computer enters sleep mode. To celebrate the milestone, Anthropic is granting existing Pro and Max subscribers a one-time cloud session credit of $100 and $250, respectively.

Decoupling from Local Hardware: Cloud Session Architecture and Invocation Workflows

Historically, Claude Code operated as a local process tied directly to the developer's active terminal emulator. When executing extensive refactoring passes or running comprehensive automated test suites that spanned tens of minutes, any laptop lid closure, battery sleep event, or lost network connection terminated the active session prematurely.

Cloud sessions resolve these local operational constraints by shifting session execution to remote cloud environments:

• CLI-Triggered Remote Execution: Developers can kick off an asynchronous cloud session from their local terminal by supplying the --cloud flag:

claude --cloud "Fix the authentication bug"

• Multiple Entry Surfaces: In addition to terminal invocations, developers can initiate and track cloud sessions via the dedicated web interface (claude.ai/code), Claude official desktop and mobile applications, or scheduled task automations via Routines.
• Local Session Handoff (Teleport): Work started remotely can be transferred directly to the local terminal environment using the --teleport flag:

claude --teleport

At present, CLI session handoff operates strictly one-way: from the cloud runtime down to the local environment.

• Repository Integration: Workspaces connect either by linking a GitHub account or by directly uploading and synchronizing a local Git repository via the CLI.

Plan Availability and One-Time Cloud Credits for Pro and Max Subscribers

Cloud sessions are available across Claude's paid subscription tiers, including Pro, Max, and Team plans, as well as Enterprise accounts with premium seats (Premium Seat / Chat + Claude Code Seat). Free tier accounts do not have access to the feature.

Anthropic does not charge separate virtual machine (VM) infrastructure fees for cloud session runtime. Instead, compute usage draws against the rate limits already included in the subscriber's active plan, sharing capacity with standard interactive sessions.

To encourage trial and adoption, Anthropic is distributing a one-time credit allocation to existing individual Pro and Max subscribers:

• Claude Pro Subscribers: $100 in dedicated cloud session credits
• Claude Max Subscribers: $250 in dedicated cloud session credits

Credits are not applied automatically and require manual claiming by the user. Subscribers can claim their credits through two official methods:

1. CLI Command: Run /claim-credit directly within Claude Code
2. Web Portal: Visit claude.ai/code/claim-credit/10 and confirm the grant

Strict deadlines govern the promotional credits. All claims must be submitted by October 8, 2026, at 15:59 JST/KST. Once claimed, the credits remain valid until November 5, 2026, at 16:59 JST/KST, after which any unused balance expires. These promotional funds serve strictly as dedicated cloud session credits and apply automatically to cloud sessions once claimed. While active, the promotional credits take priority over normal subscription quotas for cloud session execution; once depleted or expired, usage automatically reverts to the account's standard plan rate limit.

Practical Considerations: Permission Boundaries and Data Governance

While background cloud execution eliminates local machine friction, team leads and individual practitioners should account for several operational considerations prior to rollout.

First, the introductory credit grant was explicitly announced for existing Pro and Max subscribers. Initial documentation did not confirm automated credit grants for Team plan seats, meaning organizations should verify plan-level credit status before planning usage around promotional allowances.

Second, running code in remote cloud environments introduces governance and permission considerations. Because Git branches are checked out and executed on remote infrastructure, engineering teams should evaluate repository access scopes, outbound network egress permissions, and secret management policies within their environment variables before enabling broader access.

Third, because the claim window closes on October 8, existing eligible subscribers should claim their credit allocations promptly through the CLI or web portal to ensure they do not forfeit the trial funds.

Sources

• Forest Watch (Impress): ノートPCを閉じてもOK、「Claude Code」の“クラウドセッション”の一般提供が開始
• ClaudeDevs Official X Announcement (@ClaudeDevs): 2026-09-23 Claude Code Cloud Sessions Announcement
• Oikon (@oikon48) on X: Claude Code cloud版 正式リリース