过去，在一次构建中管理多个会话，需要你拆分工作、来回协调交接，再把结果拼接回去。如今在 Claude Code 项目中，你只需描述需要完成什么，Claude 就会管理这些工作。
Claude 会界定请求范围、分派工作、协调并行线程、审查输出，并汇总出最终结果。你可以在整个过程中随时引导进度，甚至可以用手机操作，而且在你离开电脑后它仍会继续工作。
例如，配置一个项目并设定目标：降低你应用结账流程的 p75 延迟。然后让 Claude 分析各个端点的性能、测试优化方案，并在并行线程中提交 PR。或者，连接你的 API、Web 和移动端仓库，设定目标：淘汰已弃用的 v1 端点。Claude 会为每个仓库创建一个线程，迁移调用方、运行测试、提交 PR，然后告诉你哪些需要先合并。
从今天起，更新版项目将以 beta 形式提供给部分 Claude Pro 和 Max 订阅用户，这些用户需在 Claude Code 中使用云会话，且目前在网页端或桌面端没有任何现有项目。
在接下来的一周内，我们将向这些套餐中的更多 Claude Code 用户扩大访问权限。之后，更新版项目将覆盖所有 Claude 以及 Team 和 Enterprise 套餐。如果你是 Pro 或 Max 用户但尚未获得访问权限，可以加入等待名单。
Pro 和 Max 套餐中的现有项目将照常运行。随着推广范围扩大到聊天和 Cowork，我们将对它们进行升级。
线程负责干活，Claude 负责指挥
项目中的各个线程负责干活，由一个协调者来指挥它们。
当你启动一个项目时，你需要选择一个目标以及仓库或上下文。Claude 会首先建议它可以立即接手的工作。你可以配置项目的云环境、连接器、插件、指令和模型。
你可以在项目主聊天中监控和引导进度，也可以深入每个单独的线程去查看和把控细节。像给幕僚长做简报那样在项目中向 Claude 交代任务，它会把工作分配到新的或已有的线程中。
Claude 还会主动跟进并落实工作。连接仓库后，线程会发起 pull request 并运行你的测试；连接文档后，它会阅读文档并起草内容。
在底层，每个线程都是一个 Claude Code 云会话，在各自的分支和仓库副本上工作。协调者负责保持工作有序，但如果任何线程修改了相同的代码，重叠部分会像其他 PR 一样以合并冲突的方式解决。
每个线程还可以在需要时通过子智能体、循环和工作流进一步拆分所委派的工作，从而让大型任务更快完成。
上下文随时间不断积累
项目是为长时间运行或智能体式工作流而设计的：即那些耗时超过一次回复、且包含多个部分的工作。
随着时间推移，Claude 会了解更多项目细节，并将其应用到工作中。现在，每个线程都会为共享记忆添砖加瓦，并从中汲取信息，从而减少了对复杂提示词工程的依赖。
例如，Claude 可以记住发布推迟到了周五、导出功能为何被移除，或者在改动计费服务之前应该先找谁确认。
Claude 还会记住你的工作和沟通风格。你可以让它调整汇报的频率、开启新线程的频率，或者每次更新的详细程度。
除了记忆之外，项目现在还包含一个库，用于收集你添加的文件以及 Claude 产出的工件。这样可以更轻松地找到相关材料，也让新工作能够建立在过往成果之上。
接下来
项目可以同时运行多个线程，每个线程都是一个完整的 Claude Code 会话。因此，项目可能会更快触及用量上限。你可以查看项目专属用量，并为协调对话以及工作线程选择所使用的模型和投入级别。
线程目前在云端运行；很快就能在你的机器上运行，与你的本地工具和代码并行，并在你的网络环境之内。
开始使用项目。
Managing multiple sessions across a build used to require you to divide the work, juggle handoffs, and stitch the results back together. Now in a Claude Code project, you describe what needs to get done and Claude manages the work.
Claude scopes the request, delegates the work, coordinates parallel threads, reviews the outputs, and assembles the finished result. You can steer progress throughout, even from your phone, and it keeps working after you step away from your computer.
For example, configure a project and set a goal to reduce your app's checkout p75 latency. Then ask Claude to profile each endpoint, test optimizations, and open PRs in parallel threads. Or connect your API, web, and mobile repos and set a goal to retire a deprecated v1 endpoint. Claude creates a thread per repo to migrate the callers, run the tests, open PRs, and then tells you which ones need to merge first.
Starting today, updated projects are available in beta to select Claude Pro and Max subscribers who use cloud sessions in Claude Code and don’t have any existing projects on the web or desktop.
Over the coming week, we'll expand access to more Claude Code users on those plans. Updated projects across all of Claude and Team and Enterprise plans come after that. If you're on Pro or Max and don't have access yet, you can join the waitlist.
Existing projects on Pro and Max plans keep working as they do today. We'll upgrade them as the rollout expands to chat and Cowork.
Threads do the work, Claude directs it
Projects have threads that do the work and a coordinator that directs them.
When you start a project, you select a goal as well as the repo or context. Claude starts by suggesting work it can pick up right away. You can configure the project’s cloud environment, connectors, plugins, instructions, and model.
You can monitor and guide progress in the main project chat, or dive into each individual thread to examine and steer the details. Brief Claude in the project the way you'd brief a chief of staff and it routes work to new or pre-existing threads.
Claude also checks in and follows through on work. With repositories connected, a thread opens pull requests and runs your tests; with documents, it reads them and drafts.
Under the hood, each thread is a Claude Code cloud session working on its own branch and copy of the repo. The coordinator keeps work organized, but if any threads work on the same code, the overlap is resolved as a merge conflict just like any other PR.
Each thread can further split its delegated work into pieces using subagents, loops, and workflows when needed so large assignments finish faster.
Context builds over time
Projects are designed for long-running or agentic workflows: work that takes longer than one reply and has more than one part.
Over time, Claude learns more about the project details and applies them to its work. Every thread now adds to and draws from a shared memory, reducing the need for complex prompt engineering.
For example, Claude can remember the release moved to Friday, why the export was dropped, or who to check in with before touching the billing service.
Claude also remembers your working and communication style. You can ask it to adjust how often it checks in, how frequently it starts new threads, or how detailed to make each update.
Alongside memory, projects now include a library that collects the files you add and the artifacts produced by Claude. This makes it easier to find relevant materials and for new work to build on past efforts.
What's next
Projects can run several threads at once, and each one is a full Claude Code session. Because of this, projects can reach usage limits faster. You can check project specific usage and select the model and effort levels used by the coordinator chat as well as the worker threads.
Threads run in the cloud today; running on your machine alongside your local tools and code and behind your network is coming very soon.
Start using projects.