Claude Code Projects multiple agents now lets selected Claude Pro and Max users coordinate parallel cloud coding sessions with shared project memory, separate repo branches, and a coordinator, after Anthropic relaunched the feature on September 17, 2026. The Verge's report on Claude Code Projects said the beta started that day for select Claude Pro and Max subscribers. The product is Claude Code, not the older general Projects feature in Claude chat.
The Claude Help Center page on Projects says the new version is rolling out in stages starting with Claude Code, while existing projects keep working as they do today. Users with access will see Projects in the sidebar of the Claude Code web app and in the Code tab of the Claude desktop app. The Help Center says chat, Cowork, Team, and Enterprise will follow, and Pro or Max users without access can join a waitlist.
Who can use Claude Code Projects multiple agents
Access starts with selected Claude Pro and Max subscribers who use Claude Code cloud sessions. ZDNet's report on Claude Code Projects said Anthropic limited the first wave to Pro and Max subscribers who use cloud sessions in Claude Code and do not have existing projects on web and desktop. Anthropic told ZDNet users already using projects keep their current version for now and will be upgraded later.
The Help Center adds one boundary that matters for teams planning rollout: regular Projects remain available to all Claude users, including free accounts, and free users are limited to five projects. The Verge reported that access will expand later to all Pro, Max, Team, and Enterprise users, as well as Cowork and regular Claude chats. The sources do not give a general availability date, a Team rollout date, or an Enterprise rollout date.
How the cloud threads work
Claude Code Projects works by turning a high-level coding request into named cloud threads that run in parallel. The Verge reported that each thread is a Claude Code cloud session with its own branch and repository copy, and that a coordinator keeps the work organized. ZDNet said a user can enter an individual thread, redirect it while it runs, and return to the main project chat to monitor the broader project.
Claude Code Projects works by splitting a request into cloud threads. Each thread is a full Claude Code cloud session with its own branch and repo copy, while a coordinator routes work, lets the user steer named threads, and leaves overlapping code to normal pull request merge handling.
Anthropic described the coordinator to ZDNet this way: "Claude scopes the request, delegates the work, coordinates parallel threads, reviews the outputs, and assembles the finished result." ZDNet also observed that the feature does not appear to be fully autonomous, because threads appear to begin when a user hits the Start button for each thread Claude recommends. That detail matters for managers who expect agent orchestration to remove human sequencing decisions.
Where the limits show up
The main limits are cloud locality, memory opacity, usage ceilings, and normal Git conflicts. ZDNet said local workflows remain outside the new system for now, and Anthropic said, "Threads run in the cloud today; running on your machine alongside your local tools and code and behind your network is coming very soon." Anthropic has not provided a date for local tools, local code, or private network support in the supplied evidence.
Teams should treat parallel Claude Code threads as branch automation, not as architecture automation. The evidence shows the system can divide work and persist context, but overlapping files, shared abstractions, and duplicated infrastructure still require human review before pull requests land.
Usage is another hard limit because every thread is a full Claude Code session. ZDNet quoted Anthropic as saying, "Projects can run several threads at once, and each one is a full Claude Code session. Because of this, projects reach usage limits faster." ZDNet's David Gewirtz also said memory is not well documented in Anthropic's post, with no apparent way to inspect, correct, export, or know how long retained memory persists.
The practitioner signal points to the same merge risk, but it is thin. In a September 22, 2026 r/ClaudeAI discussion, one commenter said multiple agents on the same repository can "botch the overall architecture" and recreate functionality or infrastructure that should be reused. Another commenter said parallel agents had been their default for months using Fable, but the supplied Reddit thread contains only two top comments, so it shows current concerns rather than a measured adoption pattern.
What teams should check now
Teams should check branch boundaries, repository ownership, and CI before letting Claude Code Projects split work across several threads. The mechanism reported by The Verge and ZDNet means conflicts are handled like pull request conflicts, so the prevention point is the task brief and repo path assignment, not the coordinator.
- Check
CODEOWNERSor repository ownership rules before assigning threads to shared components. - Assign each thread to non-overlapping paths when possible, such as one template directory, one test suite, or one service package.
- Require CI status, unit tests, linting, and type checks before merging any thread output.
- Review pull requests for duplicated helpers, recreated infrastructure, and changes to shared abstractions before resolving conflicts.
Measure whether the feature saves engineering time by tracking merge conflict count per project run, review time per accepted pull request, and usage limit interruptions per project. If generation time falls but review time rises, the team has moved the bottleneck from coding to integration. That is still useful for some work, but it changes staffing and review expectations.
What it changes for search teams
For search and marketing engineering teams, the change mainly affects how fast repo-backed changes can be prepared, not how Google or AI answer engines rank pages. That is an inference from the supplied evidence, because Anthropic's change is a developer workflow change. It can help prepare isolated updates to schema templates, landing page components, analytics instrumentation, or internal content tooling when ownership boundaries are clean.
The risk for search teams is inconsistent code that changes crawlable output at template scale. If multiple threads alter structured data, canonical handling, analytics events, or page components in overlapping parts of a site, the merge conflict may be obvious but the rendered HTML regression may not be. Search teams using Claude Code Projects should verify rendered pages, structured data output, canonical tags, and tracking events after CI passes, because answer engines and search crawlers see the deployed output, not the agent plan.
The next event to watch is Anthropic's staged rollout beyond selected Pro and Max cloud users. The practical trigger is Projects appearing in the Claude Code sidebar or the Code tab of the Claude desktop app, followed by Anthropic shipping the promised local tools and local code support.