Let Claude coordinate ongoing work with Projects changedclaude-projects
Nearest release: v2.1.283, published 8 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 26 Sep 2026 03:05 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 28 Sep 2026 23:37 UTC.
Upstream edited
Recorded here
Lines+44added
Lines−44removed
From line
189
where the diff opens
First seen
17 Sep 2026
this site's first read of the page
Recorded edits12to this page, all time
The whole hunk
from line 189, old and new numbered
/
from line 189
189189
190190The pane's **Threads** tab groups threads by state:
191191
192| Group | What's in it |
193| :------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
194| **Ready for review** | Threads whose pull request is open and awaiting review |
195| **Waiting on you** | Threads that need your reply or approval, or that failed |
196| **Working** | Threads still running |
197| **Landing** | Threads whose pull request is approved or queued to merge |
198| **Idle** | Threads that finished and aren't waiting on anything |
199| **Resolved** | Threads marked done: by you from the thread's menu, by Claude once you've taken the last step, such as merging its pull request, or automatically after a week with no activity. You can reopen one from the same menu |
192| Group | What's in it |
193| :- | :- |
194| **Ready for review** | Threads whose pull request is open and awaiting review |
195| **Waiting on you** | Threads that need your reply or approval, or that failed |
196| **Working** | Threads still running |
197| **Landing** | Threads whose pull request is approved or queued to merge |
198| **Idle** | Threads that finished and aren't waiting on anything |
199| **Resolved** | Threads marked done: by you from the thread's menu, by Claude once you've taken the last step, such as merging its pull request, or automatically after a week with no activity. You can reopen one from the same menu |
200200
201201The pane's other tabs are **Library** for the files and folders you added and the files threads produced, **Pull requests** once threads have opened any, and **Routines** for the [routines](/docs/en/routines) Claude set up from this project.
202202
from line 274
274274
275275Project memory, project instructions, and the project's repositories, files, and environment carry context across threads. You set each one once.
276276
277| Context | What it carries | How you set it |
278| :----------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
279| Project memory | Notes Claude keeps about the project, such as requirements, decisions, and pitfalls, stored as files. Every cloud thread reads the index file `MEMORY.md` when it starts and opens the other files when it needs them | Ask Claude in the project conversation or any cloud thread to remember a requirement, a decision, or a pitfall, or to forget one. Read, edit, and delete the files in **Project settings > Memory** |
280| Project instructions | Text sent to each new thread and to Claude in the project conversation, up to 16,000 characters. [Write project instructions](#write-project-instructions) covers what to put in it | **Project settings > Memory > Project instructions**, or ask Claude to change the instructions |
281| Repositories, files, and environment | The repositories every cloud thread clones, the folders and files it can read under `/mnt/project-files`, and the cloud environment it runs in | Repositories and environment in **Project settings > Environment**, or ask Claude in the conversation to add a repository to the project. Files and folders from **Add** on the **Library** tab in **Overview** |
277| Context | What it carries | How you set it |
278| :- | :- | :- |
279| Project memory | Notes Claude keeps about the project, such as requirements, decisions, and pitfalls, stored as files. Every cloud thread reads the index file `MEMORY.md` when it starts and opens the other files when it needs them | Ask Claude in the project conversation or any cloud thread to remember a requirement, a decision, or a pitfall, or to forget one. Read, edit, and delete the files in **Project settings > Memory** |
280| Project instructions | Text sent to each new thread and to Claude in the project conversation, up to 16,000 characters. [Write project instructions](#write-project-instructions) covers what to put in it | **Project settings > Memory > Project instructions**, or ask Claude to change the instructions |
281| Repositories, files, and environment | The repositories every cloud thread clones, the folders and files it can read under `/mnt/project-files`, and the cloud environment it runs in | Repositories and environment in **Project settings > Environment**, or ask Claude in the conversation to add a repository to the project. Files and folders from **Add** on the **Library** tab in **Overview** |
282282
283283**Project settings > Memory** lists these files under **Auto memory**, because Claude writes them itself as it works in the project. They're separate from the [auto memory](/docs/en/memory) Claude Code keeps on your machine, even though both use a `MEMORY.md` index. Project memory is also separate from the `CLAUDE.md` files in the project's repositories. Each cloud thread still reads those `CLAUDE.md` files from its clone when it starts, so put instructions about a repository in its `CLAUDE.md` and notes about the project in project memory.
284284
from line 322
322322
323323Each cloud thread clones every repository in the project and loads `CLAUDE.md` and skills from all of them. Permission rules, hooks, and `env` come only from the `.claude/settings.json` in the directory the thread starts in: inside the repository when the project has one, and above the clones when it has several, where no repository's file is read for them.
324324
325| In each repository | One repository | Several repositories |
326| :-------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------- |
327| `CLAUDE.md` | Loaded when the thread starts | Loaded from every repository when the thread starts |
328| Skills, agents, and commands under `.claude/` | Loaded | Loaded from every repository |
329| Plugins enabled in `.claude/settings.json` | Not loaded. Add the plugin in **Project settings > Plugins** instead | Not loaded. Add the plugin in **Project settings > Plugins** instead |
330| Permission rules, hooks, and `env` defined in `.claude/settings.json` | Apply to the thread, except the `env` keys that [no cloud session honors](/docs/en/cloud-environments#what-carries-over-from-your-setup) | Don't apply |
325| In each repository | One repository | Several repositories |
326| :- | :- | :- |
327| `CLAUDE.md` | Loaded when the thread starts | Loaded from every repository when the thread starts |
328| Skills, agents, and commands under `.claude/` | Loaded | Loaded from every repository |
329| Plugins enabled in `.claude/settings.json` | Not loaded. Add the plugin in **Project settings > Plugins** instead | Not loaded. Add the plugin in **Project settings > Plugins** instead |
330| Permission rules, hooks, and `env` defined in `.claude/settings.json` | Apply to the thread, except the `env` keys that [no cloud session honors](/docs/en/cloud-environments#what-carries-over-from-your-setup) | Don't apply |
331331
332332In a project with several repositories, each clone is attached to the thread as an [additional directory](/docs/en/memory#load-from-additional-directories) with `CLAUDE.md` loading turned on, which is why every repository's `CLAUDE.md` and skills load at start even though the thread starts above them. In such a project, put standing rules in project instructions and give threads environment variables through the [cloud environment](#choose-an-environment-for-threads).
333333
from line 354
354354
355355Settings save as you change them; a text field you're editing, such as the goal or instructions, shows **Save changes** and **Discard** until you leave it. Changes to instructions, repositories, plugins, and environment in **Project settings** reach new threads, not threads already running.
356356
357| Setting | Section | What it controls |
358| :--------------------------- | :---------- | :------------------------------------------------------------------------------------------------------------------ |
359| Name, icon, and goal | General | The project's name and icon in the sidebar, and its one-line goal |
360| Coordinator model and effort | General | The model and [effort level](/docs/en/model-config#adjust-effort-level) for Claude in the project conversation |
361| Thread model and effort | General | The model and effort level for threads |
362| Project instructions | Memory | [Standing rules](#give-a-project-standing-context) every new thread receives |
363| Project repositories | Environment | The repositories new cloud threads clone |
364| Cloud environment | Environment | The [cloud environment](#choose-an-environment-for-threads) new cloud threads run in |
365| Connectors | Environment | A link to manage the claude.ai connectors cloud threads get |
366| Plugins | Plugins | The plugins that load into each new cloud thread |
367| Usage | Usage | [Token use](#usage-and-cost) by thread and by model |
368| Memory | Memory | The project's [memory files](#give-a-project-standing-context) |
369| Restart Claude | General | Restarts the project conversation when [Claude stops responding there](#claude-hasnt-responded) |
370| Pause, Archive, Delete | General | Stops, hides, or removes the project; see [Pause, archive, or delete a project](#pause-archive-or-delete-a-project) |
357| Setting | Section | What it controls |
358| :- | :- | :- |
359| Name, icon, and goal | General | The project's name and icon in the sidebar, and its one-line goal |
360| Coordinator model and effort | General | The model and [effort level](/docs/en/model-config#adjust-effort-level) for Claude in the project conversation |
361| Thread model and effort | General | The model and effort level for threads |
362| Project instructions | Memory | [Standing rules](#give-a-project-standing-context) every new thread receives |
363| Project repositories | Environment | The repositories new cloud threads clone |
364| Cloud environment | Environment | The [cloud environment](#choose-an-environment-for-threads) new cloud threads run in |
365| Connectors | Environment | A link to manage the claude.ai connectors cloud threads get |
366| Plugins | Plugins | The plugins that load into each new cloud thread |
367| Usage | Usage | [Token use](#usage-and-cost) by thread and by model |
368| Memory | Memory | The project's [memory files](#give-a-project-standing-context) |
369| Restart Claude | General | Restarts the project conversation when [Claude stops responding there](#claude-hasnt-responded) |
370| Pause, Archive, Delete | General | Stops, hides, or removes the project; see [Pause, archive, or delete a project](#pause-archive-or-delete-a-project) |
371371
372372### Pause, archive, or delete a project
373373
from line 485
485485
486486These messages name their own cause. The table gives the next step for each.
487487
488| Message | What to do |
489| :--------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
490| "Unable to connect to repository" with "Claude couldn't reach GitHub to fetch your repository" | Wait a moment, then send another message to retry |
491| "Unable to connect to repository" with "Claude couldn't access your repository or environment" | Your GitHub account needs push access to the repository, and the environment must still exist. Check both in **Project settings > Environment**, then retry |
492| "Couldn't show the setup proposal" | The app you have open is older than the **Setup recommendations** Claude sent. Refresh the page or restart the desktop app, or ask Claude to propose the setup again |
493| "The project's environment was removed" | Choose a different environment in **Project settings > Environment**; the change applies to new threads |
494| "Setup script failed" | Click **Edit setup script** on the error, fix the script in the environment, then send another message. [Setup script failed](/docs/en/web-quickstart#setup-script-failed) lists common causes |
495| "Claude ran out of context on this turn" | The thread filled its context window. If the message says the thread continues in a fresh session, it carries on by itself; otherwise ask Claude in the project conversation to start a new thread for the remaining work |
496| "Couldn't start in" followed by your folder's name | You allowed a thread to run on your computer, but the session couldn't start there. When a line under the message gives the reason, fix that, then ask Claude to run the task again |
497| "Claude is out of date on your device" | The computer you picked to run a thread has a Claude Code version older than v2.1.280. Update Claude Code there, or update the desktop app if that's what connects the folder, then ask Claude to run the task again |
498| "Reached the turn limit" | The thread reached the cap on agentic turns that [`CLAUDE_CODE_MAX_TURNS`](/docs/en/env-vars) sets. Send another message to continue, or raise or remove that variable where it's set |
488| Message | What to do |
489| :- | :- |
490| "Unable to connect to repository" with "Claude couldn't reach GitHub to fetch your repository" | Wait a moment, then send another message to retry |
491| "Unable to connect to repository" with "Claude couldn't access your repository or environment" | Your GitHub account needs push access to the repository, and the environment must still exist. Check both in **Project settings > Environment**, then retry |
492| "Couldn't show the setup proposal" | The app you have open is older than the **Setup recommendations** Claude sent. Refresh the page or restart the desktop app, or ask Claude to propose the setup again |
493| "The project's environment was removed" | Choose a different environment in **Project settings > Environment**; the change applies to new threads |
494| "Setup script failed" | Click **Edit setup script** on the error, fix the script in the environment, then send another message. [Setup script failed](/docs/en/web-quickstart#setup-script-failed) lists common causes |
495| "Claude ran out of context on this turn" | The thread filled its context window. If the message says the thread continues in a fresh session, it carries on by itself; otherwise ask Claude in the project conversation to start a new thread for the remaining work |
496| "Couldn't start in" followed by your folder's name | You allowed a thread to run on your computer, but the session couldn't start there. When a line under the message gives the reason, fix that, then ask Claude to run the task again |
497| "Claude is out of date on your device" | The computer you picked to run a thread has a Claude Code version older than v2.1.280. Update Claude Code there, or update the desktop app if that's what connects the folder, then ask Claude to run the task again |
498| "Reached the turn limit" | The thread reached the cap on agentic turns that [`CLAUDE_CODE_MAX_TURNS`](/docs/en/env-vars) sets. Send another message to continue, or raise or remove that variable where it's set |
499499
500500## Related resources
501501
No line in this hunk matches that.