Claude Code Projects: Parallel Cloud Session Threads From One Conversation
Claude CodeAnthropic redesigned Claude projects from a folder-based structure into a single ongoing conversation, rolling it out in beta on September 17, 2026. Instead of organizing a project as a folder, a user briefs it the way they would brief a chief of staff, and Claude routes the work to new or existing threads, each running as its own Claude Code cloud session on its own branch of the repository. Threads share memory and a common library of files and artifacts, so Claude retains project decisions, timelines and stakeholder details across sessions instead of needing to be re-briefed.
Key Takeaways
- Projects moved from a folder-based structure to a single ongoing conversation: a user briefs the project like a chief of staff, and Claude routes work to new or existing threads.
- Each thread runs as its own Claude Code cloud session on its own branch, so parallel work streams do not overwrite each other's changes.
- Threads share memory and a common library of files and artifacts, so Claude retains project decisions, timelines and stakeholders instead of being re-briefed each session.
- Users can follow progress from the main project conversation or open an individual thread and redirect it, including from a phone.
- Beta access began September 17, 2026 for a subset of Pro and Max subscribers using cloud sessions, with Team and Enterprise plans to follow.
- Because Projects can run multiple simultaneous cloud sessions, it can consume usage limits faster, and merge conflicts between threads still need manual resolution.
Sources & Mentions
3 external resources covering this update
From Folder to Conversation
Anthropic's blog post "Projects redesigned: from folder to conversation," published September 17, 2026, describes a new experience for Claude projects, available in beta. Rather than organizing a project as a folder of files a user manages by hand, the redesigned version treats a project as one continuous conversation. A user briefs Claude the way they would brief a chief of staff, and Claude scopes the request, delegates the pieces, coordinates parallel work, reviews the outputs and assembles the result.
How Threads Work
Claude routes work to new or pre-existing threads. For repository-based work, each thread runs as its own Claude Code cloud session, on its own branch and its own copy of the repository, so multiple parts of a task can move forward at once without one thread overwriting another's changes. Threads can spawn their own subagents, loops and workflows for larger pieces of work, and draw on connected APIs, repositories and documents as needed.
Memory That Persists
Every thread adds to, and draws from, memory shared across the whole project, along with a common library of files and artifacts. That reduces the need to re-explain context: Claude retains a project's decisions, timelines and stakeholder details over time instead of requiring the same background in every new session.
Rollout and Trade-offs
A user can follow a project's progress from the main project conversation, or open an individual thread to watch it directly and redirect it, including from a phone. Beta access began September 17 for a subset of Claude Pro and Max subscribers who already use cloud sessions and have no existing projects, with wider Pro and Max access due within the week and Team and Enterprise plans to follow. Anthropic says running Projects on a local machine is coming.
The redesign does not remove the ordinary coordination costs of parallel development. Because a project can run multiple simultaneous cloud sessions, it can consume usage limits faster than a single session, and conflicting changes between threads still have to be resolved by hand.