Claude Code now reports parallel work in the main project chat

Anthropic has updated Projects in Claude Code so the main conversation can volunteer progress reports from parallel tasks. In a November 13 announcement, the company said the Claude session that coordinates the project now answers questions there and gives updates on ongoing work. A developer who handed off several jobs can see which one has a result or needs a decision before opening each worker's conversation.

Anthropic introduced the Projects beta on September 17. Its original design already divided a project goal among several work threads. The November change brings reports from those threads into the conversation where the developer made the request. The coordinator sees what the threads report, according to the Claude Code documentation. The details of a test failure or the files a worker inspected are still in that worker's conversation.

Progress in the main chat, alternatives in separate threads

When a message comes into the project chat, Claude can answer there, send the request to a thread already working on it, or start a thread. It can also separate unrelated jobs that arrive in the same message. Writing directly in a thread reaches that worker. In cloud coding work, individual threads can make changes on separate branches and open pull requests when appropriate.

Anthropic also announced that two commands now work inside projects. The first, `/btw`, moves a side question into its own thread. The second, `/fork`, starts another thread from the current conversation so the developer can try a different approach. A reminder can bring back work that needs attention later. Anthropic says setting one sets the thread aside until the chosen time, when it reappears and Claude mentions it in the project chat.

Some work needs the developer's machine

A thread normally runs as a separate Claude Code session in the cloud. It can use repositories and files attached to the project and starts with the project's instructions. Cloud workers can continue after the developer closes a laptop. If two threads edit overlapping code, conflicts still have to be handled through the normal merge process.

For work that needs a local file or development tool, the documentation describes a separate path. A developer grants access to a folder on their own computer, and the thread uses that machine's tools and permission settings through Claude Code's Remote Control feature. That option requires version 2.1.280 or later, and the thread pauses if the computer sleeps. Other threads can keep running in the cloud. If a cloud thread asks for permission during a task, the corresponding approval prompt is inside that thread.

Who gets the beta and how usage adds up

The November announcement lists the web and desktop as places to use the updated experience and says the latest mobile app has the new design. It lists Pro and Max for the beta. The Claude Code documentation, checked November 14, also lists Ultra and says Projects has yet to reach Team or Enterprise. The rollout is gradual, so the project menu may not appear on every eligible account at the same time.

While reports now come to one conversation, each worker is still a full session that draws from the subscriber's allowance. The coordinator uses part of that allowance to read reports and decide what to do next. A thread can also use more of the allowance if it wakes to respond to a failed pull-request check or a review comment. Under the default setting, a thread paused by a usage limit resumes when the limit resets. Work it does after resuming counts toward the next usage window. The project's usage page shows tokens by thread and by model and separates the main conversation's use.