Skip to content
AI Primer
release

Claude Code Projects reportedly adds separate coordinator and thread model settings

TestingCatalog reports that Claude Code Projects lets users choose separate coordinator and thread models. Wes Roth also reports /btw side threads, /fork alternatives and coordinator progress updates during parallel work.

3 min read
Claude Code Projects reportedly adds separate coordinator and thread model settings
Claude Code Projects reportedly adds separate coordinator and thread model settings

TL;DR

  • Coordinator and worker-thread models can now be selected separately in Project settings, according to testingcatalog.
  • The coordinator answers questions and reports parallel-work progress in the main chat; /btw and /fork also work in Projects, as WesRoth's update describes.
  • Read-only thread links require recipients to sign in to Claude and exclude threads that accessed your computer, ClaudeDevs says.

Anthropic's architecture guide says the coordinator sees what workers report back, rather than every step they take. Its redesign announcement describes a project goal of reducing checkout p75 latency, with endpoint profiling, optimization tests, and PRs delegated to parallel threads.

Coordinator and thread models

Independent model selection is the standout control in this refresh. TestingCatalog reports separate project-level choices for the coordinating conversation and the worker threads.

Project goals and progress updates

The goal belongs to the project and lives under Project settings → General, according to testingcatalog's reply. The coordinator distributes the work; TestingCatalog says a per-session /goal would compete with that project-wide objective.

The updated coordinator also answers questions in the main project chat and posts status updates while threads run in parallel.

Side threads and forks

The two commands now work inside Projects:

  • /btw gives a side question its own thread, keeping the current thread on topic.
  • /fork starts a new thread from the current one to explore another approach.

Reminders and artifact views

Anthropic describes the first three changes in its release thread; testingcatalog also reports custom views:

  • Reminders: Set one on a thread, or ask Claude to remind you. The thread disappears until the reminder is due, then returns and gets mentioned in the project chat.
  • Recent artifacts: A row at the top of the threads panel surfaces artifacts recently opened, updated, or pinned.
  • Thread thumbnails: Each thread shows its own artifact thumbnails, with an option to disable them in view settings.
  • Custom views: Users can create views and assign artifacts to them.

Read-only thread sharing

An individual thread can be shared through its menu with anyone signed in to Claude. Threads that had access to your computer cannot be shared.

Local permissions also produced a concrete snag: one Hacker News user reported a file write being blocked because approval arrived through the coordinator rather than directly from the user in the worker thread.

Beta access and token overhead

Anthropic's rollout announcement lists Projects as a public beta for Pro and Max on web and desktop, with a waitlist for accounts awaiting access. The latest mobile app also carries the new design.

Projects draws on the same plan limits as other Claude Code sessions, according to Anthropic's documentation. Boris Cherny, from the Claude Code team, said on Hacker News that internal A/B tests and evaluations put coordinator token overhead below 10% compared with running sessions directly.

Further reading

Discussion across the web

Where this story is being discussed, in original context.

On X· 4 threads
TL;DR1 post
Coordinator and thread models1 post
Project goals and progress updates1 post
Reminders and artifact views1 post
Share on X