Claude Code Projects: proactive coordinator, /btw, /fork

The coordinator in Claude Code Projects now answers questions in the project chat and posts status updates on running threads without being asked, the Claude Code team said in a post on X on November 13. Threads that are waiting for input, finished or blocked now show up in that main conversation, where before they had to be spotted by watching the thread list; the change ships in the Projects public beta on Pro and Max.

A project is one long-running conversation in which a coordinator hands tasks to threads, and each thread works on its own branch and copy of the repo. When two threads touch the same code, the overlap comes back as an ordinary merge conflict once the branches are combined, so work with strict dependencies still needs someone to sequence the pull requests.

Side threads, reminders and links

Two slash commands from regular Claude Code sessions now work inside projects. /btw gives something that comes up mid-task its own thread, so the current one stays on topic. /fork starts a new thread from the state of the one you’re in, for trying a different implementation or debugging path without losing the original.

Any thread can also get a reminder, set directly or by asking Claude. The thread moves out of the way until then; when the time comes, it moves back and Claude brings it up in the project chat. That fits work waiting on a later review, a deployment or an outside reply.

Sharing works one thread at a time: pick Share in the thread’s menu and you get a read-only link that anyone signed in to Claude can open, without the rest of the project. Threads that had access to your computer can’t be shared, and since Anthropic added local support for Projects threads in September, a thread that ran on your own machine falls under that rule. The restriction appears meant to keep local files and shell output out of shared transcripts.

Artifacts are easier to get back to as well. The threads panel now opens with a row of recently opened, updated or pinned threads, and each thread shows thumbnails of its own artifacts, which can be switched off in the view settings.

What the threads cost

Projects carry no separate fee, but every worker is a full Claude Code session drawing on the subscriber’s existing allowance, so several high-effort threads running at once can exhaust plan limits faster than a single session. Accounts are capped at 200 new threads a day across all projects. A thread that hits a usage limit pauses and resumes automatically when capacity frees up.

Project usage appears separately in the usage controls, and the model and effort level can be set for the coordinator and for worker threads. New projects default to Opus in both roles, with low effort for the coordinator and high effort for workers, so the setting that multiplies with every new thread is already the expensive one. Small changes that fit one branch and one context window generally use fewer resources in a regular Claude Code session.

Who can get in

Projects opened as a beta on September 17 for selected Pro and Max subscribers and is now a public beta on those two plans; Team and Enterprise plans remain unsupported, AlphaSignal reports. The redesign also simplifies project settings and local folder access. Everything is live on web and desktop, and the latest mobile app has the new design. Pro and Max subscribers who don’t have Projects yet can join the waitlist.