# Claude Code Projects: Parallel Agents, One Goal > Source: > Published: 2026-09-22 11:18:09+00:00 Claude Code Projects used to be a folder with a memory problem. You added CLAUDE.md files, pasted in reference documents, and crossed your fingers that Claude would synthesize them correctly at the start of each session. You still managed the handoffs. You still decided what to run next. Anthropic just changed that. As of September 17, 2026, Claude Code Projects is in beta as a **parallel agent coordinator**. You describe a goal once. Claude scopes the work, spins up parallel cloud sessions called threads, and runs them while you do something else — including closing your laptop. That is a real architectural shift, and it carries implications for your plan costs that are easy to miss. ## What a Thread Actually Is A thread is a full Claude Code cloud session running on Anthropic’s infrastructure, not on your machine. Each thread clones your repository into its own cloud sandbox and works on its own branch. Threads can open pull requests, run tests, and report back to the coordinator conversation. If two threads modify the same file, you get a merge conflict handled exactly like any other PR — no special magic, just standard git. The persistence angle matters. Close your browser, close your laptop, switch to your phone. The threads keep running. When they finish, the results show up in your project conversation. If you have work that takes hours — a large refactor, a generated test suite, a documentation sweep — you no longer need to keep a terminal open for it. ## The Coordinator in Action Here is what the workflow looks like in practice. Say you tell Claude: “Add dark mode support to the component library and update all consumers.” Under the old Projects, you would have opened three sessions yourself, kept notes on what each one was doing, and manually reconciled the branches at the end. Under the new Projects, Claude scopes that request into three threads: one for the design token system, one for the consumer components, one for Storybook documentation. Each thread opens its own PR. The coordinator reviews the outputs, flags any conflicts, and surfaces a summary. You review and merge. The cognitive overhead of orchestration moves from you to Claude. Projects also now maintains a **shared memory** that all threads draw from. CLAUDE.md files, AGENTS.md files, and auto-generated memory notes are available across threads. A new **library** collects reference files you add and artifacts Claude produces — design diagrams, logs, implementation plans. Every thread starts with the same baseline context. ## The Plan Limits Gotcha Anthropic puts this directly in the [cost documentation](https://code.claude.com/docs/en/costs): “A project uses plan limits faster than a single session, because every running thread is a full session.” That sentence needs to be read carefully before you kick off your first multi-thread project. If you are on Pro ($20/month), running four parallel threads consumes roughly four times the session bandwidth. The five-hour rolling limit resets on its own schedule. Max 5x ($100/month) and Max 20x ($200/month) subscribers have proportionally more headroom, and Projects is genuinely suited to those tiers. Pro users can still use Projects, but burning through a session window on a single parallel build is a real risk if you are not paying attention. Usage credits let you continue at standard API rates past your plan limit, capped at $2,000 per day. That is a meaningful safety valve, but it also means an unchecked project can generate unexpected costs. Start with two threads, understand the consumption rate, then expand. ## Who Has Access Right Now Beta access as of September 17 is limited to **Pro and Max subscribers who use cloud sessions in Claude Code and have no existing projects on web or desktop**. That last clause trips people up — if you already have Projects on claude.ai or the desktop app, you are in the waitlist group, not the initial wave. Anthropic says access will expand to more Claude Code users on Pro and Max plans over the coming weeks, with Team and Enterprise plans following after the beta matures. [The official announcement](https://claude.com/blog/projects-redesigned) has current eligibility details and the waitlist link. The [Projects documentation](https://code.claude.com/docs/en/claude-projects) is worth reading before your first multi-thread build — especially the section on how the coordinator decides what becomes a thread versus what it handles inline.