What ClaudeDevs announced
ClaudeDevs posted on 9 October 2026 that every Pro and Max user already on the Claude Code Projects waitlist had just been let in. The account called a project an ongoing conversation in which Claude coordinates the work and runs each task as its own thread in parallel. ClaudeDevs said Projects are in beta and that more Pro and Max users will be let in as capacity allows.
The docs describe the same arrangement: one conversation, a thread for each task, usually a cloud session, with threads running in parallel. You can check on them and steer them from your phone. Cloud threads keep going after you close your laptop. A thread on your computer runs only while that computer is awake. The docs point to work that fits this shape, such as bugs, stack traces, and review requests for one service, pasted in as they arrive, or one change across repositories, such as bringing every service up to a new lint config, with a thread for each repository. The docs call Projects a public beta on Pro and Max, rolling out gradually, starting with accounts that have used cloud sessions and do not already have projects in claude.ai chat or Cowork. The waitlist page still says Projects are rolling out in stages and asks people to join for earlier access.
Who can open it
Team and Enterprise plans do not have Projects yet. If Projects is missing from the sidebar at claude.ai/code, or from the Code tab of the desktop app, the docs say the rollout has not reached that account.
During the beta a project belongs to one user. You cannot share a project or its threads, and there are no organization-level controls. Projects are available at claude.ai/code, in the desktop app, and in the Claude mobile apps for iOS and Android. They are absent from the terminal CLI, the VS Code extension, the JetBrains plugin, Amazon Bedrock, Google Cloud's Agent Platform, and Microsoft Foundry.
Project code work needs a repository on github.com, push access from the connected GitHub account, and the Claude GitHub App. A repository on GitHub Enterprise Server, GitLab, or Bitbucket does not qualify. The docs say a token from /web-setup lets other cloud sessions reach a repository and is not enough for a project's cloud threads.
What a first project spends
On your first project, Claude takes a turn of its own as soon as the project is created, unless you send a message first. That turn uses your plan. A new project runs Opus everywhere. Effort is the model effort setting: threads start at high effort, which draws on your plan fastest, and the coordinating conversation starts at low effort. Thread model and effort can be changed in Project settings > General.
Project usage counts against the same plan limits as other Claude Code sessions and uses those limits faster. On Pro, the docs say to expect the limit sooner on days a project runs. A thread count you tell Claude in the project is a preference about how many threads to start. It leaves the plan limit unchanged. The enforced cap is 200 new threads per day across your projects. Work goes past plan limits only if you have turned on usage credits. A thread cannot turn them on. When a thread or the project conversation hits the plan's five-hour or weekly limit, it keeps retrying and continues when the limit resets. A routine is scheduled work in the project. A thread that a routine started stops with a limit error instead of waiting. An idle project with no running threads, no watched pull requests, and no new messages does not use the plan, and neither does an archived project. A watched pull request can wake a thread and spend usage again.
What the pages leave open
The batch admission is ClaudeDevs' announcement. The Projects doc and the waitlist form do not state that every waitlisted Pro and Max account was admitted on 9 October. They give no general-availability date and no capacity figure.
The waitlist form calls Projects new in Claude Code and an upgrade for the projects you already have in chat and Cowork. The docs say those earlier projects group conversations and reference files without threads or a coordinator, and keep working as they do today until the redesigned experience reaches them. ClaudeDevs names a four-minute walkthrough and does not include its steps. The post and these pages list no separate price for Projects and no usage-credit price.
Source
Also from
Sources and editorial approach
Sources checked on 9 October 2026: the ClaudeDevs post, the Claude Projects documentation, the Projects waitlist page, and the Claude Code changelog. The post is the admission announcement. Plan, usage, and setup rules come from the Projects documentation, and the waitlist page is the signup copy. The changelog has no note of this admission. The four-minute walkthrough named in the post was not reviewed. This is a reading of those pages, not a hands-on trial of Projects.