Claude Code Cloud Sessions Go GA; $100/$250 Credits Due Oct. 7

Claude Code Cloud Sessions Reach General Availability​

The underlying change is the general availability. Anthropic's ClaudeDevs developer account announced that cloud sessions are officially available and out of research preview, and that they let you keep Claude Code working even when your laptop is closed. BleepingComputer, which first reported the credit terms in detail, notes that the feature had previously been available to some users via research preview, but is now officially available to eligible subscribers.

A cloud session is a Claude Code agent session that runs on remote infrastructure instead of your own machine. In Anthropic's words, "Cloud sessions run on Anthropic-hosted infrastructure, so the work keeps going even without your computer running." Pasquale Pillitteri's write-up describes these as virtual machines managed by Anthropic. The practical upshot is that you can hand the agent a task, close the lid, and come back later to review what it did.

The feature itself is available to more people than the credit offer. General availability covers Pro, Max, and Team subscribers, and Anthropic's product page also lists Enterprise users with premium seats or Chat + Claude Code seats. The credit is only for individual Pro and Max accounts. Team and Enterprise admins should read the promotion as a consumer-plan incentive, not as a budget line for their organization.

Cloud sessions are tied to GitHub. AlphaSignal reports that a GitHub connection is required since each session runs on its own branch and repo copy. That makes the cloud workflow suited to repositories already hosted on GitHub. Code that lives only on a local disk or in another hosting service doesn't fit the model as neatly.

Starting Claude Code in the Cloud From Web, Mobile, Desktop or CLI​

Anthropic lists four ways in. You can start one at claude.ai/code, from the Code tab in the Claude mobile app, from the desktop app, or with claude --cloud in the CLI. BleepingComputer says it observed the same four entry points in its own testing.

Terminal users on Windows, macOS or Linux get the most direct route through the --cloud flag on the claude command. A session started there runs on Anthropic's hardware. Once it's running, you don't need a live connection from the machine you launched it on.

Anthropic's original web announcement, from the preview period, described isolated environments for each session, progress tracking, the ability to steer a task while it runs, parallel tasks, and automatic pull-request creation. It pitched the cloud workflow at repository questions, routine bug fixes, and backend changes that tests can verify. Those are sensible first jobs to try with the credit, because the output is easy to check.

How the $100 Pro and $250 Max Claude Code Credits Actually Work​

The amounts are simple. Existing Pro and Max users can claim a one-time dedicated credit—$100 for Pro and $250 for Max—valid exclusively for Cloud Sessions and separate from their regular subscription usage limits. The $250 figure applies only to Max. Pro subscribers get $100.

Anthropic describes the credit this way: "The credit is separate from your usage limits, and it applies automatically once you start a cloud session. If you hit a limit locally, keep going in the cloud until your credit runs out." In other words, the promotional balance is an extra bucket that sits on top of your plan allowance. It doesn't replace that allowance.

The announcement caused some confusion, and Anthropic followed up with a clarification: "Cloud sessions run on your Pro or Max plan, like the rest of Claude Code. This promo is an optional one-time credit that your cloud sessions spend first, before falling back onto your normal plan usage." The spending order is fixed. Cloud work draws down the promo balance first, and when that's gone, it counts against your ordinary subscription limits.

BleepingComputer reports that no additional VM charges apply, and standard subscription limits take effect after credits are exhausted. Several readers had worried that the promotion meant cloud sessions would become a separately billed product. On the evidence so far, they haven't. After the promotion ends, cloud sessions work like the rest of Claude Code and share your plan's limits.

The credit isn't a general account balance, and it isn't the same thing as Anthropic's paid usage credits. Anthropic's Help Center describes those separately: usage credits allow individuals subscribed to paid Claude plans (Pro, Max 5x, and Max 20x) to continue using Claude seamlessly after reaching their included usage limits, and they are billed at standard API rates. The promotional balance can't be spent in chat, through the API, or in local Claude Code sessions.

Claiming the Credit Before the October 7 Deadline​

According to BleepingComputer, claims must be made by October 7, and credits expire on November 4. Pillitteri's report adds that the deadline is end of day on the US West Coast. That's the only report giving a time zone, so if you're in Europe or Asia, claim well before the date to be safe.

