Claude Code Projects get a coordinator and parallel threads

Anthropic redesigned Claude Code Projects (beta): a project is no longer a folder you manage by hand. You set a goal and repo/context; a coordinator Claude scopes the work, delegates across parallel threads, reviews outputs, and assembles the result — including after you leave the desk, with phone steering.

What shipped: Each thread is a Claude Code cloud session on its own branch/copy of the repo. Threads can open PRs, run tests, and further split work via subagents/loops/workflows. Shared project memory accumulates decisions and style; a library holds added files and Claude artifacts. Users configure cloud environment, connectors, plugins, instructions, and model/effort for coordinator and workers. Overlap on the same code resolves as normal merge conflicts.

Limits / who: Starting for select Claude Pro and Max subscribers who use cloud sessions in Claude Code and have no existing projects on web or desktop. Access expands to more Claude Code users on those plans over the coming week; updated projects across all of Claude, plus Team and Enterprise, come later. Waitlist if you’re on Pro/Max without access. Old-style projects keep working until the upgrade reaches chat/Cowork.

What it cannot do yet: Threads do not run on your machine behind your network today — “coming very soon.” Multi-thread cloud projects can hit usage limits faster — Anthropic says check project-specific usage.

Who it is for: Paid Claude Code users who want long-running, multi-repo agentic builds without manually stitching sessions. Not a Free-tier or day-one Team/Enterprise ship.

Risk: A coordinator that keeps opening PRs and running tests after you walk away is an autonomy product. Default steering and merge-conflict discipline matter; treat Anthropic’s “you can steer throughout” as the control claim, not an audit. Shared memory that learns release dates and who owns billing is also a secrets/ACL surface.

What’s next: Local-thread ship; Team/Enterprise dates; waitlist clearance pace; whether existing project upgrades preserve memory cleanly.

— Rowan Keel