Run a fleet of cloud Claude Code sessions from one agent with Claude Projects

Chase shows how Claude Projects lets you talk to one agent that manages many always-on Claude Code sessions in the cloud, sharing context and memory, with a setup demo.

Chase AI · YouTube · published Oct 16, 2026 · Software & DevOps

Run a fleet of cloud Claude Code sessions from one agent with Claude Projects — video by Chase AI▶ Watch on YouTube
Prompt
Using Claude Projects, create a project for [my app] and have the lead agent split the work into [number] cloud sessions (frontend, backend, tests), share context between them, and report progress back to me.

Visual breakdown

Claude Code projects lets you talk to one coordinator agent that splits your work across a fleet of full, persistent Claude sessions running 24/7 in Anthropic's cloud, sharing context and memory and opening PRs in your GitHub repo. It draws from your Max plan usage, not API costs.

The problem: Normally you manage every terminal and agent yourself, keep them on the same page, and the work stops the moment your laptop shuts down.

How a Claude Code project runs your work

  1. Create the projectProjects beta in the desktop app: name, optional goal and context files
  2. Repo and environmentPick a GitHub repo for PRs; add a cloud environment with network access and secrets if needed
  3. CoordinatorOne orchestrator (Opus on low effort by default) splits the prompt and deals out work
  4. Parallel threadsFull Claude sessions with their own context, shared memory, each owning its PRs
    Dropped: Blockers handed back to you for a decision or a key
  5. Unblock and steerAnswer blockers through the coordinator or talk to any thread directly
  6. Always-on projectPRs in your repo and a living build you can feed from anywhere, even with your computer off
Repo and secretsYou: setup and decisionsClaude sessionsResult

Use projects vs. a normal session

  1. Use it for complicated, long-running work you keep feeding and can split into parts
  2. Skip it for quick tasks you can finish in one chat
  3. Be wary when the work must touch files that live only on your machine
  4. Not on Team or Enterprise plans yet

By the numbers

5parallel threads from one prompt
25 minrun before the first review
< 24 hto get off the wait list

Set up your first project

Apply on the wait list page, then open Projects beta in the Claude desktop app.

  1. Archive old chat-era projects to start from a clean slate
  2. Click New project, give it a name, and optionally a goal and context files
  3. In settings, keep the coordinator on low effort and the thread model on Opus medium (or Sonnet)
  4. Keep project instructions short and turn on auto memory
  5. Select a GitHub repo, and add a cloud environment with secrets if you need API keys
  6. Allow local device access with a pre-approved folder only for work that must run on your machine
  7. Give it your prompt, then clear blockers through the coordinator

Turn on auto-continue so work resumes when your usage limit resets.

Tips from the demo

  • The coordinator only deals out work, so low effort is fine; bump it up only if coordination is poor.
  • Usage burns fast with 5, 10 or 15 threads working 24/7, so watch the thread model.
  • Less is more in project instructions: every thread reads them.
  • A session that needs your logged-in accounts (here, scanning X) can run locally and even build a local scheduled routine.
  • Unlike subagents, threads persist, own their PRs, and you can message them at any time.

Distilled from the video’s captions

How to try it

  1. Open Claude Code.
  2. Copy the prompt and fill in the [placeholders].
  3. Watch Chase AI's video for the full walkthrough and setup.

Related use cases

Share