Claude Code 发布云端会话指南，Pro/Max 用户可领一次性云额度

The Claude Code team just published a 𝗳𝘂𝗹𝗹 𝗳𝗶𝗲𝗹𝗱 𝗴𝘂𝗶𝗱𝗲 to cloud sessions. You can ask Opus 5.5 to use it to pick out everything in your project that can run in the cloud.

Existing individual Pro and Max subscribers can also claim a one-time cloud credit ($𝟭𝟬𝟬 𝗼𝗻 𝗣𝗿𝗼, $𝟮𝟱𝟬 𝗼𝗻 𝗠𝗮𝘅): run /claim-credit in Claude Code by October 7. It expires November 4.

Cloud sessions give every task a fresh virtual machine, and they keep going when you close your laptop. There's no separate charge for the machine, it draws on your plan's usual limits, and it doesn't tie up your laptop's CPU, so you can run tests without holding back: in the guide, a test that failed now and then was fixed and then run 𝟰𝟬 𝘁𝗶𝗺𝗲𝘀 𝗶𝗻 𝗮 𝗿𝗼𝘄 𝘄𝗶𝘁𝗵 𝘇𝗲𝗿𝗼 𝗳𝗮𝗶𝗹𝘂𝗿𝗲𝘀. Small unrelated fixes, and fixes you can only prove by running tests over and over, go to the cloud. Anything that needs a local database, a VPN, a GPU or a phone simulator stays local.

Send this prompt to Opus 5.5 👇

"Read this guide: https://claude.dev/blog/claude-code-in-the-cloud/

Then look for work in this project's TODOs, failing or flaky tests (check CI history and skip markers; don't rerun them locally over and over), places where the docs and code disagree, and recent commits, and sort it into three groups: 1. Work that suits cloud sessions running in parallel, 5 items at most: unrelated tasks that can each be proven done on their own. Write each as one ready-to-use claude --cloud "…" line that says what's wrong, what done looks like, and how to prove it (make the proof heavy, for example run the full test suite 30 times in a row). Keep the items from editing the same files where you can, and give a merge order. 2. Work that has to stay local: anything that needs a local database, a VPN, a GPU or a phone simulator, or where I want to see each change in my own browser right away. 3. Things a cloud session would be missing: CLAUDE.md, skills and agents this project uses that live only in ~/.claude; changes that aren't committed or pushed; variables the tests need that live only in a local .env; a private repo without the Claude GitHub App installed. Mark anything you can't check as needing my confirmation. For each item, point to the exact location, explain why it goes where it does in words a 10-year-old could follow, and for group 3 give the smallest fix. Show me the list first, and don't start any sessions yet."