Claude Code Projects is reaching more paying users. Anthropic said on 9 October that it had admitted every Pro and Max subscriber then on the waitlist. The attraction is work that keeps moving after you close your laptop. The catch is that several tasks draw from the same usage allowance.
Based on 6 reviewed sources · See sources
The waitlist moved; the beta remains staged
The announcement is an access expansion, not a promise that every subscriber can start immediately. Its follow-up says new applicants still join the waitlist and enter as capacity allows. The walkthrough below introduces the redesigned experience.
Anthropic says every Pro and Max user then on the Claude Code Projects waitlist has been admitted; later applicants remain subject to capacity.
View the original post on X ↗Anthropic’s help page distinguishes this beta from existing chat and Cowork Projects. Those existing spaces continue to work. The new experience currently rolls out through Claude Code for Pro and Max users; Team and Enterprise support is planned.
One conversation, several pieces of work
The Projects documentation describes a persistent conversation that delegates tasks to separate Claude Code sessions, called threads. They share project context, while the coordinator tracks progress. Cloud threads keep running when your laptop closes. A local thread connected through Remote Control still needs that computer awake.
For someone building a website, that distinction matters: background changes can run in the cloud, while a test that needs their own machine cannot. Parallel work also consumes the plan allowance faster.
What to check before starting
Documented beta boundaries, checked 11 October 2026
| Question | Current position |
|---|---|
| Who can enter? | Pro and Max, in stages; new applicants still wait. |
| Can I close my laptop? | Cloud threads continue; local threads need the machine awake. |
| Does it get a separate allowance? | No. Conversation and running threads use the same plan limits. |
| How much work can it start? | 200 new threads per day across projects. A requested concurrency limit is not a hard cap. |
More autonomy, with a usage trade-off
On 10 October, Helsinki-based Agion co-founder Mikko Alasaarela reported more autonomous development alongside rapid use of his Max 200 allowance. He attributed his near full-day autonomy to Projects combined with his own harness—the surrounding software that manages an agent’s work.
Another user, @Divine_machine, described weeks of successful cloud work with local threads for live testing. Neither report supplies comparable workloads, token logs or outputs. They show different experiences, not a measured cost or quality result.
Sources
- Pro and Max waitlist access expansion
ClaudeDevs on X · Announcement ·
- Staged beta availability clarification
ClaudeDevs on X · Announcement ·
- Let Claude coordinate ongoing work with Projects
Claude Code Docs · Documentation
- What are projects?
Claude Help Center · Documentation
- Firsthand report on autonomy and Max-plan usage
Mikko Alasaarela on X · Research ·
- Firsthand reply on cloud work and local testing
Divine 〽️achine on X · Research ·
Written with AI assistance from the sources above. Analysis and practical implications are our interpretation. Our editorial approach.
