Claude Code Projects Update November 2026: Proactive Coordinator, /btw and /fork Threads, Read-Only Sharing
Anthropic's Claude Code Projects got its first major upgrade on 13 November 2026: the coordinator that runs each project is now proactive, answering questions in the project chat and posting status updates as its threads work, instead of waiting to be asked. The update, announced by Anthropic's Claude Developers account that evening, also adds /btw and /fork side threads, read-only sharing links for individual threads, reminders, and a tidier threads panel. Projects remain in public beta on Pro and Max, with a waitlist for everyone who does not have access yet.
A Claude Code Project is one long-running conversation in which Claude acts as a coordinator: you describe the work, Claude scopes it, starts a thread for each task, and assembles the finished result. It is the redesign Anthropic launched on 17 September 2026, replacing the old project-as-folder model. The 13 November update does not change that shape. It changes how much the coordinator does on its own, and how easily you can branch and share the work inside it.
What changed on 13 November
The announcement came as a thread from Anthropic's Claude Developers account at 22:51 UTC on 13 November, and it lists six changes. The headline is the coordinator. "The coordinator is now much more proactive," Anthropic wrote. "It answers your questions in the project chat and gives you updates on the status of your ongoing threads." Until now, the coordinator mostly worked silently and reported back when a thread finished. Now it talks while the work is running.
The second change is side threads. The /btw and /fork commands now work inside projects. "/btw gives it its own thread so your current one stays on topic," Anthropic wrote. "/fork starts a new thread from the one you're in," the way to try a second approach without abandoning the first. Both commands already existed in ordinary Claude Code sessions; what is new is that they now work inside a project.
Third, reminders. "You can also set a reminder on any thread, or just ask Claude to remind you," the announcement says. A thread with a reminder moves out of the way until the time comes.
| Change (13 Nov 2026) | What it does |
|---|---|
| Proactive coordinator | Answers questions in the project chat and posts status updates on running threads |
| /btw | Opens a side thread for a tangent so the current thread stays on topic |
| /fork | Starts a new thread from the current one, to try a second approach |
| Reminders | Set a reminder on any thread, or ask Claude to remind you; the thread moves out of the way until then |
| Read-only thread sharing | Share one thread as a read-only link with anyone signed in to Claude; threads with computer access cannot be shared |
| Threads panel | New row at the top with recently opened, updated or pinned threads |
Fourth, sharing: "You can now share an individual thread as a read-only link with anyone who's signed in to Claude" — but with one hard limit: "Threads that had access to your computer can't be shared." Fifth, the threads panel gets a row at the top "with the ones you recently opened, updated, or pinned," and sixth, "project settings and local folder access are simpler now too." The changes are live on web and desktop, and the latest mobile app has the new design.
![]() |
AI-generated illustration (generated 14 Nov 2026)
How a project actually works
To see why the coordinator matters, it helps to picture the machinery. A project is one coordinating conversation plus the threads it starts. Each thread is a full Claude Code cloud session working on its own branch and its own copy of the repository, so several threads can work in parallel and open pull requests. Every thread adds to and draws from one shared project memory, and a library collects the files you add and the artifacts the threads produce.
The coordinator's job is to scope each request, decide what becomes a thread, keep track of every thread it started, and review what comes back before assembling the result. You steer from the main project chat, even from your phone, or open any thread and steer it directly. Anthropic is explicit about one limit: if two threads touch the same code, the overlap is resolved as an ordinary merge conflict, just like any other pull request. The update does not remove that. It also does not change the cost shape: a project is several full Claude Code sessions running at once, and Anthropic says projects can reach usage limits faster.
Anthropic's two worked examples at launch still describe the intended use: cut an app's checkout latency by profiling each endpoint in parallel threads, or retire a deprecated endpoint by opening one thread per repository to migrate the callers, run the tests and open the pull requests. The 13 November changes make that kind of project easier to supervise — you ask the coordinator where things stand instead of opening each thread — and easier to share, one thread at a time.
Who gets it, and who is still waiting
Access has widened in stages since the September launch. The redesigned Projects experience opened in beta on 17 September 2026 to select Pro and Max subscribers who use cloud sessions in Claude Code and had no existing projects on the web or desktop. On 9 October, Anthropic let in every Pro and Max user from the waitlist. The announcement thread restates the current position plainly: "Projects is in public beta on Pro and Max."
Team and Enterprise plans still come later. Existing projects on Pro and Max keep working as they do today and will be upgraded as the rollout reaches chat and Cowork.
![]() |
AI-generated illustration (generated 14 Nov 2026)
What the update does not do
Three gaps are worth stating plainly. The first is local work. At launch, threads ran in the cloud only, and Anthropic said running them on your machine was "coming very soon." The 13 November thread refers to threads that had access to your computer and to simpler local folder access — but it does not say when local threads arrived. Anthropic's own documentation describes running a thread on your computer through Remote Control for tasks that need something only your machine has.
The second gap is the sharing limit. Read-only links cover individual threads, and only for people signed in to Claude — and never for a thread that had access to your computer.
The third is memory. The shared project memory is the feature that makes a project more than a batch of sessions, but Anthropic has still published no way to read, correct or export it, and the November update does not mention memory controls at all.
Background: Anthropic's proactive-agent push did not start with Projects — Claude Duet is its proactive assistant for small businesses, and Claude Commerce Agents explained covers the shopping agents built on the same pattern. Developers extending Claude Code can use the claude-seo Claude Code SEO plugin, and the Impeccable GitHub skill shows how far community-built Claude Code skills have come.
What to watch next
The next milestones are the ones Anthropic named at launch and has not yet delivered. First, the rollout reaching chat and Cowork, which is when existing projects migrate and Projects stops being a Claude Code-only feature. Second, Team and Enterprise availability. Third, local threads with a stated arrival date, and whether they share the project's memory the same way cloud threads do. Fourth, any documentation on inspecting or exporting shared memory.
![]() |
AI-generated illustration (generated 14 Nov 2026)
Key Takeaways
- On 13 November 2026 Anthropic made the Claude Code Projects coordinator proactive: it now answers questions in the project chat and posts status updates on running threads.
- The update adds /btw side threads, /fork threads, reminders on any thread, and a recents row in the threads panel.
- Individual threads can now be shared as read-only links with anyone signed in to Claude — except threads that had access to your computer.
- Each thread is a full Claude Code cloud session on its own branch and copy of the repository, and overlapping work still surfaces as an ordinary merge conflict.
- Projects remain in public beta on Pro and Max with a waitlist; Team and Enterprise plans still come later.
Conclusion
The 13 November update is a supervision upgrade, not a new product. Projects already let one conversation run many parallel coding sessions; now the coordinator talks while they run, tangents and second attempts get their own threads, and a single thread can be shared read-only. The limits that mattered in September are still the limits now: local threads have no stated arrival date, computer-access threads cannot be shared, and shared memory cannot be inspected.
Sources
- Anthropic — Projects redesigned: from folder to conversation (17 Sep 2026)
- Anthropic, Claude Code Docs — Let Claude coordinate ongoing work with Projects
- CellCog — Claude Code Projects: One Chat Directs Parallel Threads (14 Nov 2026; quotes the Claude Developers thread of 13 Nov 2026, 22:51 UTC)
- AlphaSignal — Anthropic Upgrades Claude Code Projects to Run Parallel AI Workers Hands-Free (13 Nov 2026)



Comments
Post a Comment