Quick Facts
- Claude Code Projects launched Sept. 17, 2026, replacing the old folder-based project structure with a persistent coordinator conversation that manages parallel cloud coding sessions.
- Each project can run up to 200 new threads per day, with every thread operating as a full Claude Code cloud session on its own branch and repository copy.
- Claude Code has reached an estimated $2.5 billion annualized run-rate by early 2026, six months after its public release in May 2025.
Anthropic on Thursday launched Claude Code Projects, a redesigned system that turns a single conversation into a persistent coordinator capable of spinning up and managing multiple concurrent cloud-based coding sessions at once.
The feature went into beta on Sept. 17 for select Claude Pro and Max subscribers who use cloud sessions in Claude Code and have no existing projects on the web or desktop. Anthropic said access will expand to more users on those plans within a week, with Team and Enterprise plan support to follow.
How It Works
The old project structure was a folder holding files and one chat. The new structure is an ongoing conversation where Claude acts as a coordinator. A developer describes the work, and Claude decides what becomes a thread.
Each thread is a full Claude Code cloud session running on its own branch and its own copy of the repository. Threads execute in parallel, report outcomes back to the coordinator conversation, and continue running after the developer closes their laptop. Anthropic describes the interaction as briefing a chief of staff: hand Claude several tasks at once, in any order, and it routes each to a new or existing thread.
The coordinator reads what developers send, answers quick questions directly, and starts threads for substantive work. It monitors what threads report back rather than every step they take. Threads can further split delegated work into subagents, loops, and workflows when needed. With a repository connected, a thread opens pull requests and runs tests. Overlapping work between threads resolves as a standard merge conflict.
Usage and Limits
A new project defaults to running Anthropic’s Opus model, with high effort for threads and low effort for the coordinator conversation. Parallel threads consume plan limits faster than single sessions. Anthropic caps the system at 200 new threads per day across all projects. A thread that hits a usage limit waits and resumes on its own.
Developers can monitor and redirect ongoing work from a phone while worker sessions run remotely. Shared project memory and instructions carry forward to every new thread automatically, so context does not need to be re-established each session.
Business Context
Claude Code’s commercial trajectory sets the backdrop for the launch. The product hit $1 billion in run-rate revenue within six months of its May 2025 public release. By early 2026, it had reached an estimated $2.5 billion annualized run-rate, with weekly active users doubling since January 1. GitHub Copilot took three years to reach $1 billion in annual recurring revenue.
Anthropic CEO Dario Amodei reported that first-quarter 2026 revenue and usage grew 80x on an annualized basis, against the 10x the company had planned. Claude Code now accounts for a meaningful share of Anthropic’s overall $14 billion annualized revenue.
Anthropic co-founder and President Daniela Amodei said developers are “the most important users of Claude.” The company frames 2026 as the year agentic coding moves from an individual productivity tool to a core business capability.
What It Means for Software Teams
The competitive question in AI coding has shifted. OpenAI, GitHub, and Google can each run agents asynchronously and in parallel. The harder problem is coordination: what remembers accumulated decisions across sessions and where developers manage work that outlives any individual conversation.
Claude Code Projects positions Anthropic’s answer as one persistent coordinator conversation backed by shared memory and a rotating pool of worker threads. For software teams on Pro, Max, Team, or Enterprise plans, the practical effect is that large multi-part builds no longer require manual handoffs between sessions. The coordinator holds the thread.