Let Claude coordinate ongoing work with Projects changedclaude-projects
Nearest release: v2.1.300, published 4 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 14 Oct 2026 19:13 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 14 Oct 2026 19:37 UTC.
Upstream edited
Recorded here
Lines+1added
Lines−2removed
From line
360
where the diff opens
First seen
17 Sep 2026
this site's first read of the page
Recorded edits22to this page, all time
The whole hunk
from line 360, old and new numbered
/
from line 360
360360
361361* Skills, subagents, and commands: commit them to a repository you added to the project, for example a skill at `.claude/skills/<skill-name>/SKILL.md`. Each cloud thread clones every repository in the project and loads `.claude/skills/`, `.claude/agents/`, and `.claude/commands/` from each of them, so a skill committed to one repository is available in every cloud thread. Cloud threads also load the [skills you enable for your claude.ai account](/docs/en/skills#skills-in-cowork-and-cloud-sessions).
362362* Plugins: add them in **Project settings > Plugins**; they load into each new cloud thread. Plugins that a repository declares in its `.claude/settings.json` [don't load in cloud threads](/docs/en/cloud-environments#what-carries-over-from-your-setup).
363* MCP servers: cloud threads get their MCP tools from the connectors on your claude.ai account, which are MCP servers you connect once at [claude.ai/customize/connectors](https://claude.ai/customize/connectors) or through the **Manage connectors** link in **Project settings > Environment**. Every cloud thread can use all of them with no per-project setup. The project conversation itself has no connectors, so send work that needs one as a task for a cloud thread. In a project with one repository, cloud threads also load MCP servers from that repository's [`.mcp.json`](/docs/en/cloud-environments#what-carries-over-from-your-setup). [How connectors reach Claude Code](/docs/en/mcp#how-connectors-reach-claude-code) lists the rules for cloud sessions and the settings that turn connectors off.
363* MCP servers: cloud threads get their MCP tools from the connectors on your claude.ai account, which are MCP servers you connect once at [claude.ai/customize/connectors](https://claude.ai/customize/connectors). Every cloud thread can use all of them with no per-project setup. The project conversation itself has no connectors, so send work that needs one as a task for a cloud thread. In a project with one repository, cloud threads also load MCP servers from that repository's [`.mcp.json`](/docs/en/cloud-environments#what-carries-over-from-your-setup). [How connectors reach Claude Code](/docs/en/mcp#how-connectors-reach-claude-code) lists the rules for cloud sessions and the settings that turn connectors off.
364364* Command-line tools and packages: install them in the environment's [setup script](/docs/en/cloud-environments#setup-scripts).
365365
366366To see which connectors a running cloud thread has at claude.ai/code, open the thread and select **Connectors** from the **+** menu beside its message box. Turning a connector off there removes it from that thread and saves that as your account default, so new threads and claude.ai chats start without it until you turn it back on. A cloud thread picks up a connector you add or reconnect after the next message you send it.
from line 379
379379| Project instructions | Memory | [Standing rules](#give-a-project-standing-context) every new thread receives |
380380| Project repositories | Environment | The repositories new cloud threads clone |
381381| Cloud environment | Environment | The [cloud environment](#choose-an-environment-for-threads) new cloud threads run in |
382| Connectors | Environment | A link to manage the claude.ai connectors cloud threads get |
383382| Plugins | Plugins | The plugins that load into each new cloud thread |
384383| Usage | Usage | [Token use](#usage-and-cost) by thread and by model |
385384| Memory | Memory | The project's [memory files](#give-a-project-standing-context) |
No line in this hunk matches that.