Claude Code Projects: How Parallel Cloud Agents Work

01

Overview

Claude Code Projects has been redesigned from a place for grouping work into an active coordinator for multiple coding-agent sessions. Anthropic announced the new Projects experience on September 17, 2026, and began a beta rollout to select Claude Pro and Max subscribers who use cloud sessions in Claude Code.

02

What changed in Claude Code Projects?

The central change is delegation. Instead of manually opening several coding sessions, dividing a larger job between them, and stitching the results together yourself, you can describe the overall engineering goal in a Project conversation. Claude can scope that request, split it into pieces, start parallel threads, coordinate their progress, review the outputs, and assemble the result.

Anthropic describes this as moving Projects “from folder to conversation.” The Project conversation acts as the coordinator; the work can fan out into separate Claude Code cloud sessions.

03

How Claude Code Projects threads work

A thread is not merely a sub-chat. Anthropic says Project work can run as parallel Claude Code cloud sessions. That matters because each thread can work independently rather than waiting for another task to finish.

For repository work, threads can operate on separate branches and can open pull requests. If parallel work eventually touches conflicting code, normal Git merge-conflict handling still applies; the coordinator does not magically remove source-control conflicts.

Anthropic's launch examples include profiling and optimizing multiple endpoints in parallel and coordinating a deprecated API migration across API, web, and mobile repositories.

04

The coordinator model

The Project conversation is the control layer. You provide the broader objective and steer the work while Claude decides how to decompose suitable tasks into threads. The coordinator can track what the threads report back, review their results, and bring the work together.

This makes Projects closer to a managed team of coding sessions than a conventional saved chat folder.

05

Projects can keep working when you step away

Because the current threads run as cloud sessions, Anthropic says work can continue after you step away from your computer. You can return to the Project and inspect progress instead of keeping a local terminal process alive for every parallel job.

Anthropic also says users can steer progress throughout the work, including from a phone, although availability of individual surfaces may vary during the beta rollout.

06

Shared project context

Projects are intended to reduce repeated context setup across a long-running engineering effort. Repository context, project instructions, files, and accumulated project knowledge can give new work a common foundation rather than forcing you to restate the same decisions in every independent session.

This is particularly useful for work that spans several components or repositories, where separate agents need to understand the same high-level goal.

07

Pull requests and parallel repository work

A practical Project workflow can look like this:

1. Give Claude a project-level engineering objective.
2. Claude identifies work that can run independently.
3. Parallel threads operate as Claude Code cloud sessions.
4. Repository work occurs on separate branches where appropriate.
5. Threads test their changes and can open pull requests.
6. The Project conversation tracks results and dependencies.
7. You review the output and decide what should land.

The important distinction is that Projects coordinates software work; it does not remove normal engineering review, CI, testing, or Git conflict resolution.

08

Who can use the redesigned Projects?

Anthropic launched the updated Projects experience in beta on September 17, 2026. Initial access is for select Pro and Max subscribers using cloud sessions in Claude Code. Anthropic says access will expand to more Claude Code users on those plans over the following week, with updated Projects across broader Claude experiences and Team and Enterprise plans coming later.

Existing Projects are not necessarily converted immediately during the staged rollout.

If Projects is not visible on an otherwise eligible account, staged availability is therefore a plausible explanation. Do not assume every Pro or Max account receives the redesign simultaneously.

09

Does Claude Code Projects run locally?

The redesigned beta is centered on Claude Code cloud sessions. Anthropic says support for working with local tools and code is coming, but it has not provided a verified public launch date for that capability.

That distinction matters for developers whose repositories, services, databases, or tooling are only reachable from a private local or corporate environment.

10

How much does Claude Code Projects cost?

Anthropic has not announced a separate universal price for Projects. Access currently depends on eligible Claude plans and the staged beta.

Parallelism also has a cost in usage: multiple active threads are multiple Claude Code sessions, so a Project can consume plan usage faster than a single sequential session. Exact practical consumption depends on the number of threads, models, effort, task length, and the limits attached to the user's plan.

There is no responsible single “cost per Project” number to publish from the current launch information.

11

Where Projects could be useful

The strongest use cases are engineering jobs that contain independent workstreams: multi-repository migrations, endpoint profiling, test expansion, dependency upgrades, refactors across components, bug investigation, and changes that can be reviewed as separate pull requests.

Projects may be less advantageous for a small linear edit where parallel sessions add coordination overhead without shortening the critical path.

12

Important limitations

Projects is a beta and its rollout is still changing. Current work is cloud-session based. Parallel agents can consume usage limits faster. Separate branches can still conflict. Human review remains important before merging generated changes, especially for security-sensitive or production-critical systems.

Anthropic has also not announced a standalone Projects API, standalone Projects price, or a confirmed date for local execution in the launch material reviewed here.

13

Claude Code Projects FAQ

Is Claude Code Projects a multi-agent feature?

It can coordinate multiple parallel Claude Code cloud-session threads from one Project conversation. Calling it a multi-agent workflow is reasonable, but each thread should be understood as a coding session rather than as proof of a new underlying Claude model.

Can Claude Code Projects work on multiple repositories?

Anthropic's own launch example describes coordinating an API migration across API, web, and mobile repositories, making multi-repository engineering one of the intended workflows.

Can Projects open pull requests?

Anthropic describes threads doing repository work, running tests, and opening pull requests as part of coordinated workflows.

Does it keep running after I close my laptop?

Current Project threads run in Claude Code cloud sessions, and Anthropic says work can continue after you step away from your computer.

Is it available to every Claude user?

No. The redesigned experience launched as a staged beta, initially for select Pro and Max users of Claude Code cloud sessions. Broader access is planned.

Is local Claude Code Projects available?

Not in the same form as the current cloud-thread beta. Anthropic says local tools and code support is coming, without a verified release date.

14

Bottom line

Claude Code Projects changes the unit of interaction from one coding session to an ongoing engineering goal. The coordinator can split that goal across parallel cloud sessions, preserve shared project context, and bring results back into one place. The early advantage is less manual orchestration; the tradeoffs are faster usage consumption, cloud-first access, beta availability, and the same need for careful code review and source-control discipline.