Experiments
Stop when this page is not the decision
A published page can record a stop. It does not, by itself, record the next plan.
claude.com published this account (2026-09-17): Anthropic put a rebuilt Projects experience into beta in Claude Code: a coordinator scopes a goal and repo, delegates parallel cloud threads that each run as a full Claude Code session on their own branch and repo copy, reviews outputs, and assembles the result. Initial access is limited to select Pro and Max subscribers using cloud sessions who do not already have web or desktop projects.
This guide uses that public page as the example. This site did not run the test, close the deal, or measure the product.
Write only what the page says
The page's claim is: Anthropic put a rebuilt Projects experience into beta in Claude Code: a coordinator scopes a goal and repo, delegates parallel cloud threads that each run as a full Claude Code session on their own branch and repo copy, reviews outputs, and assembles the result. Initial access is limited to select Pro and Max subscribers using cloud sessions who do not already have web or desktop projects.
Put the URL under that sentence. If a later recap adds a number or a date, keep the original page as the record.
A published page can record a stop. It does not, by itself, record the next plan.
Do the site's check on this one page. Fill a line only when the page supports it. Where the page is silent, write Not stated.
A finished note names the page, the date, and the limit of the claim. It does not borrow a result from a different story.
Stop at the untested line
Anything you did not open, install, or count stays untested. Leave that line visible.
Source page: Claude Code Projects redesigned around a coordinator directing parallel cloud threads.
Sources: Claude Code Projects redesigned around a coordinator directing parallel cloud threads