--- title: Claude Code Projects opens to Pro and Max users | daily.dev description: Claude Code Projects has rolled out to all Pro and Max subscribers who were on the waitlist, based on an announcement from the ClaudeDevs account. A project... canonical: https://daily.dev/posts/claude-code-projects-opens-to-pro-and-max-users-5r79iiexp twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Claude Code Projects opens to Pro and Max users | daily.dev og:description: Claude Code Projects has rolled out to all Pro and Max subscribers who were on the waitlist, based on an announcement from the ClaudeDevs account. A project... og:url: https://daily.dev/posts/claude-code-projects-opens-to-pro-and-max-users-5r79iiexp og:image: https://api.daily.dev/og/posts/5R79IIexP.png og:image:alt: Claude Code Projects opens to Pro and Max users og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Claude Code Projects opens to Pro and Max users **[Collections](https://daily.dev/sources/collections)** · 2 min read · 1 upvotes · 0 comments ## Summary Claude Code Projects has rolled out to all Pro and Max subscribers who were on the waitlist, based on an announcement from the ClaudeDevs account. A project groups a stream of related work that persists beyond a single session, letting users set instructions, repos, and memory once instead of repeating them each time. Claude runs each task as a parallel cloud thread, and an Overview pane reports which threads finished, which pull requests are ready, and which need input. Walkthrough and demo videos from community creators are also available for newcomers. ## Content Claude Code Projects is now available to every Pro and Max user who was on the waitlist, according to @ClaudeDevs. It launched in beta on Sept-17, but only a narrow group had access until now. @ClaudeDevs also posted a 4-minute walkthrough for people new to it. ## What a project is A project is meant for a stream of related work that outlasts a single session. @rohanpaul_ai says it replaces the old folder-style project with a coordinator. The coordinator scopes a goal, hands pieces to parallel threads, reviews what they produce and assembles the finished result. You set the instructions, repos and memory once instead of repeating them each session, as @addyosmani describes it. ## How the threads work Each thread is a full Claude Code cloud session on its own branch and its own copy of the repo. All threads read from and write to one shared project memory. So if a decision in one task changes, say a release date moves, later tasks pick it up without re-prompting. Collisions between threads show up as ordinary merge conflicts, not silent overwrites. That's a sensible choice, since you already know how to deal with merge conflicts. ## Handing off a batch @addyosmani's favorite part is that you can hand off a batch of tasks and walk away. When you come back, the Overview pane shows which threads finished, which PRs are ready and which need your answer. @addyosmani points to a video from @delba_oliveira for a closer look. @shadcn says most of their Claude Code work now happens in Projects. ## Questions this post answers ### What is Claude Code Projects and who can use it now? Claude Code Projects is a feature that groups a stream of related work into a persistent project, letting users set instructions, repositories, and memory once rather than repeating them per session. Claude runs each task as a parallel cloud thread and an Overview pane shows which threads finished, which pull requests are ready, and which need a response. It has opened to every Pro and Max subscriber who was on the waitlist. _Developers rolling out new Claude Code features can track announcements like this on daily.dev._ ## Community take How the wider developer community reacted, aggregated from 2 discussions and 77 comments across x (as of 2026-10-10). **TL;DR:** Early adopters, including at least one prominent shipping on it daily, are enthusiastic about Projects' persistent context and cross-repo coordination, but many commenters probe hard at merge-conflict handling, approval friction, and cloud-only/secrets limitations. **Sentiment:** 50% positive · 35% mixed · 15% skeptical **The case for** - Persistent project memory eliminates re-explaining repo conventions or schema every session. - Coordinating multiple repos (API, web, mobile) with a single coordinator clarifies merge order across PRs. - Scoping a read-only tests folder prevents agents from altering tests to force a pass. - Context written to a plain file is portable and can be picked up by other harnesses/tools. **The pushback** - Parallel threads editing the same file shift the bottleneck from writing code to merging it, and it's unclear how conflicts between semantically incompatible (not just textually conflicting) changes get resolved. - Requiring repeated manual approvals across chats undercuts the point of having a coordinator. - Cloud-only restriction makes Projects far less useful for non-cloud workflows like iOS development. - Context doesn't transfer when switching to other tools (e.g., cursor, codex), so it stays siloed. - Letting agents access tokens/secrets directly via .env is a trust and security concern. - One commenter dismissed Projects outright as useless compared to just using sub-agents. **By community** - x (mixed): A technical thread focuses skeptically on how the coordinator will actually resolve conflicting edits between parallel threads. - x (positive): A long reply thread under a heavy user's posts is largely enthusiastic about Projects as a default workflow, though interspersed with pointed questions about approvals, secrets management, cloud restrictions, and context portability. **Hottest debate:** Whether the coordinator can meaningfully resolve conflicts between parallel threads beyond simple file-level merge conflicts, versus just creating more merge overhead. **Open questions** - How does the coordinator handle two clean diffs that encode incompatible product decisions rather than simple file conflicts? - Can tokens/secrets be scoped per script or thread so agents don't need broad access? - Do projects maintain their own separate MCP connections, useful for isolating client work? - Is usage/cost the same when using Projects versus plain Claude Code? - What's the best practice for organizing projects — one per repo, one per feature, or one per client? **Highlights** > @rohanpaul_ai File conflicts are the easy case. What happens when two clean diffs encode incompatible product decisions? Does shared project memory help the coordinator catch that, or does a human still have to decide? > — [ham\_zax on x](https://x.com/ham_zax/status/2108851490274099290) > @kentcdodds Hmm not really. I always ask models to write context in a file that another harness can pick up. I use a lot of harnesses :) > — [shadcn on x · 10 points, 1 comments](https://x.com/shadcn/status/2108812258218594313) > @shadcn just sort of defeats the purpose of the coordinator for me if i have to keep typing "go" bouncing between chats > — [Zee on x · 1 comments](https://x.com/Zee/status/2108845948378259893) > @shadcn How have you worked around the Cloud only restriction? I am waiting for a power user to make a really really solid guide on setting up all the bells and whistles in Cloud. Until then Projects are super limited for me given I do predominantly iOS stuff atm. > — [JonahDevs on x · 1 points](https://x.com/JonahDevs/status/2108830903015559565) > @shadcn Claude projects are useless. Better off just asking Claude code to use sub agents. > — [fernandoeeu\_dev on x](https://x.com/fernandoeeu_dev/status/2108905132662350318) **Source threads** - [x](https://x.com/rohanpaul_ai/status/2108768446154760403) · 0 points · 4 comments - [x](https://x.com/shadcn/status/2108804948750393689) · 0 points · 73 comments --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#anthropic](https://daily.dev/tags/anthropic), [#claude-code](https://daily.dev/tags/claude-code) [View this post on daily.dev](https://daily.dev/posts/claude-code-projects-opens-to-pro-and-max-users-5r79iiexp) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Claude Code Projects opens to Pro and Max users","url":"https://daily.dev/posts/claude-code-projects-opens-to-pro-and-max-users-5r79iiexp","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/claude-code-projects-opens-to-pro-and-max-users-5r79iiexp"},"datePublished":"2026-10-09T18:23:15.386Z","dateModified":"2026-10-10T21:21:05.692Z","description":"Claude Code Projects has rolled out to all Pro and Max subscribers who were on the waitlist, based on an announcement from the ClaudeDevs account. A project...","isAccessibleForFree":true,"articleSection":"Collections","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Collections","logo":"https://media.daily.dev/image/upload/s--fk_6ycEi--/f_auto,q_auto/v1780996001/logos/collections?_a=BAMAMiWQ0","url":"https://daily.dev/sources/collections"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/claude-code-projects-opens-to-pro-and-max-users-5r79iiexp","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,anthropic,claude-code","timeRequired":"PT2M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collections","item":"https://daily.dev/sources/collections"},{"@type":"ListItem","position":3,"name":"Claude Code Projects opens to Pro and Max users"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/claude-code-projects-opens-to-pro-and-max-users-5r79iiexp#faq","mainEntity":[{"@type":"Question","name":"What is Claude Code Projects and who can use it now?","acceptedAnswer":{"@type":"Answer","text":"Claude Code Projects is a feature that groups a stream of related work into a persistent project, letting users set instructions, repositories, and memory once rather than repeating them per session. Claude runs each task as a parallel cloud thread and an Overview pane shows which threads finished, which pull requests are ready, and which need a response. It has opened to every Pro and Max subscriber who was on the waitlist. Developers rolling out new Claude Code features can track announcements like this on daily.dev."}}]} ```