Eligibility has a cutoff too. BleepingComputer reports that the offer is limited to individual Pro and Max subscribers whose subscriptions were already active when the promotion began on September 23. Signing up for Pro today to collect $100 looks unlikely to work. SmartScope's guide flags eligibility after a new subscription from Free, any different amounts for Max 5x versus Max 20x, separate Team or Enterprise promotions as open questions that only the account-specific terms can settle.

Several outlets independently describe a three-step process that matches the popup shown in Claude Code on the web:

1. Claim the credit. Pillitteri says you can claim the credit from Anthropic's link or by running /claim-credit in the CLI, and AlphaSignal and explainx.ai also report the /claim-credit command.
2. Connect GitHub and pick a repository. According to explainx.ai, you need it to start a session, and the credit only applies once you do.
3. Start a cloud session and the credit is used automatically. There is no code to enter.

Once the credit is claimed, the claim deadline no longer matters. The November 4 expiry is the date to plan around. Anything left in the balance after that disappears.

Where the Promotion Leaves Claude Code's Usage Limits​

The timing makes sense given the recent tension over Claude Code limits. BleepingComputer's own coverage lists a related story about Anthropic cutting Claude Code's current weekly limits by 17%. Heavy users have felt the squeeze. AlphaSignal points out that before this change, background work previously consumed the same allowance used for interactive sessions.

The credit eases that problem for a few weeks and then stops. AlphaSignal says so plainly: "The promotion provides temporary capacity; regular plan limits govern usage after the balance is depleted." If you're weighing a Max upgrade because the cloud workflow looks appealing, remember that from November onward, your long unattended tasks will come out of the same weekly allowance as your interactive work.

Nobody has published a way to convert the dollar figure into hours of runtime, number of tasks, or tokens. SmartScope lists the promotional balance's conversion rate among the unverified details. How far $100 or $250 goes will depend on the model, the size of the repository, and how long the agent runs. Keep an eye on your usage for the first few sessions before planning anything large around the balance.

Organizations have another option. AlphaSignal reports that Enterprise teams can route sessions to self-hosted runners inside their own networks via partners like Coder. That matters for companies that can't let source code run on a vendor's VMs, but it's a separate path from the consumer credit.

What this means for you​

If you're an individual Pro or Max subscriber whose plan was active on September 23 and you keep code on GitHub, claim the credit now. It costs nothing, the deadline is close, and the balance gets used before your plan allowance. Team and Enterprise users, new subscribers, and developers whose repositories aren't on GitHub can skip the promotion. Evaluate cloud sessions on their own merits, knowing they draw on normal plan limits.

Treat the credit as a trial budget. Point it at work that's easy to verify, such as bug fixes with test coverage, dependency updates, or questions about a codebase. Check the branch and pull request the agent produces before merging anything. AlphaSignal's advice to verify permissions, secret handling, network access, retention, and usage limits before production adoption is worth following before you give a cloud VM access to a private repository.

• Pro accounts get a one-time $100 cloud-session credit and Max accounts get $250. Both are limited to individual subscribers whose plans were active when the promotion began on September 23, 2026.
• Claim the credit by October 7 through Anthropic's claim link or the /claim-credit command in the Claude Code CLI. Any unused balance expires November 4.
• The credit only pays for cloud sessions. It can't be used for chat, the API, or local Claude Code, and it's separate from Anthropic's paid usage credits, which are billed at API rates.
• You need a connected GitHub account and a selected repository before a cloud session will start and draw on the credit.
• Start sessions at claude.ai/code, in the Code tab of the Claude mobile app, in the desktop app, or with claude --cloud.
• When the credit runs out, cloud sessions count against your normal plan limits. The cloud VM itself has no separate charge.

Moving cloud sessions to general availability is the lasting change. Claude Code can now run on Anthropic's machines for anyone on Pro, Max, Team, or an eligible Enterprise seat, with no preview signup. The $100 and $250 credits are a short-term incentive that ends on November 4. After that date, cloud sessions draw on the same weekly allowance as everything else in Claude Code, and subscribers will have to decide whether unattended cloud work is worth spending that allowance on.