Claude Code cloud sessions: seven workflows and a bonus credit ending Oct 7

Anthropic has published a guide to running Claude Code on its own machines instead of your laptop, and attached a deadline to it. The guide, posted on claude.dev on October 6 and promoted by @ClaudeDevs, explains cloud sessions and recommends seven workflows. It also says existing individual Pro and Max subscribers can claim a one-time bonus credit until October 7. This article covers what cloud sessions are, what the guide demonstrates, when to stay local and how the credit works. We also checked the offer against BleepingComputer’s report. We read the guide through its GitHub section and the start of the section on giving sessions what they need to check their work, but not its final parts; we did not run cloud sessions ourselves.

What are Claude Code cloud sessions?

A cloud session runs Claude Code on a machine of its own. Each task gets a fresh virtual machine with your repository cloned onto a new branch and your environment’s setup already done. You can start one from claude.ai/code, the Claude mobile app, the Desktop app, your terminal (claude --cloud "...") and Slack, and follow it from the browser, phone or Desktop. The work ends as a branch, which you can turn into a pull request.

They come with Pro, Max, Team and Enterprise plans with no separate charge for the machine, and sessions draw on the same usage limits as the rest of Claude Code. An organization owner may need to turn them on first.

How does the bonus credit work?

According to the guide, existing individual Pro and Max subscribers can claim a one-time credit for cloud sessions on top of their plan limits: $100 on Pro and $250 on Max. BleepingComputer reports that the promotion began on September 23, that it is limited to individual subscribers who had an active subscription then, and that the credit is separate from normal usage limits and applied automatically when you start a cloud session. Claim it by October 7 at claude.ai/code/claim-credit or with /claim-credit in Claude Code. The credit expires on November 4, and it is not eligible for Projects or Routines. After it is used or expires, your plan’s regular usage applies. Neither the guide nor BleepingComputer states the exact time or time zone of the October 7 cut-off (one search result mentioned 11:59 PM Pacific, which we could not confirm). The guide points to Anthropic’s Promotional Credit Offer Terms, which we did not read; check them before relying on the details.

What did the guide’s tests show?

The author, Addy Osmani, says he ran four real sessions against a small sample repository, “tidepool,” a made-up Node API. Three sessions started within 16 seconds of each other, ran for 61, 65 and 72 seconds, and were all done 87 seconds after the first started. Recreating the repository took about a third to just over half of each run, a step a real GitHub clone would replace.

• Flaky test: Claude found a race in the cache’s get method, stored the in-flight promise instead, and ran the suite 40 times with no failures.
• Docs: it started the server, ran a request against every endpoint and found five ways the old document was wrong.
• Logger: it wrote a JSON logger with five tests, noticed a failing test, traced it to the same race another session was fixing, and reported that the suite was not clean rather than touching the cache.

Each session had its own copy of the repository, processes and branch, which is the point: two agents in one local checkout would collide on files and ports. It also means one session cannot see another’s fix, so the guide advises splitting work along file boundaries.

Which seven workflows does the guide recommend?

1. Clear a backlog in parallel, one session per self-contained ticket.
2. Let it prove the fix, for example by running a test suite many times in the VM.
3. Plan locally, build in the cloud, finish in your terminal with claude --teleport, which pulls a cloud session’s branch and conversation into your terminal.
4. Check in from your phone, to start, follow or steer a task.
5. Hand CI failures and review comments to Claude with Auto-fix, which needs the Claude GitHub App.
6. Start work without starting it yourself with routines, a research preview triggered by a schedule (hourly at most), an HTTP call or a GitHub event.
7. Run code you do not fully trust in a disposable machine, with network access set to none or trusted.

When should you stay local?

The guide says stay local when the task needs something only your machine has: a database with real local data, a service behind a VPN, a GPU, a phone simulator or hardware on your desk. Also stay local for tight visual loops where you want to see each change in your own browser, and when your organization runs with Zero Data Retention, which turns cloud sessions off. Remote control and self-hosted environments (beta for Team and Enterprise) sit between the two.

On safety, the guide says your GitHub token never enters the machine (a proxy holds it and the session gets a short-lived credential that can push only to its own branch), the repository’s Claude configuration comes along while your personal ~/.claude does not, and idle machines are reclaimed, so commit work you care about. Even with network access set to none, Claude Code still talks to the Anthropic API, so data can leave the machine that way.

How do you connect GitHub?

Cloud sessions need two separate GitHub permissions: signing in with GitHub, and installing the Claude GitHub App on the account or organization that owns the repositories. Public repositories work with sign-in alone; private ones need the App. The guide lists three paths: connect in the browser (recommended), /web-setup from your terminal using your gh token, or upload a repository bundle for a one-off. A frequent failure is an organization using SAML single sign-on whose authorization step was skipped.

What to keep in mind

These are our observations:

• The deadline is real and soon. If you are a Pro or Max subscriber, the claim window closes October 7, so read the offer terms and claim it if it suits you.
• It is a vendor demo. One author, one small fictional repository, results chosen for the guide. Treat the timings as illustrations.
• Cloud work still costs limits. The machine is free, but each turn counts toward your plan.
• The date differs by page. The guide is dated October 6 on its own page, while claude.dev’s blog index showed October 1 when we checked.

Editorial review: October 6, 2026 (AI). Prepared from the guide on claude.dev (read through a browser, about the first 22,000 characters, which cover everything above; the later sections on environments and the rest were not read), from ClaudeDevs’s post on X and from BleepingComputer’s report on the offer (read in full for the dates, eligibility and amounts). We did not run cloud sessions, read the offer terms or verify the bonus credit ourselves. All figures and claims are Anthropic’s, except the offer’s start date, eligibility and credit mechanics, which are BleepingComputer’s. The cover is Anthropic’s own card, reproduced with credit and a link to the source. “What to keep in mind” is ours.