TL;DR — Key Takeaways
- Anthropic redesigned Claude Projects to coordinate multiple Claude Code sessions working in parallel on different parts of a development goal.
- Each thread runs as a separate cloud session, while shared memory and a central coordinator help maintain context and track work across the Project.
- The beta starts with select Pro and Max users.
Anthropic announced it has redesigned Claude Projects to coordinate multiple coding sessions in parallel, with the new experience debuting in beta for Claude Code users.
In the redesigned Projects, a coordinator can break a development goal into separate threads, assign them to individual Claude Code cloud sessions and track their progress from one shared project. The beta is initially available to select Claude Pro and Max subscribers using Claude Code cloud sessions, with wider Pro and Max access coming over the next week. Updated Projects across the rest of Claude and on Team and Enterprise plans will follow.
The naming may be confusing because Anthropic already uses “Projects” for its general-purpose Claude workspaces. Anthropic describes this as a new version of that existing feature, rather than a separate Claude Code product. The redesign is debuting in Claude Code, while existing Projects in chat and Cowork will continue to work for now and be upgraded as the rollout expands.
In the redesign, each thread for repository-based work runs as a separate Claude Code cloud session with its own branch and copy of the repository, so that multiple parts of a development task can move forward at the same time without one session overwriting another’s changes. Developers can follow the work from the main project conversation or open an individual thread to observe its progress and redirect it if needed.
Those sessions can make code changes, run tests and open pull requests. Threads can also use Claude Code’s existing subagents and other workflows for more complex assignments. Anthropic has not eliminated the usual coordination problems of parallel development, however. If multiple sessions make conflicting changes, developers will still need to resolve any merge conflicts.
For developers, the new Projects could mean less manual work dividing tasks among multiple Claude Code sessions and keeping track of the results. Anthropic says developers could, for example, have separate threads profiling multiple application endpoints at once or coordinating changes across API, web and mobile repositories during a migration.
The redesign also adds shared memory across threads so parallel sessions can work from the same context. New threads can draw on decisions and information from earlier work, and a project library stores any uploaded files and artifacts Claude creates. Developers can also configure the environment, connectors, plugins, instructions and model used across the Project.
The new Projects fits with how Anthropic says Claude Code usage has been evolving. In a June analysis of roughly 400,000 sessions, the company found that users generally retained control over planning while delegating more execution to Claude, with usage shifting toward more end-to-end work, including deploying and running code, over the seven months studied. In the new Projects, developers can set the larger goal and let Claude coordinate more of the work.
Running several sessions at once also comes with trade-offs. Anthropic warns that Projects can consume usage allowances more quickly because each thread is a full Claude Code session. Threads currently run in the cloud, and Anthropic says support for running them locally alongside developers’ tools and code is coming later.

