<- all tokdocs

Claude Code Projects: How the Beta Works and How It Differs From Subagents

By , founder of Mavric and Apso

View on TikTok ->

Projects in Claude Code lets one ongoing conversation start and track parallel cloud sessions, called threads, that keep working after you close your laptop. It is a public beta for Pro and Max plans with its own documentation page, not a secret feature. Each thread has its own context window, which subagents also have, so the real difference is scope and persistence.

What is Claude Code Projects?

A TikTok from @chase_ai_ calls it "a secret feature hidden behind a waitlist." Anthropic documents it at Let Claude coordinate ongoing work with Projects, and the video itself shows that page.

The docs describe threads as "parallel cloud sessions that share repositories, instructions, and memory." You send work to the project conversation, and the coordinator "takes what you send, decides what becomes a thread, and keeps track of every thread it started." A cloud thread "works on its own branch and opens a pull request when the work calls for one."

Anthropic announced it on 2026-09-17 in Projects redesigned: from folder to conversation: "Starting today, updated projects are available in beta to select Claude Pro and Max subscribers who use cloud sessions in Claude Code."

The name overlaps with an older feature. Projects in claude.ai chat are "self-contained workspaces with their own chat histories and knowledge bases," per the support article. The Claude Code version is a redesign, and the waitlist page says "It's new in Claude Code and an upgrade for the projects you already have in chat and Cowork."

Who can use Claude Code Projects?

The docs callout says "Projects are in public beta on Pro and Max plans and rolling out gradually." They "aren't available on Team or Enterprise plans yet." If Projects does not appear in the sidebar at claude.ai/code or in the desktop app's Code tab, you can join the waitlist.

Threads that work on code also need the Claude GitHub App installed on each repository they clone, according to the cloud sessions page. The video mentions neither requirement.

How long is the waitlist?

The waitlist is at claude.com/form/projects, which says "We are rolling out Projects in stages. Join the waitlist to get earlier access." The video says you get off it "in less than 24 hours", but no Anthropic source gives an approval time.

On 2026-10-09, @ClaudeDevs posted "We just let in every Pro and Max user from the Claude Code Projects waitlist!" followed by "We're letting in more Pro and Max users as capacity allows." The video went up eight days later, so a quick approval fits the creator's experience, but admission depends on capacity.

Does Claude Code Projects run with your computer off?

Yes, for cloud threads. The docs say "Cloud threads keep going after you close your laptop, while a thread on your computer runs only while that computer is awake." Three limits apply:

  • Plan usage. "A project uses your limits faster than a single session does, and on a Pro plan in particular you should expect to reach your limit sooner on days you run one." A thread that hits a limit "keeps retrying on its own and continues when the limit resets."
  • Daily cap. "The enforced limit is 200 new threads per day across your projects."
  • Idle expiry. Cloud sessions "stop after a period of inactivity and the session's VM is reclaimed." Reopening restores the conversation but not background work that was still running.

The video's line about talking "with one agent instead of 20" has no fixed number behind it. The docs say "There's no fixed number; Claude starts as many as the work calls for."

Do threads share memory and context?

They share standing context, not a conversation. Project memory is a set of files, and "Every cloud thread reads the index file MEMORY.md when it starts." Project instructions are "Text sent to each new thread and to Claude in the project conversation, up to 16,000 characters." Each cloud thread also starts with the project's repositories, the CLAUDE.md and skills in each, and your claude.ai connectors.

Each thread is "a separate session with its own context window that does one piece of work and reports back to the conversation when it finishes." The coordinator "sees what threads report back, not every step they take."

Threads can also run on your own computer through Remote Control, with Claude Code v2.1.280 or later. A local thread "Starts with the project's instructions, but not with its memory files loaded." The Sept 17 announcement called local threads "coming very soon", and the video describes the cloud-only version.

Claude Code Projects vs subagents

The video says projects differ from subagents because each session has "their own memory, their own context window, and they are persistent." The context window point is wrong. The subagents docs say "Each subagent runs in its own context window with a custom system prompt, specific tool access, and independent permissions."

The docs draw the line by scope: "a subagent runs inside one session, does a side task in its own context window, and returns a summary to that session. A project's threads are whole sessions that Claude starts and that report back to the project conversation, and a thread can still use subagents for its own side tasks."

Persistence is a real difference. "Each subagent invocation creates a new instance rather than continuing an earlier one," while a thread is a session you can open, steer and follow up on. Memory is a partial difference: a non-fork subagent does not load auto memory by default, while every cloud thread reads project memory at start.

Bottom line

Claude Code Projects is a documented public beta for Pro and Max plans, with Team and Enterprise excluded for now. Cloud threads keep running when your laptop is closed, within plan limits and a 200-thread daily cap. Threads share memory and instructions but each has its own context window, as subagents do. The difference is that a thread is a whole, persistent session.

Sources

Published October 17, 2026. Based on a TikTok by @chase_ai_. Full video notes (markdown)