Claude Code Projects now run a coordinator over cloud threads

Anthropic redesigned Claude projects on September 17, 2026. The old object was a folder you stuffed with files and chats. The new one is a conversation that owns the work. You describe what needs to get done. Claude scopes it, starts parallel threads, reviews what they produce, and puts the result together. You can steer from the main chat or from your phone. The threads keep going after you leave the computer.

That is the company's pitch. The access line is narrower than the headline.

Who actually has it

Updated projects are in beta for select Claude Pro and Max subscribers who use cloud sessions in Claude Code and who do not already have projects on the web or desktop. Anthropic says it will expand to more Claude Code users on those plans over the coming week, then to the rest of Claude, including Team and Enterprise.

If you are on Pro or Max and do not have it, there is a waitlist. Existing Pro and Max projects keep working as they do today. Anthropic says it will upgrade those as the rollout reaches chat and Cowork.

This is not a claim that every Claude seat has a coordinator tonight. It is a staged Claude Code cloud-session beta.

Threads do the work. Claude directs them.

A project has two parts: worker threads and a coordinator.

When you start one, you pick a goal plus a repo or other context. Claude suggests work it can pick up immediately. You can set the project's cloud environment, connectors, plugins, instructions, and model.

You stay in the main project chat, or you drop into a single thread to steer the details. Anthropic's analogy is briefing a chief of staff. Claude routes work to new or existing threads, checks in, and follows through. With a repository connected, a thread opens pull requests and runs tests. With documents, it reads them and drafts.

Under the hood, each thread is a Claude Code cloud session on its own branch and its own copy of the repo. If two threads touch the same code, the overlap is a merge conflict, the same as any other PR. A thread can split further into subagents, loops, and workflows.

Anthropic's examples are specific. Reduce checkout p75 latency: profile endpoints, test optimizations, open PRs in parallel. Retire a deprecated v1 endpoint across API, web, and mobile repos: one thread per repo to migrate callers, run tests, open PRs, then tell you which merges have to go first.

Memory and a library, not a better paste buffer

Projects are for work that lasts longer than one reply and has more than one part. Every thread writes to and reads from shared memory. Anthropic's examples: the release moved to Friday, why the export was dropped, who to ask before touching billing.

Claude also stores working and communication style. You can ask it to check in more or less often, start fewer new threads, or make updates shorter.

Alongside memory, a library collects files you add and artifacts Claude produces, so later threads can find them.

Usage, local, and what this is not

Several full Claude Code sessions at once can burn usage faster. You can inspect project-specific usage and pick model and effort for the coordinator chat and for the worker threads separately. Claude pricing still lists Projects as a plan feature. It does not publish a Projects SKU.

Threads run in the cloud today. Running on your machine, with local tools, local code, and your network, is "coming very soon." That is Anthropic's phrase. There is no date on the post.

This is not Cursor Projects. Cursor's cut, shipped September 10, is a left-nav coordinator over Cursor Cloud Agents, rolling out inside Cursor. Claude's cut is a Claude Code cloud-session coordinator, in beta for a subset of Pro/Max, with chat and Cowork still on the later list. Same nouns. Different product, different workers, different gate.

It is also not the Claude Code 2.1.232 fork-default story. That was a CLI default. This is a project surface.

When to bother

If you already live in Claude Code cloud sessions, have Pro or Max, and do not have a pile of old web projects blocking the gate, this is the first Anthropic feature that looks like a staffed backlog instead of another chat with a repo attached. Start from projects if the beta is on your account.

If you need local files, internal network, Team/Enterprise, or the old web project you already use, wait. The coordinator is the part to test, not the word "redesigned."