Skip to main content

Claude Code Cloud Sessions for Beginners: How to Delegate Work and When to Choose Them

A Claude Code cloud session runs your GitHub repository task on a virtual machine in the cloud and hands the result back as a pull request. This guide explains how it works and how to decide between cloud and local sessions.

By
🌐 This article was machine-translated and may contain inaccuracies. Read the Korean original if in doubt.

A cloud session — a Claude Code session that runs on cloud infrastructure instead of on your own computer. You pick a GitHub repository, describe the task, and Claude does the work and hands back something you can review. According to the official documentation, once the task has started you can leave the page entirely and Claude keeps working.

🟢 Model references match the current lineup · model notice · Fable subscription
🟢 Model references match the current lineup · Claude Opus 5.5 / Claude Sonnet 5.5 / Claude Haiku 5.5 (higher tier: Claude Fable 5.2). This notice changes only when Anthropic ships a new model.

Fable subscription (updated November 10, 2026): Claude Fable 5.2, released November 9, 2026, is the current Fable model; Fable 5.1 and Fable 5 are now legacy. Plan terms are the same for all three — Max and Ultra plans and premium seats on Team and seat-based Enterprise plans include Fable at up to 50% of the weekly usage limit; Pro plans and standard seats use usage credits (not available on Free). As a launch offer, Fable models are also included for Pro plans and Team standard seats at up to 50% of the weekly limit through November 16, 2026 (PT). API pricing is $8/M input and $40/M output tokens for Fable 5.2, and $10/$50 for Fable 5.1 and 5. Some cybersecurity and biology requests may be answered by an Opus model due to safety classifiers. See the Fable 5.2 launch news and the Fable 5.2 guide for details.

1. Pick a repo GitHub repository 2. Describe task Write the request 3. Cloud work Runs in a virtual machine 4. New branch Changes pushed 5. You review Create a pull request

What you will be able to do after this guide

You will be able to judge what a cloud session is and which tasks are worth delegating to one. It takes about 5 to 10 minutes to read. This is a concept and decision guide based on the official help article; exact button labels can change, so this guide does not name them. Please check them on your own screen.

What you need before you start

The main requirement is access to a GitHub repository. According to the official documentation, you can assign tasks on any GitHub repository you have access to without cloning it locally.

  • A GitHub repository — a project folder hosted on GitHub (an online service for storing and managing code). A repository is a storage box for code and its change history.
  • A Claude account — which plans include this feature is not confirmed in the source material for this guide. Check whether it appears in your own account.
  • One place to start from — Claude Desktop, claude.ai/code on the web, Claude Mobile, or your terminal.

Quick glossary

  • Branch — a separate line of work where changes pile up without touching the original.
  • Pull request (PR) — a request asking "please review these changes before merging them into the main code."
  • Virtual machine — a temporary computer created inside the cloud. A new one is made for each task.
  • Terminal — a window where you type commands as text.
  • IDE — a dedicated program for writing and editing code.

How do you start a cloud session?

You can start from whichever of four places is most convenient. The official documentation lists Claude Desktop, claude.ai/code on the web, Claude Mobile, and your terminal. From the terminal, use this command:

claude --cloud
  1. Pick where to start — if you use the terminal, type the command above. This assumes Claude Code is already installed in your terminal.
  2. Select a GitHub repository — it must be one you have access to.
  3. Describe the task concretely — for example, "Find and fix every typo in the login screen help text." A request with a clear finish line works best.

What success looks like — the session shows that the task is in progress, and on the web you can follow its progress. The documentation says you can also add guidance while it runs if needed. If it does not start, first check that you have access to the repository and that the feature appears in the app or account you are using; if that does not help, look up the article of the same title in the help center at support.claude.com.

What happens behind the scenes after you start?

Claude creates a temporary virtual machine, works inside it, and returns the result as a new branch. In the same order as the diagram above:

  • Pick a repo — the selected GitHub repository is cloned into an isolated virtual machine, which the documentation says comes pre-configured with common development tools and language ecosystems.
  • Describe the task — if your repository's configuration defines setup commands (installing dependencies, preparing databases, and so on), Claude runs them first to prepare the environment.
  • Cloud work — Claude reads code, makes changes, writes tests, and runs commands to verify the work. If the task needs the internet, for example to install packages or fetch data, you can configure the environment's level of internet access.
  • New branch — when the task is done, the changes are pushed to a new branch in your GitHub repository and you get a notification.
  • You review — after looking over the changes, you can create a pull request directly from the interface.

On security, the documentation says each task runs in complete isolation, with controls such as restricted network access and protected credential handling. Your GitHub authentication goes through a secure proxy (an intermediary channel), so credentials never exist directly in the environment where Claude is working.

Caution — results come back for review; they are not merged automatically. Do not skip the step of opening the pull request and reading through the changes yourself.

Should you choose a cloud session or a local session?

Choose the cloud when requirements are clear and you will rarely need to change direction; choose local when you expect to keep adjusting as you watch. A local session runs on your own computer, such as in Claude Desktop, your terminal, or your IDE. Here is the official guidance arranged by situation:

Good fit for cloud sessions · Tasks with clear requirements · Bug backlogs run in parallel · Repos not on your machine · Queued work to review later Good fit for local sessions · Frequent course correction · Exploring unclear requirements · Immediate feedback needed (per official documentation)
SituationSuggested choiceWhy
The goal is clear, such as "fix all these typos"CloudYou rarely need to step in, so you can start it and check the result later.
Several bug issues are piling upCloudEach task runs in its own environment in parallel and creates its own pull request.
You need to change a repository you have never downloadedCloudThe cloud session handles cloning and environment setup.
You are not sure how to solve the problem yetLocalYou need the back-and-forth to refine your request as you learn.
You want to redirect Claude as you watch it workLocalYou get immediate feedback and can adjust as it goes.

As a beginner, start by delegating one small task with a clear finish line. A wording fix or a small bug is a good choice because you can verify the result by eye. Try several at once only after you are comfortable with the flow.

Common sticking points

  • The request was vague and the result missed the mark — the usual cause is unclear requirements, which the official documentation says suit local sessions. Rewrite the request more concretely or work locally.
  • A task that needs the internet is blocked — the environment's internet access setting affects things like installing packages or fetching data. Check the access level in the settings.
  • Several tasks were started on one repository — the documentation says more than one task can work on the same repository at once. Each creates its own pull request, so check during review that their changes do not overlap.

Frequently asked questions

Q. Can I turn off my computer after starting a task?
According to the official documentation, once Claude has started working you can leave the page completely and it continues. You get a notification when it finishes, and you can come back to review the result.

Q. Do I need to download the repository to my computer?
No. For any GitHub repository you have access to, you can delegate a task without cloning it or setting up a development environment yourself.

Q. Can I run several tasks at the same time?
Yes. Each task runs independently in its own isolated environment and creates its own pull request when it finishes. More than one task can even work on the same repository simultaneously.

Q. Which plans include cloud sessions?
The source material for this guide does not confirm that. Prices and availability can change, so check the official pricing page at claude.com/pricing and your own account screen.

Was this helpful?

Keep reading