Anthropic pone un jefe multiagente en la nube: Claude Code Projects vuelve (Pro/Max)

On September 17, 2026, Anthropic relaunched Projects inside Claude Code: a multi-agent cloud coordinator that splits work across parallel threads — each a cloud Claude Code session on its own branch/copy of the repo — with shared memory, goals and a file/artifact library. Beta today for select Pro/Max subscribers.

If your team (or ecommerce shop with a technical backlog) already “parallelizes” by opening several Claude windows by hand, this is the orchestration step: a boss that assigns, watches and resolves overlaps like merge conflicts/PRs.

How the coordinator works (no magic)

Per The Verge and The New Stack, each thread is a Claude Code cloud session on its own branch. The coordinator keeps work organized; if threads touch the same code, overlap is resolved as a merge conflict / PR — the language your team already uses.

Each thread can spawn subagents, loops and workflows so large assignments finish faster. You can talk to a thread or monitor/update from the main project chat. At launch threads run in the cloud; local support is “coming very soon,” Anthropic says.

Who gets it today (and who next)

Beta for select Claude Pro and Max; later expanding to all Pro, Max, Team and Enterprise, plus Cowork and Claude chats. For product/ecommerce teams living in daily PRs, the useful angle is less “solo copilot” and more a coordinated crew with shared memory and artifacts.

Checklist if you orchestrate multiple coding agents

1. Define Project goals and shared files before spawning threads.
2. Assign branches per thread; treat merge conflicts as part of the design.
3. Keep a human on the coordinator chat: priorities and kill-switch.
4. If you are on Pro/Max, request beta access; if not, document the manual parallel flow you want to replace.

If your ecommerce needs automation, funnels and a digital stack that can handle agents without chaos, Presticorp can land it. See presticorp.com/landingpages/ecommerce.

Writer’s take

Treat Projects as a cloud crew boss, not another chat. The value is not “more tokens” — it is shared memory + branched threads + conflicts resolved as PRs. If your process cannot survive two agents touching the same module, fix that before you ask for beta.

Sources

• The Verge — Claude Code Projects relaunch
• The New Stack — Claude Code parallel Projects