Claude Code Now Runs a Team

Claude Code used to give you a folder with files in it. As of 17 September 2026, a Project is a team.

You pick a goal and a repo. Claude scopes the work, opens parallel threads, reviews what they produce, and stitches a result. You can steer from the main chat or from a phone. It keeps going after you close the laptop.

Image: Anthropic, Projects redesigned: from folder to conversation, 17 September 2026.

A thread is a whole session

This is the part that is easy to miss if you already use Cursor Projects. Anthropic's thread is not a subagent inside one chat. It is a full Claude Code cloud session: its own branch, its own copy of the repo. The coordinator sits above those sessions. If two threads edit the same code, the overlap becomes a merge conflict, the same way two humans would collide.

A thread can still split work with subagents, loops, and workflows. The extra layer is the fleet object. Anthropic's examples are the kind of work that used to die in a spreadsheet: cut checkout p75 latency by profiling endpoints in parallel, or retire a v1 API across web, mobile, and the backend and then tell you which PR has to merge first.

Memory, plus a library

Every thread writes into shared memory and reads from it. Anthropic says that is how the system remembers the release moved to Friday, why an export got dropped, or who you ping before touching billing. Next to memory sits a library of files you added and artifacts Claude produced, so the next thread does not start from a blank prompt.

That is the same industry move Cursor made a week earlier: a coordinator that does not type the code, plus a place for the lore. The product difference is distribution. Cursor's Projects beta went to all users. Claude's redesigned Projects opened to select Claude Pro and Max subscribers who already use cloud sessions and do not have an existing web or desktop project. Access widens this week, then Team, Enterprise, Cowork, and regular Claude chats. Old projects keep working until they get upgraded.

Cloud first, bill later

Threads run in the cloud today. Local tools and code behind your network are coming "very soon," which is vendor-speak for not this build. Because each thread is a full session, a Project can burn usage faster than a single chat. Anthropic put project-level usage in the UI, plus model and effort controls for the coordinator and the workers. That is the number to watch, not the demo.

The Verge compared the setup to other fleet managers. The useful question for a team is more boring: who owns the merge when a coordinator is opening PRs from a cloud box you cannot see? Least privilege, an audit trail, and a kill switch still matter. A folder never needed those. A team of sessions does.

Sources

Anthropic, Projects redesigned: from folder to conversation, 17 September 2026. https://claude.com/blog/projects-redesigned

Stevie Bonifield, The Verge, 17 September 2026. https://www.theverge.com/ai-artificial-intelligence/997134/anthropic-claude-code-projects