Claude's Projects Redesign and Co-work Merger: Who Actually Has Access
Anthropic is merging Claude Co-work into Chat and rebuilding Projects around conversations, but the rollout is staggered and most users are locked out.
What is changing in Claude Projects and Co-work?
Anthropic announced two structural changes to Claude at once. First, Claude Co-work and Claude Chat are being merged into a single interface, so users no longer have to switch between a “chat” mode and a “co-work” mode to get different kinds of help. Second, Claude Projects is being rebuilt from the ground up, moving away from the old folder-based model (where a project was basically a container of files and instructions) toward a conversation-based system built on Claude Code sessions. Anthropic’s own framing for this is “from folder to conversation.” Neither change is fully available to the general Claude user base yet. Both are rolling out in stages, and access depends heavily on which plan you’re on and whether you already use Claude Code.
TL;DR
- Anthropic is merging Co-work and Chat into one unified experience inside the Claude app, cutting down on the friction of switching between modes.
- The merger is rolling out first to Pro and Max subscribers across web, desktop, and mobile, with wider availability promised “over the coming weeks.”
- The new Projects design treats a project less like a folder of files and more like a standing conversation with a chief of staff that assigns and tracks work.
- Under this redesign, each work thread runs as its own Claude Code cloud session operating on a separate branch and copy of a repository, and conflicting changes get resolved like a normal pull request merge conflict.
- Beta access to the new Projects is currently limited to select Pro and Max users who already use Claude Code sessions and, critically, only if they have no existing projects on web or desktop.
- Anyone with existing web or desktop projects is excluded from the beta for now, and everyone else can only join a waitlist.
- The announcements highlight a recurring pattern in AI product releases: features get announced as “available” before they’re actually usable by most of the audience being told about them.
How does the new Projects system actually work?
The redesigned Projects starts with a goal instead of a folder. When someone creates a project, they pick a goal and connect it to a repository or other context, and Claude begins suggesting work it can start on immediately. From there, users can configure the project’s environment: cloud settings, connectors, plugins, custom instructions, and which model handles the work.
The interaction model is closer to managing a team than editing a shared document. There’s a main project chat that acts as a coordination layer, and individual threads that branch off from it to handle specific pieces of work. Users can either steer things from the main chat, treating it like briefing a chief of staff, or drop into a specific thread to examine and direct the details of that piece of work directly.
Technically, each thread is a separate Claude Code cloud session, and each one works on its own branch and its own copy of the underlying repository. When two threads happen to touch the same code, the system resolves the overlap as a merge conflict, the same way a human team would handle two people editing the same file in parallel. Context is meant to accumulate across the life of the project rather than resetting between sessions, so the project theoretically gets more useful the longer it runs.
This is a meaningfully different mental model from the original Projects feature, which was essentially a way to group files, custom instructions, and chat history under one roof. The new version behaves more like an orchestration layer for multiple parallel coding sessions than a static workspace.
Who actually gets access right now?
This is where the rollout gets messy. According to Anthropic’s own announcement, the updated Projects experience is available in beta only to “select” Claude Pro and Max subscribers who already use Claude Sessions in Claude Code, and only if they don’t have any existing projects on web or desktop. That last condition matters: if someone has been using the older Projects feature at all, they are currently locked out of the new one, regardless of their subscription tier.
Anthropic says access will expand to more Claude Code users on Pro and Max plans “over the coming weeks,” with support for Team and Enterprise plans coming after that. Pro and Max users who don’t have access yet can join a waitlist. There’s no committed date for when the feature reaches everyone.
The Co-work and Chat merger follows a similar staggered pattern. Anthropic’s announcement states it’s rolling out to Pro and Max plans first, across the Claude app on web, desktop, and mobile, over the coming weeks, for both existing and new users on those plans. Notably, even users on the $200/month Max plan aren’t guaranteed to have it the day it’s announced. Anthropic has confirmed the feature is live for some accounts, but plenty of paying subscribers, including on the top-tier plan, are still seeing the old separate Chat and Co-work options.
Why does Anthropic keep announcing features before they’re available?
This is a pattern worth naming because it’s not unique to Anthropic. AI companies frequently publish blog posts with headlines that declare a feature is “now available” or that two products “are now one,” when the actual rollout is a beta limited to a subset of users, with broader availability promised at some unspecified future point. Google did something similar with Gemini Notebooks (formerly NotebookLM), announcing new audio recording capabilities for its mobile app as a feature “starting next week” rather than something live at the time of the announcement.
The practical effect is that headlines and blog titles can outpace reality by weeks. A post titled “Projects redesigned: from folder to conversation, now available in beta” technically describes something true, it is available in beta, but only for a narrow slice of users who meet specific conditions (Pro/Max, active Claude Code sessions, no pre-existing projects). Someone reading only the headline would reasonably assume the feature is ready to use today. For builders and teams planning workflows around these tools, the gap between announcement and actual access matters: budgeting time or restructuring processes around a feature that isn’t live yet for your account is a common trap.
Is the Projects redesign worth paying attention to?
For anyone using Claude Code for real development work, the redesign looks like a substantive improvement rather than a cosmetic one. Moving from a static folder model to a conversation-driven system that spins up parallel Claude Code sessions, tracks them against branches, and resolves conflicts through standard merge logic mirrors how engineering teams already work with version control. The “chief of staff” framing, where a main thread coordinates and delegates to sub-threads, is a more natural way to manage multiple concurrent AI-driven tasks than manually opening separate chats and losing track of which one is doing what.
Whether it’s worth actively pursuing right now depends entirely on eligibility. If someone is on a Pro or Max plan, already uses Claude Code sessions, and has never created a project on web or desktop, joining the beta or waitlist makes sense. Everyone else is better off treating this as a preview of where Claude is headed rather than a tool to build around immediately.
Frequently Asked Questions
What is the difference between Claude Co-work and Claude Chat?
Co-work and Chat were previously separate modes in the Claude app requiring users to switch between them depending on the type of task. Anthropic is merging them into a single unified interface so that distinction disappears, though the merger is still rolling out gradually rather than being available to all users at once.
Do I need Claude Code to get the new Projects experience?
Yes, at least for now. The beta is limited to Pro and Max subscribers who are already using Claude Sessions within Claude Code. Anthropic says it will expand to more Claude Code users before eventually reaching Team and Enterprise plans.
Why don’t I have access even though I pay for Claude Max?
Plans first. Then code.
Remy writes the spec, manages the build, and ships the app.
Anthropic’s rollout is staggered and appears to exclude users who already have existing projects on web or desktop, regardless of subscription tier. Being on the $200/month Max plan does not guarantee immediate access to either the Co-work/Chat merger or the new Projects beta.
How does the new Projects system handle conflicting edits across threads?
Each thread in a project runs as an independent Claude Code cloud session on its own branch and copy of the repository. If two threads modify the same code, the system treats it as a merge conflict, similar to how conflicting pull requests are handled in standard version control workflows.
When will the redesigned Projects be available to everyone?
Anthropic has not given a firm date. The company says access will expand to more Claude Code users on Pro and Max plans over the coming weeks, with Team and Enterprise plan support arriving after that, and a waitlist available for Pro and Max users without current access.
