Claude Code Projects: Power-User Guide to /btw, /fork and Reminders

Last updated: November 16, 2026

On November 13, 2026, Anthropic updated Claude Code Projects so the coordinator answers questions and posts thread status updates on its own. Projects also gained /btw and /fork, thread reminders, read-only thread sharing and a recents row for artifacts. Projects remain a public beta on Pro, Max and Ultra plans.

Contents

What is new in the November 13 update

Anthropic’s developer account @ClaudeDevs announced the changes on X on November 13, 2026. The headline change is the coordinator, the Claude instance that runs the project conversation. Anthropic says it is now “much more proactive”: it answers your questions in the project chat and gives you updates on the status of your ongoing threads.

Feature What it does How to use it
Proactive coordinator Answers questions in the project chat and reports thread status without being asked Ask questions in the project conversation
/btw Gives a side topic its own thread so the current thread stays on topic Type /btw followed by the side task
/fork Starts a new thread from the one you are in Type /fork in a thread to try another approach
Reminders Moves a thread out of the way, then brings it back in the project chat when due Set a reminder on a thread, or ask Claude to remind you
Thread sharing Read-only link for anyone signed in to Claude Thread menu, then Share
Recents row Recently opened, updated or pinned threads, with artifact thumbnails Top of the threads panel; thumbnails can be turned off in view settings

Anthropic also says project settings and local folder access are simpler, the changes are on web and desktop, and the latest mobile app has the new design. Threads that had access to your computer cannot be shared, according to the sharing announcement.

How a project works

Anthropic introduced the redesigned, conversation-based Projects in Claude Code in beta on September 17, 2026, in its “Projects redesigned” article. The November update builds on that design.

Per the Claude Code Projects documentation, a project is one long-running conversation where Claude acts as coordinator. It decides what becomes a thread and tracks every thread it started. Each thread is a separate session with its own context window. A cloud thread works on its own branch and opens a pull request when the work calls for one.

Every cloud thread starts with the project’s repositories, files, instructions and memory, each repository’s CLAUDE.md, your claude.ai connectors and the cloud environment. It does not load repository skills, .claude/settings.json or .mcp.json.

Plans, apps and access

Item Status per Anthropic docs
Plans Public beta on Pro, Max and Ultra, rolling out gradually
Team and Enterprise Not offered yet
Where it runs claude.ai/code, Code tab of the desktop app, Claude mobile apps for iOS and Android
Not available Terminal CLI, VS Code extension, JetBrains plugin, Amazon Bedrock, Google Cloud’s Agent Platform, Microsoft Foundry
Default models Opus everywhere, high effort for threads, low effort for the coordinator
Project instructions Up to 16,000 characters
Thread limit 500 new threads per day across your projects

If you do not see Projects in the sidebar at claude.ai/code or the desktop Code tab, check under More. If it is not there, the rollout has not reached your account and you can join the waitlist.

How to start a project

  1. Confirm the prerequisites: a Pro, Max or Ultra plan, code on github.com, push access, and the Claude GitHub App installed. A token from /web-setup is not enough for project threads.
  2. Open Projects at claude.ai/code or in the desktop Code tab, or go to claude.ai/code/projects/browse, and select New project.
  3. Enter a name. Optionally add a one-line goal under “What do you want to work on?” and add repositories, files, folders or Google Drive folders.
  4. Click Create project. On your first project, Claude may take a turn of its own, which uses your plan.
  5. Open Project settings, then Memory, then Project instructions, and write the brief every thread should follow.
  6. Set the thread and coordinator models and effort in Project settings, then General.

Power-user workflows

Keep threads focused with /btw. When a thread on one bug surfaces an unrelated issue, use /btw to spin it off. The original thread keeps a clean context.

Compare approaches with /fork. Fork a thread when you want to test a second fix or design without discarding the first.

Tell the coordinator how to run. The docs list instructions such as “Run at most two threads at a time”, “Only post when something finishes or is blocked” and “Don’t open a pull request until I’ve seen the plan”. Claude saves these to project memory, but they are preferences, not enforced caps. Put exact rules in project instructions.

Run local-only tasks on your machine. For a local database or an API behind a VPN, choose Work locally from the + menu. The computer needs Claude Code v2.1.280 or later, with Remote Control on in the desktop app or claude remote-control running in the folder. Add --spawn worktree to give each thread its own worktree.

For a single task, the docs recommend a plain cloud session instead. If you run several local sessions yourself, see our guide to OpenCode background subagents for a terminal-first alternative, or Cursor Projects multiplayer for shared team agents.

Usage limits and cost

Anthropic lists no separate price. Project usage counts against the same plan limits as your other Claude Code sessions, and the docs warn that projects use them faster, especially on Pro. Our explainer on Claude Code usage limits and our Claude Code cost breakdown cover the plan side.

Running threads, the coordinator itself, and threads watching a pull request all use your plan. An idle or archived project does not. The cache lifetime on Pro, Max and Ultra is one hour, so reviving a long-idle thread re-reads its whole conversation. Starting a fresh thread can be cheaper. Check token use by thread and model in Project settings, then Usage.

Limitations

  • Beta rollout. Access is gradual, and there are no organization-level controls during the beta.
  • Sharing. As fetched on November 16, the docs still say threads cannot be shared with another user, while Anthropic’s November 13 post says read-only thread links are available. Check the thread menu for Share before relying on it.
  • Uncommitted work. If a paused cloud sandbox cannot resume, the thread continues from a fresh clone, so ask Claude to commit and push work in progress.
  • Local settings ignored. Cloud threads skip repository hooks, permission rules and MCP files. Our Claude Code Code Mode guide and Claude Code memory explainer cover how local sessions differ.

Frequently asked questions

What changed in Claude Code Projects on November 13, 2026?

The coordinator became more proactive, answering questions and posting thread status updates. Anthropic also added /btw and /fork, thread reminders, read-only thread sharing and a recents row with artifact thumbnails.

Who can use Claude Code Projects?

Projects are a public beta on Pro, Max and Ultra plans, rolling out gradually. They are not offered on Team or Enterprise plans yet, and there is a waitlist.

Can I use Claude Code Projects in the terminal CLI?

No. Projects work at claude.ai/code, in the desktop app and in the mobile apps, not in the CLI, VS Code or JetBrains. A thread can still run on your computer through Remote Control.

What do /btw and /fork do in a project?

Per Anthropic, /btw gives a side topic its own thread, and /fork starts a new thread from the current one so you can try a different approach.

Do Claude Code Projects cost extra?

No separate price is listed. Projects draw on your normal Claude Code plan limits, but faster, because several threads run at once. Usage credits apply only if you turned them on.

Sources

Related answers

Leave a Comment