Claude Code 推出 Projects 功能，支持多任务并行协调

Give Claude a body of related work in one conversation and let it coordinate parallel cloud sessions that share repositories, instructions, and memory. Projects are in public beta on Pro and Max plans and rolling out gradually, starting with accounts that have used cloud sessions and don't have existing projects in claude.ai chat or Cowork. They aren't available on Team or Enterprise plans yet. If Projects doesn't appear in the sidebar at claude.ai/code or in the Code tab of the desktop app, the rollout hasn't reached your account, and you can join the waitlist. Run agents in parallel lists what you can use in the meantime. A project is one ongoing conversation where Claude coordinates a stream of related work for you. You tell it what needs doing and it starts a thread for each task. Each thread is a cloud session: Claude Code running in the cloud rather than on your machine. Threads run in parallel and keep going after you close the laptop. Without a project, running several sessions means doing the coordinating yourself: you decide what each one works on, repeat the same background at the start of each, and check back to see which finished or needs an answer. With a project, you instead: * Send work to one place: paste a bug report, a stack trace, or a list of tasks into the conversation whenever one comes up. Claude starts a thread for each piece of work or passes it to the thread already working in that area, and answers quick questions in place. * Set context once: every new thread starts with the project's repositories, instructions, and memory, so a rule you state once, such as which branch to target, reaches all of them. * Walk away and come back to finished work: when you come back an hour later or the next morning, the Overview pane shows which threads finished, which pull requests are ready for review, and which thread is waiting for your answer. If you already know the work you want a project to run, go straight to Create a project. Projects in claude.ai chat and Cowork, which group conversations and reference files, are a separate feature from the projects on this page. ## When to use a project A project is worth creating when the work has a goal that outlasts one session and keeps producing tasks. These kinds of work suit a project well: * One goal across many repositories: "Bring every service up to the new lint config." Claude can run a thread per repository, each with its own pull request, and the Overview pane shows which ones are ready for review. * An area you keep feeding: the bugs, stack traces, and review requests for one service, pasted into the conversation as they reach you. A pitfall you tell Claude to remember after one fix is in project memory for the next. * A build or migration bigger than a session: "Build what `docs/spec.md` describes" or "Move the app off the deprecated ORM." The work splits into threads that each take a part, decisions you ask Claude to remember early on reach the later threads, and the spec changes and bugs you find during the build go into the same conversation. * Work that isn't code: a folder of contracts or a support-ticket export you keep coming back to with new questions, such as "find the ten most common integration mistakes in these tickets." Upload the documents instead of adding a repository, and threads deliver each write-up as a file on the project's Library tab. In any of them you can send a batch of tasks, tell Claude to start without asking you to confirm, walk away, and find the threads that need you under Waiting on you when you're back, or ask Claude to put part of the work on a schedule as a routine. If one of these is your situation, create a project. ### When something else fits better Threads work on GitHub repositories and on the files, folders, and Google Drive folders you upload to the project, not on files or tools that exist only on your machine. Something else fits better in these cases: * One task that fits in a session: "Fix the flaky login test." Start a cloud session yourself. * Work that needs tools or services only your machine can reach: a local database, a device emulator, an API behind your VPN. Use a local session, or agent view to run several at once. If the work only needs local files, upload them to the project instead. * One task that repeats on a schedule with no conversation around it: "Post a dependency report every Monday." Create a routine on its own. * Several people giving Claude work and steering it together in a Slack channel: see Claude Tag. A project draws on the same plan limits as your other Claude Code sessions and uses them faster. Usage and cost covers what draws on your plan and how to keep it down. ## How a project is organized A project is one coordinating conversation with Claude plus the threads it starts to do the work. These are its parts: * The project conversation: one long-running session where Claude acts as coordinator. It takes what you send, decides what becomes a thread, and keeps track of every thread it started. It sees what threads report back, not every step they take. * Threads: the workers. Each is a separate cloud session with its own context window that does one piece of work on its own branch, opens a pull request when the work calls for one, and reports back to the conversation when it finishes. * What every thread starts with: * The project's repositories and files, plus its instructions and memory * The `CLAUDE.md`, skills, and plugins in each of the project's repositories, and in a project with one repository, that repository's permission rules and hooks too * The connectors on your claude.ai account * A cloud environment that sets its network access, environment variables, API credentials, and installed tools * The Overview pane: where you see all the threads at once and which of them need you. Its other tabs are Library for the files you added and the files threads produced, Pull requests for the ones threads opened, and Routines for scheduled work in the project. Threads don't pick up anything from the Claude Code setup on your own machine. Get skills, plugins, connectors, and tools into threads covers how to give them what they'd otherwise be missing. Here is how those parts connect, from you through the conversation to the threads doing the work, with Overview tracking their state: ## Create a project You create and use projects at claude.ai/code or in the Code tab of the desktop app. There are two ways to start one: * From scratch, when you know the stream of work you want Claude to run: open the New project dialog and name it. Start a new project from scratch walks through the dialog. * From a cloud session that's already doing the work: choose Continue as a project from that session's menu, and Claude proposes the project's setup from what the session was doing. See Start from an existing cloud session. Either way, check the prerequisites first. ### Check the prerequisites Before you create a project, check your plan, your GitHub setup, and what the work needs to reach: * Plan: you're on Pro or Max and Projects shows in your sidebar. * GitHub, if the project will work on code: your code is on github.com rather than GitHub Enterprise Server, GitLab, or Bitbucket, your connected GitHub account has push access to it, and the Claude GitHub App is installed on it. If you connected GitHub with `/web-setup`, that token lets your other cloud sessions reach a repository but isn't enough for project threads, which need the Claude GitHub App. Set up GitHub access has the steps. * Network, credentials, and tools: these come from the project's cloud environment. The default environment already reaches common package registries, so check this only if the work needs other domains, a secret, or a tool that isn't preinstalled. If the work needs an MCP server, check that it shows as connected in