AI News · 6 min read
Claude Code Projects coordinator turns proactive
On November 13, 2026, Claude Code Projects added a proactive coordinator, /btw, /fork, reminders, and read-only thread links, plus desktop themes.
What ClaudeDevs posted on November 13
On November 13, 2026 at 22:51 UTC, @ClaudeDevs ↗, Anthropic's account for developer updates, posted: "The coordinator is now much more proactive. It answers your questions in the project chat and gives you updates on the status of your ongoing threads."
The picture above is ours.
The next posts in that thread, from the same account, add the controls:
| Post | What ClaudeDevs wrote |
|---|---|
| /btw and /fork ↗ | "/btw and /fork work in projects now too." /btw "gives it its own thread so your current one stays on topic." /fork "starts a new thread from the one you're in." |
| Reminders ↗ | "You can also set a reminder on any thread, or just ask Claude to remind you. The thread moves out of your way until then. When it's time, it moves back and Claude brings it up in the project chat." |
| Read-only links ↗ | "You can now share an individual thread as a read-only link with anyone who's signed in to Claude. Open the thread's menu and pick Share! Threads that had access to your computer can't be shared." |
| Threads panel ↗ | Recent threads on top, plus artifact thumbnails you can turn off in view settings. |
| Where it runs ↗ | Web, desktop, and the latest mobile app. "Projects is in public beta on Pro and Max." Waitlist: claude.com/form/projects ↗. |
The commands page ↗ still describes the terminal versions differently. There, /btw is a side question that does not enter the conversation, and /fork copies the session into a background session. The Projects posts describe a thread either way.
Who has it, and what a new project spends
The Projects docs ↗, fetched November 14, and the thread do not use the same plan list.
| ClaudeDevs, November 13 | Projects docs, fetched November 14 | |
|---|---|---|
| Plans named | Public beta on Pro and Max | Public beta on Pro, Max, and Ultra, rolling out gradually |
| Team and Enterprise | Not named in that post | "aren't offered on Team or Enterprise plans yet" |
| If you do not see it | Join the waitlist | Sidebar, or under More. The rollout started with accounts that have used cloud sessions and do not already have projects in claude.ai chat or Cowork |
| Where | Web, desktop, latest mobile app | claude.ai/code, the desktop app, and the Claude mobile app. Not the terminal, VS Code, or JetBrains |
A project is one conversation. Claude starts a thread per task, usually a cloud session on its own branch. The docs say a new project "runs Opus everywhere, with high effort for threads and low effort for the conversation," and that high-effort Opus "draws on your plan fastest." Auto-continue when usage limits reset is on by default, so a thread that stops at a limit continues when the limit resets. Turn it off under Project settings > General.
The pool is the same one as your other Claude Code sessions. The docs say a project spends it faster than a single session, and that on Pro you should expect to hit the limit sooner. The enforced cap is 500 new threads per day across your projects. A number you type in chat is a preference, not that cap.
The docs page had not caught up with Share on November 14. It still says you cannot share a project or its threads. ClaudeDevs says the thread menu has Share, the link is read-only, the recipient signs in to Claude, and a thread that touched your computer cannot be shared. Check the menu. A local thread uses Remote Control and runs only while that computer is awake, which is the case the post excludes from Share. What that session can read on disk is Claude Code settings and local JSON.
Desktop themes, the same night
At 23:59 UTC the same night, @ClaudeDevs ↗ posted: "You can now build custom themes for Claude Code on desktop with mods! Change the colors, add an animated background, and make it your own. Just tell Claude how you want it to look, or get started quickly with the theme-examples plugin."
The follow-up ↗ says themes work in local desktop sessions today and cloud support is coming soon. The mods docs ↗ say Code-tab colors need v2.1.324 or later, the terminal keeps its own colors, and a backdrop via $.theme.set needs v2.1.319 or later. The terminal draws no backdrop. You describe the colors in a local Code-tab session, or you write the mod. The theme-examples plugin is named in the post, not in that docs section.
What people are saying
"It fully replaced running Claude Code on my own machine through Remote Control" — Vox (@Voxyz_ai) ↗
"big change for Claude Code projects, the proactivity of the coordinator was the main issue" — Anthony Kroeger (@kr0der) ↗
"The catch in the docs: new projects default to Opus everywhere and turn on auto-continue after usage resets by default." — Tekon Burns (@TekonBurns) ↗
"Less thread-watching, not hands-free coding: developers still resolve merge conflicts, and workers share usage limits." — Hamza Chishti (@haamzaC) ↗
"i already run claude code + codex side by side. do i actually need a manager on top of that?" — Kyson (@KysonBuilds) ↗
Reddit was not reachable for this story.
Tekon's catch matches the docs. None of these accounts is Anthropic's. Vox is describing his own switch. Remote Control is still how a project thread runs on your computer.
Our take
Use it if you already have Projects and you still merge the results yourself. Status now lands in the project chat. A reminder parks a thread until a time you set. /btw and /fork branch a tangent. You still open the pull request. Hamza's line holds: less thread-watching, not hands-free coding, and the workers share your limits.
Change the defaults before the first batch. Opus everywhere plus auto-continue spends the next window after you hit the cap. Check Thread model and Thread effort, and ask for fewer threads, before a large run. On Pro, one busy project ends the day early. Other harness prices are in cheaper Claude Code alternatives and the Claude Code review.
Skip it for a team seat. The post names Pro and Max. The docs add Ultra and still leave out Team and Enterprise. A read-only link, once Share is actually in the menu, shows one thread to someone signed in to Claude. It does not add a teammate. Cursor's multiplayer Projects share a board, and each person's coordinator bills as them. If you already run Codex beside Claude Code, Kyson's question stands: a coordinator is another layer on the same pool. That comparison is Codex vs Claude Code.
Themes stay on the local desktop app for now. Update, try a local Code-tab session, and wait on cloud sessions until that follow-up ships. The terminal picker is a separate theme system.