AI Catchup

Claude Code Projects Turn One Conversation Into Parallel Cloud Sessions

By 10 min read

Anthropic's redesigned Projects beta gives Claude Code one coordinating conversation that delegates work to parallel threads. Threads are usually cloud sessions, which Anthropic's docs now list as available, no longer in research preview, on Pro, Max, and Team and for eligible Enterprise seats. A project can also run a thread on your own machine through Remote Control.

Anthropic is rolling out a redesigned Projects experience in Claude Code. The beta gives a project one coordinating conversation that can delegate work to parallel cloud sessions, keep shared memory, and continue working after you close your laptop. (Anthropic's announcement; Claude Code Projects documentation; ClaudeDevs on X)

This is a different shape from a folder that simply holds several chats. You describe the work in one conversation, and Claude decides which requests should stay in that conversation and which should become threads. Each thread is a separate session with its own context window, and a cloud thread works on its own branch. (Claude Code Projects documentation)

Key Takeaways

  • One coordinator: A long-running project conversation routes tasks and tracks the threads it starts.
  • Parallel cloud work: Threads run in parallel as separate Claude Code sessions, each handling one part of the work.
  • Shared context: New threads start with the project's repositories, files, instructions, memory, connectors, plugins, and cloud environment.
  • Work continues away from the desk: Cloud threads keep going after you close your laptop, and you can check on them from your phone.
  • Cloud sessions are out of research preview: Anthropic's current documentation lists them as available on Pro, Max, and Team, plus Enterprise users with premium seats or Chat + Claude Code seats. (Claude Code cloud documentation)
  • A thread can run on your machine: when a task needs something only your computer has, you can ask Claude to run that thread on your computer through Remote Control; the computer running project threads needs Claude Code v2.1.280 or later. A session you started yourself on your machine still cannot be added to a project. (Claude Code Projects documentation)
  • Projects remain a separate beta workflow: The coordinator and parallel-thread experience still has the rollout and account limits described below. (Claude Code Projects documentation)
  • Higher usage pressure: Every thread is a full session, and the coordinator also consumes tokens, so a project can reach plan limits faster.

One Conversation, Many Threads

The project conversation is the control surface. Claude receives bug reports, task lists, stack traces, updates, and quick questions, then routes each message based on the work involved. A quick question can be answered in the conversation; a new piece of work can be sent to a new thread or an existing one working in the same area. (Claude Code Projects documentation)

Threads are the workers. Each is a separate session with its own context window that does one piece of work and reports back to the conversation when it finishes; a cloud thread works on its own branch and opens a pull request when the work calls for one. Threads can also split delegated work into subagents, loops, and workflows. If two threads change the same code, the result can be a merge conflict just as it would with other pull requests. (Anthropic's announcement; Claude Code Projects documentation)

That makes Projects suited to work that outlasts one reply and has more than one part: migrations across repositories, a research stream that needs several deliverables, or a build where implementation, tests, and review can proceed in parallel. Anthropic says you can configure the project's goal, repository or other context, cloud environment, connectors, plugins, instructions, and model. (Anthropic's announcement) To choose between Projects, subagents, agent teams, and dynamic workflows, see our comparison of Claude Code's parallel approaches.

Repository Context and Shared Memory

Every new cloud thread starts with the project's repositories and files, instructions and memory, the connectors on your claude.ai account, and a cloud environment. The environment sets network access, environment variables, API credentials, and installed tools. Each cloud thread clones every repository in the project and loads CLAUDE.md and skills from all of them. (Claude Code Projects documentation)

The project also has shared memory and a Library. Threads can draw on details accumulated by earlier work, while the Library collects files added to the project and files produced by threads. This is the part that turns a set of parallel runs into a continuing workstream rather than independent sessions. (Anthropic's announcement; Claude Code Projects documentation)

The boundary is important: cloud threads work on GitHub repositories and on the files, folders, and Google Drive folders you upload to the project, not on files or tools that exist only on your machine. If a task needs your machine (a local database, a device emulator, or an API behind your VPN), ask Claude to run that thread on your computer through Remote Control: in the Claude desktop app, open Settings > Claude Code, turn on Use this computer from your phone and claude.ai, and add the folder to the list under that switch, or run claude remote-control in the folder and leave it running. That machine needs Claude Code v2.1.280 or later, and a project cannot run a thread on your machine while Require trusted devices is on in your claude.ai settings. A session you started yourself on your machine still cannot be added to a project. (Claude Code Projects documentation)

Access and Limits

Projects are in public beta on Pro and Max plans and are rolling out gradually, starting with accounts that have used cloud sessions and do not have existing projects in Claude or Cowork. Team and Enterprise plans are not available yet. If Projects does not appear at claude.ai/code or in the Code tab of the desktop app, the rollout has not reached that account; Anthropic provides a waitlist for users who want to request earlier access. (Claude Code Projects documentation; Anthropic's announcement)

The beta is available at claude.ai/code, in the desktop app, and in the Claude mobile app, not in the terminal CLI, the VS Code extension, or the JetBrains plugin, and not through Amazon Bedrock, Google Cloud's Agent Platform, or Microsoft Foundry. A project reaches your machine only by running a thread there through Remote Control. (Claude Code Projects documentation)

Projects use the same plan limits as other Claude Code sessions, but they can consume those limits faster. Every running thread is a full session, and the project conversation uses tokens too. Threads that watch pull requests can use the plan again when a CI failure or review comment arrives, and the enforced limit is 200 new threads per day across your projects. A thread that reaches its limit waits and continues on its own when the limit resets; a thread that a routine started instead stops with a limit error. (Claude Code Projects documentation)

Cloud Sessions Left Research Preview

Anthropic's cloud-session documentation no longer calls the feature a research preview. The "Use Claude Code in the cloud" page, as retrieved September 18, 2026 by the Internet Archive, opens: "Cloud sessions are in research preview for Pro, Max, and Team users, and for Enterprise users with premium seats or Chat + Claude Code seats." The same page, read September 25, 2026, opens: "Cloud sessions are available on Pro, Max, and Team plans, and for Enterprise users with premium seats or Chat + Claude Code seats." Anthropic's developer account on X posted the change the same week (Sources, below). (Claude Code cloud documentation; archived capture; ClaudeDevs on X)

You can start a cloud session from claude.ai/code, the Claude mobile app, the Desktop app with Cloud selected, or the terminal with claude --cloud; each session can then be checked or steered from another device. (Claude Code cloud documentation; Claude Code quickstart)

The same X post said existing subscribers get a one-time credit to try cloud sessions. As of September 25, 2026, no Anthropic documentation or help article carries that credit, so this page does not repeat the amounts. What was checked, all read September 25, 2026:

SurfaceWhat it says about a cloud-session credit
Help Center article on managing usage credits for paid Claude plans (last updated September 24, 2026)Nothing. It covers pay-as-you-go usage credits.
Help Center article on managing usage credits for Team and seat-based Enterprise (last updated September 4, 2026)Nothing.
The cloud-sessions and costs pages of the Claude Code docsNothing.
Claude Code changelog on GitHubNo entry.

The cloud-session change does not make Projects generally available. Projects remains the beta described above, with its own rollout and plan limits, and the Projects documentation stays the source of truth for the coordinator, threads, and beta access. (Claude Code Projects documentation)

What This Changes for Developers

Projects make coordination the primary workflow. Instead of manually opening several sessions, copying context between them, and stitching results together, you can give Claude a stream of related work and let the coordinator decide when to fan out. You still need to choose the repository context carefully, watch for branch conflicts, and account for the fact that parallel sessions spend limits faster.

The practical promise is not simply “more agents.” It is a persistent work queue with shared memory, repository-aware threads, and a single place to review what is finished, what needs attention, and which pull requests are ready. For teams that need private network services or organization-level controls, the current beta's single-user boundary (a project belongs to one user, with no organization-level controls during the beta) matters as much as its parallelism; local tools now reach a project only through a Remote Control thread.

Corrections and Updates

  • September 25, 2026: This page said a project could not use your machine and that machine-only work needed a separate local session. Anthropic's Projects documentation now lets Claude run a project thread on your computer through Remote Control; a session you start yourself on your machine still cannot be added. (Claude Code Projects documentation)
  • September 25, 2026: This page gave one-time cloud-session credit amounts from an X post. No Anthropic documentation carried them, so the amounts were removed; the checks are in Cloud Sessions Left Research Preview, above.

Sources

Read next

Related coverage

Frequently Asked Questions

What are Projects in Claude Code?

Projects are a beta workflow in Claude Code where one ongoing conversation coordinates related work by delegating tasks to parallel sessions called threads. Each thread is usually a cloud session with its own context window, and the conversation keeps track of every thread it started.

Who can use Claude Code Projects?

Projects are rolling out in public beta to Pro and Max users, beginning with accounts that have used cloud sessions and do not already have Projects in Claude or Cowork. Team and Enterprise access is not available yet.

Can Claude Code Projects keep working when I close my laptop?

Yes. Threads are usually cloud sessions, which keep working after you close your laptop, and you can steer them from the web, the desktop app, or your phone. For files or tools only your machine has, ask Claude to run that thread on your computer through Remote Control; the computer running project threads needs Claude Code v2.1.280 or later.

Do Claude Code Projects use more of a plan's limits?

Yes. Each thread is a full Claude Code session, and the coordinating conversation also consumes tokens, so Projects can use plan limits faster than a single session. Threads watching a pull request also wake up and use your plan when CI fails or a review comment arrives.

Get the weekly AI Catchup

Tools, practices, and what matters, in your inbox every week.