What Anthropic is selling with the rebuilt Projects feature in Claude Code is not a nicer chat window. The pitch is a team of agents that talk to one another.
Under the new setup, several agents can operate beneath a single roof, pooling memory, goals and a shared library of files and artifacts. A project opens “threads” that work through separate tasks side by side, with a “coordinator” handing out the assignments. Anyone who has worked with Grok Bot, or any of the other tools built to wrangle groups of AI agents, will recognise the layout immediately.
Every thread is its own branch
This next detail is the one that lands for anybody who has ever watched a bot roam loose through a repository. Internally, a thread is a Claude Code cloud session running on a branch of its own, against its own copy of the repo.
Organising all of that falls to the coordinator. Yet Anthropic makes no magical claims about what happens when two threads reach for the same code. That collision shows up as a merge conflict, exactly like any other pull request you would untangle by hand.
Call it an honest design decision rather than a solution. Git has long been able to flag that two people rewrote the same function, and Projects defers to that rather than pretending a coordinator could settle questions of intent.
Threads can split themselves further
The thread is not where the hierarchy bottoms out. Any thread can carve up the work handed to it through subagents, loops and workflows, and Anthropic credits that mechanism for getting big assignments done quicker.
Three levels deep, then: project, then thread, then subagent. Whether the arrangement survives contact with a repo carrying real history is a question no launch post can settle.
The cloud-only catch
Threads live in the cloud for now. Local tools and local code will be supported “very soon,” according to Anthropic — a phrasing whose meaning is familiar enough.
If your build leans on a local toolchain, a local database, or anything else that has no existence inside a cloud sandbox, that caveat is hardly small print. It decides whether you use this now or simply bookmark it.
Who actually gets it
Beta access to the refreshed Projects feature opens today for “select Claude Pro and Max subscribers.” Not the whole group. Select ones.
Wider access follows later for every Pro, Max, Team and Enterprise user, along with Cowork and standard Claude chats. “Later” comes without a date.
Pro subscribers who cannot find it have done nothing wrong. They simply have not been picked yet — and the piece of this release most developers would actually use, running threads against code sitting on their own machine, has not shipped in any form.