Anthropic has rebuilt Projects inside Claude Code so a single stated goal, not a single chat, becomes the unit of work. Tell a project to cut your app’s checkout latency and it opens separate threads to profile each endpoint, test fixes, and open pull requests at the same time, then reports back which ones are safe to merge first.
Each thread is a full Claude Code cloud session running on its own branch and its own copy of the connected repository. A coordinator assigns work, checks progress, and folds finished threads back together; if two threads touch the same code, the system treats it as an ordinary merge conflict rather than something special. Anthropic says a thread can also break its own assignment into subagents, loops, and workflows to finish faster, so the parallelism can nest more than one layer deep.
The design targets work that runs longer than a single reply and touches more than one file or repository, the kind of job that today gets split across several manually managed chat windows. A project can hold multiple connected repositories at once. In one example Anthropic gives, connecting an API, web, and mobile repo and asking to retire a deprecated endpoint produces one migration thread per repo, each running its own tests before opening its own PR.
Memory now persists at the project level instead of resetting with every chat. Anthropic says the coordinator and every thread draw on a shared record of prior decisions, so a project can recall that a release moved to Friday or which teammate to check with before touching billing code, without the user re-explaining it each session. A new library inside the project also collects added files and generated artifacts so later threads can build on earlier ones instead of starting cold.
Access is narrow for now. The redesigned Projects went live today only to select Claude Pro and Max subscribers who already use Claude Code’s cloud sessions and have no existing project on web or desktop. Anthropic says it will widen access to more Code users on those plans over the coming week, with Team and Enterprise plans and existing project holders added after that; anyone without access can join a waitlist. Existing projects keep working unchanged until their turn to upgrade comes.
This is Anthropic’s own framing of the release, published on its company blog rather than reported by an outside outlet, so the “up to six threads at once” style workflow claims and the latency-fixing example have not been tested by anyone outside the company. Anthropic also has not said how projects perform once dozens of threads are running against the same repository at once, only that conflicts get resolved the same way a human’s would. Running threads on a developer’s own machine, behind their own network instead of in Anthropic’s cloud, is described as coming soon but not yet available.
For teams already running multiple Claude Code sessions by hand to split a migration or a bug hunt, this collapses that manual coordination into one instruction, provided their workload fits inside the beta’s usage limits, since Anthropic warns that running several full sessions at once burns through quota faster than a single chat does.
Anthropic detailed the redesigned Projects feature in a post on the Claude blog published September 18, 2026.
