Claude Code cloud sessions go GA with credit outside limits

You can close your laptop and Claude Code keeps working, and for existing Pro and Max subscribers, Anthropic pays for the first stretch, according to the ClaudeDevs post on X. Cloud sessions are out of research preview and officially available. Every existing subscriber gets a one-time credit to try them: $100 on Pro or $250 on Max.

At a glance

• According to Anthropic, cloud sessions run Claude Code on cloud infrastructure instead of your machine, so work continues after the lid closes. They are available on Pro, Max and Team plans.
• The credit sits outside your usage limits and applies automatically once you start a cloud session. If you hit a cap locally, you can keep going in the cloud until the credit runs out.
• The fine print: one credit per account, cloud sessions only, GitHub must be connected, and the claim deadline is Oct 7. The post does not say what sessions cost afterwards.

If you have not been following, Claude Code spent the summer learning to work away from your desk. According to Claude Code Docs, self-hosted environments for cloud sessions entered public beta on Team and Enterprise plans in the week of August 3–7, 2026. The same docs say that `claude remote-control`, shipped in the week of August 17–21, 2026, lets you start a session on a registered machine from your phone.

Existing Pro subscribers get $100 and Max subscribers get $250 for cloud sessions

The main offer is a one-time credit for existing subscribers: $100 on Pro and $250 on Max. The post gives no credit amount for Team, although Anthropic lists Team among the plans that can use cloud sessions. You get one credit per account, and it pays for cloud sessions only.

You can claim it two ways: follow the link in the announcement, or run /claim-credit in the CLI. You need GitHub connected before you can start a session at all. The deadline to claim is Oct 7, and the post notes that terms apply without spelling them out.

The credit runs outside the usage limits that cap local Claude Code work

According to the post, the credit is separate from your usage limits and kicks in automatically once you start a cloud session. The team gives one practical case: if you hit a limit locally, you keep going in the cloud until the credit runs out.

For context on those limits, Truefoundry reports that Claude Code usage runs on two layers: a 5-hour rolling window and a weekly cap on active compute hours. That quota is shared across Claude Code, Claude.ai chat and Cowork. Truefoundry puts Pro at ~10–45 prompts per 5-hour window and ~40–80 Sonnet hours a week. For Max 5x, it gives ~50–225 prompts per window and 140–240 Sonnet hrs + 15–35 Opus hrs a week.

Truefoundry also reports that Anthropic reduced the 5-hour limits during weekday peak hours (5–11 AM PT) starting March 2026. It adds that Anthropic acknowledged on March 31 that users were hitting limits faster than expected.

Cloud sessions move the Claude Code session off your laptop and onto cloud infrastructure

Anthropic describes a cloud session as a Claude Code session that runs on cloud infrastructure instead of on your machine. Your laptop stops being the place where the work happens. The session lives somewhere that does not care whether your lid is open, your Wi-Fi drops or your battery dies.

The difference is clearest next to what came before. According to MindStudio, Claude Code's /bg command already moved an active session into Agent View so it kept working while you switched tasks. But it ran inside the terminal, so the session ended when the terminal closed. Local background mode is like leaving the oven on while you step into another room. A cloud session is more like handing the dish to a bakery that keeps baking after you go home.

Price is the biggest gap. The post says the credit lasts until it runs out, but it never says what cloud sessions cost per hour or per task, so you can't tell whether $100 on Pro buys an afternoon or a month. In our view, a credit counted in dollars with no published rate is hard to plan around, and the GitHub requirement likely shuts out teams whose code lives elsewhere.

Before the October 7 claim deadline

The next checkpoint is Oct 7, the last day to claim the credit through the link or /claim-credit. What comes after the credit is still open. The announcement names no per-session rate and does not say whether Team accounts get a credit of their own. According to Claude Code Docs, self-hosted environments are still in public beta on Team and Enterprise, and no general availability date has been given.