One read of Claude Documentationclaude-docs-20261110T223705Z
7 pages moved out of 289 read.
Pages moved
7
significant first
Pages read
289
in this capture
Captured
22:37 UTC
Corpus hash
2d889120dfe1
corpus-hash
What this read moved
1-7 of 7government/org-admin/analytics-api Changed · +14 / -5 lines
from line 27
2727Send your admin API key in the `x-api-key` header. Every request also needs the `anthropic-beta` header while the API is in beta. This request returns token usage for each model:
2828
2929```http theme={null}
30GET https://<claude-for-government-host>/gateway-api/v1/organizations/analytics/usage?starting_at=<start-time>&ending_at=<end-time>&group_by[]=model
30GET https://<claude-for-government-host>/gateway-api/v1/organizations/analytics/usage?starting_at=2026-10-31T00:00:00Z&ending_at=2026-11-07T00:00:00Z&group_by[]=model
3131x-api-key: <your-admin-api-key>
3232anthropic-beta: analytics-usage-cost-2026-08-24
3333```
from line 61
6161
6262## Read the response
6363
64Each row in `data` covers one period and one combination of the fields you group by. A day, hour, member, product, or model with no usage has no row. Count a missing row as zero if its period ends at or before `data_refreshed_at`. This is a response to the [example request](#send-a-request-to-the-analytics-api) for one week, shortened to one row and three of the `group` fields:
64Each row in `data` covers one period and one combination of the fields you group by. A day, hour, member, product, or model with no usage has no row. Count a missing row as zero if its period ends at or before `data_refreshed_at`. This is a response to the [example request](#send-a-request-to-the-analytics-api), shortened to one row and three of the `group` fields:
6565
6666```json theme={null}
6767{
from line 132
132132| `group` | What the row is split by. A field is `null` if you don't group by it, or if the usage has no value for it. The fields in `group` that the examples leave out are `null`. |
133133| `group.actor` | The member. `deleted` is `true` once a member is deactivated or moved to another organization. After a move, `name` and `email_address` are `null`, and `user_id` stays. |
134134| `uncached_input_tokens` | Input tokens neither read from nor written to the prompt cache. |
135| `cache_creation` | Input tokens written to the prompt cache, split by how long the cache keeps them (5 minutes or 1 hour). |
135| `cache_creation` | Input tokens written to the prompt cache, split into 5-minute and 1-hour cache writes. |
136136| `cache_read_input_tokens` | Input tokens read from the prompt cache. |
137137| `output_tokens` | Tokens that Claude generated. |
138138| `total_tokens` | Input and output tokens together, including input written to or read from the prompt cache. |
from line 139
139139| `server_tool_use` | `web_search_requests` is `0`. |
140140| `requests` | Requests that reached Claude, including ones that were canceled or that ended in an error. |
141141| `amount`, `list_amount` | Estimated cost in US cents, as a string. `list_amount` equals `amount`. |
142| `has_more`, `next_page` | Whether more rows remain, and the value of `page` that reads them. See [Read every page of results](#read-every-page-of-results). |
142143| `data_refreshed_at` | The time the figures run up to, as described under [How current the figures are](#how-current-the-figures-are). |
143144
144145### What the estimated cost covers
from line 166
165166
166167### Read every page of results
167168
168While `has_more` is `true`, send the same request again with `page` set to the value of `next_page`. Send the other parameters as they were. You can change `limit`. To read many rows, set `limit` to `1000`.
169While `has_more` is `true`, send the same request again with `page` set to the value of `next_page`. Without `page`, you get the first page again. Send the other parameters as they were. You can change `limit`.
169170
171For example, this query reads every member's usage for October, 1,000 members at a time:
172
173```text theme={null}
174?group_by[]=actor&limit=1000&starting_at=2026-10-01T00:00:00Z&ending_at=2026-11-01T00:00:00Z
175```
176
177For the next 1,000, add `&page=` and the value of `next_page`.
178
170179## Rate limits
171180
172181An organization can send about 60 requests per minute, across all its keys, and four at the same time. A request over either limit returns a 429 error.
from line 195
186195| 401 | `invalid or revoked admin API key` | Check the key, or [create a new one](https://claude.com/docs/government/org-admin/admin-api-keys.md#create-a-key). |
187196| 403 | `missing_scope` | Use a key from the organization's **Admin API keys** page that was created with **Usage and cost reports**. |
188197| 403 | `tenant_restriction_violation` | See [Tenant restrictions](https://claude.com/docs/government/tenant-admin/tenant-restrictions.md). |
189| 404 | `no such Analytics API endpoint` | Check the path. |
198| 404 | `no such Analytics API endpoint` | Use a path that ends in `/usage` or `/cost`. |
190199| 414 | `Request URL is over 8 KiB or has more than 256 query parameters` | Send fewer values, in several requests. |
191200| 429 or 503 | `rate_limited`, `too_many_in_flight`, or `reports_unavailable` | Wait the number of seconds in the `Retry-After` header and try again. |
192201| 504 | `query_timeout` | Use a shorter range, or group by fewer fields. |
third-party/claude-desktop/admin-console Changed · +43 / -18 lines
### Devices that migrated on an earlier release
from line 295
295295
296296### Users in more than one Claude organization
297297
298A user's Claude account can belong to your deployment's organization and to other Claude organizations, and the user can move between them in Claude Desktop. When such a user signs in, the app opens in their other organization and asks whether to switch to yours, with **Switch and restart** and **Not now** buttons. A user who chooses **Not now** isn't asked again on that device and can switch later by choosing your organization from the account menu. Each move into or out of your organization restarts the app, because third-party mode runs as a separate app configuration. To go back, the user chooses **Sign out** and signs in to Claude again after the restart. From Claude Desktop 1.49585.0, they can instead pick their other organization from the account menu, which also restarts the app and asks them to sign in.
298A user's Claude account can belong to your deployment's organization and to other Claude organizations, and the user can move between them in Claude Desktop. When such a user signs in, the app opens in their other organization and asks whether to switch to yours, with **Switch and restart** and **Not now** buttons. A user who chooses **Not now** or presses Esc isn't asked again on that device and can switch later by choosing your organization from the account menu. Each move into or out of your organization restarts the app, because third-party mode runs as a separate app configuration. To go back, the user chooses **Sign out** and signs in to Claude again after the restart. From Claude Desktop 1.49585.0, they can instead pick their other organization from the account menu, which also restarts the app and asks them to sign in.
299299
300300To remove **Not now**, turn on **Require this organization in Claude Desktop** under **Desktop sign-in** on the **Connection** page. Members who also belong to another organization then get the prompt the next time Claude Desktop starts or they sign in, and they can't dismiss it. While they are in your organization, the account menu lists another of their organizations only if that organization has the same setting on. Browsers are not affected.
301301
from line 371
371371
372372Set every setting you rely on in the console, because the console's configuration replaces the profile's. Add your [plugin marketplaces](#plugin-marketplaces) on the **Plugins** page. To migrate users' work, check that the **Automatically import earlier third-party sessions** switch under **Claude.ai data import** on the **Capabilities** page is on (the default). To skip the migration, turn it off. Devices that already migrated keep their items.
373373
374With a bootstrap server, each telemetry category is off unless the server's response sets its key, [`disableEssentialTelemetry`](https://claude.com/docs/third-party/claude-desktop/configuration#disableessentialtelemetry) or [`disableNonessentialTelemetry`](https://claude.com/docs/third-party/claude-desktop/configuration#disablenonessentialtelemetry), to `false`. With the console, both categories are on. To keep them off, turn on the **Block essential telemetry** and **Block nonessential telemetry** switches on the **Telemetry & updates** page before users sign in.
375
374376> [!WARNING]
375377>
376378> The app migrates users' work once on each device, the next time it starts after the user signs in to your organization. It skips uploaded plugins, saved skills, and scheduled tasks if the console has turned that feature off, and optional plugins that your organization doesn't offer yet. Changing those settings later doesn't migrate the skipped items.
379>
380> If a device already migrated into another admin console organization, such as a test organization, it doesn't migrate into yours. To let its user bring earlier sessions over with the [import wizard](https://claude.com/docs/third-party/claude-desktop/import.md#open-the-import-wizard), turn on the **Enable import** switch under **Claude.ai data import** on the **Capabilities** page.
377381
378382**3. Update Claude Desktop**
379383
380Update devices to Claude Desktop 2.42304.0 or later. Earlier releases migrate fewer items.
384Update devices to Claude Desktop 5.1231.0 or later before users sign in. Earlier releases migrate fewer items, and a later update brings back only some of them. See [Devices that migrated on an earlier release](#devices-that-migrated-on-an-earlier-release).
381385
382386**4. Remove the managed profile**
383387
384Remove the Claude Desktop configuration profile or registry policy, including one that carries only bootstrap keys. You can keep a profile that sets only the [app-behavior keys](https://claude.com/docs/third-party/claude-desktop/mdm.md#update-keys-and-managed-precedence) and [`forceLoginOrgUUID`](#keep-a-device-on-its-managed-profile).
388Remove the Claude Desktop configuration profile or registry policy, including one that carries only bootstrap keys. Delete the keys (in the Windows registry, the values) and don't leave them empty. For example, if the only thing left is an empty `bootstrapUrl`, the app treats the profile as invalid, ignores the admin console, and opens standard Claude Desktop. On Windows, check both `HKLM\SOFTWARE\Policies\Claude` and `HKCU\SOFTWARE\Policies\Claude`.
385389
390You can keep a profile that sets only the [app-behavior keys](https://claude.com/docs/third-party/claude-desktop/mdm.md#update-keys-and-managed-precedence) and [`forceLoginOrgUUID`](#keep-a-device-on-its-managed-profile).
391
392* **Devices that need a network proxy**: keep the [network proxy keys](https://claude.com/docs/third-party/claude-desktop/network-proxy.md#pin-a-proxy-from-managed-configuration), which the console can't set. A profile with only these keys also replaces the console's update policy, relaunch window, and re-check interval with [its own values or the defaults](#which-settings-apply-on-a-device-with-a-managed-profile). To set those in the console, add [`forceLoginOrgUUID`](#keep-a-device-on-its-managed-profile) to the profile, which also limits sign-in on the device to your organization.
386393* **Devices that keep a profile with any other key**: see [Devices with a managed profile](#devices-with-a-managed-profile)
387394* **Devices configured in the app**: the user signs out and chooses the Anthropic sign-in option, as described under [Single-machine setup](https://claude.com/docs/third-party/claude-desktop/installation.md#single-machine-setup)
388395
from line 399
392399
393400### What is migrated
394401
395The app migrates these items in the background. The originals stay in place, so migrated sessions use disk space a second time.
402Claude Desktop 5.1231.0 or later migrates these items in the background. [Earlier releases migrate less](#devices-that-migrated-on-an-earlier-release). The originals stay in place, so migrated sessions use disk space a second time.
396403
397* Chat, Cowork, and Code sessions
398* Cowork projects
399* Artifacts
404* Chat, Cowork, and Code sessions, in their custom groups in the sidebar. Cowork sessions keep their connected folders.
405* Cowork projects, with their descriptions, folders, and sidebar pins
406* Artifacts, with their earlier versions
400407* Memory, unless the user paused it
401408* Users' global instructions and **Instructions for Claude**, unless they already set them in your organization
402* Scheduled tasks from Cowork and Code, except one-time tasks whose time has passed
409* Scheduled tasks from Cowork and Code, except one-time tasks whose time has passed. Each task stays on or off as it was. It starts with no runs, and its earlier runs arrive as ordinary sessions.
403410* Plugins that users uploaded, unless [`userPluginUploadsEnabled`](https://claude.com/docs/third-party/claude-desktop/configuration#userpluginuploadsenabled) is `false`
404411* Skills that users saved, unless [`skillCreationEnabled`](https://claude.com/docs/third-party/claude-desktop/configuration#skillcreationenabled) is `false`
405412* Optional organization plugins that users turned on, if you offer them from your plugins directory or from a marketplace that your inference gateway serves
from line 418
411418
412419Users set up these items again:
413420
421* **Project links**: add them again on each project's page
422* **Project folders in Chat**: Claude can't read a migrated project's folder in Chat until the user [adds the folder to the project again](https://claude.com/docs/third-party/claude-desktop/import.md#make-an-imported-project-folder-readable-in-chat)
423* **Approval mode and model of scheduled tasks**: each task arrives with **Default model**, and a Cowork task that ran on **Automatically approve** arrives on **Manually approve**. Until the user sets the mode again, a run that needs an approval waits for them. Cowork offers **Automatically approve** only where [`autoModeEnabled`](https://claude.com/docs/third-party/claude-desktop/configuration#automodeenabled) is `true`.
424* **Sidebar pins of sessions and scheduled tasks**: pin them again
414425* **Optional organization plugins that the migration skipped**: install them again from **Customize → Plugins → Discover → Organization**
415426* **Plugins from marketplaces the user added**: add the marketplace and install the plugins again
416427* **One-time scheduled tasks that the migration skipped**: create them again
417428* **App preferences**: set the model, per-tool permissions, and notifications again
418* **Connected folders in Cowork sessions**: connect the folders again
429* **Files that users attached to sessions**: attach them again
419430* **"Always allow" choices in Cowork sessions and scheduled tasks**: approve again when a session or task asks
420* **Connector sign-ins**: sign in again to any connector that asks
431* **Connector sign-ins**: click **Connect** again on any connector that asks. If your users sign in with your identity provider (OIDC), every connector they had signed in to asks again. For a server that accepts a token in a request header, you can set a [**Headers helper script**](#managed-mcp-servers-that-need-authentication) instead, which needs no sign-in.
421432
422433To let users import their claude.ai conversations, and any local sessions that the migration left out, with the [import wizard](https://claude.com/docs/third-party/claude-desktop/import.md#open-the-import-wizard), turn on the **Enable import** switch (off by default) under **Claude.ai data import** on the **Capabilities** page.
423434
435### Devices that migrated on an earlier release
436
437On a device that migrated before Claude Desktop 5.1231.0, users set up these items themselves:
438
439* **Project descriptions**: enter them again on each project's page
440* **Project folders outside the default location**: the project has a new, empty folder. The user [adds the original folder again](https://claude.com/docs/third-party/claude-desktop/import.md#add-the-original-folder-to-a-copied-project).
441* **Connected folders in Cowork sessions**: connect the folders again
442
443The first time such a device starts 5.1231.0 or later, it gets these items:
444
445* **Sidebar pins of projects and custom groups of sessions**
446* **Earlier versions of artifacts**, if the **Automatically import earlier third-party sessions** switch is still on
447* **The work of a user who had no earlier sessions**, if that switch is still on. Earlier releases migrate nothing for a user who had projects, scheduled tasks, or instructions but no sessions. Projects and scheduled tasks that the user made again in your organization appear twice. A migrated task that was on runs beside the user's new one.
448
424449## Devices with a managed profile
425450
426451A managed profile is a macOS configuration profile, a Windows registry policy, or the Linux `/etc/claude-desktop/managed-settings.json` file, from [MDM](https://claude.com/docs/third-party/claude-desktop/mdm.md) or [bootstrap](https://claude.com/docs/third-party/claude-desktop/bootstrap.md) delivery. A device whose profile sets any key other than the [app-behavior keys](https://claude.com/docs/third-party/claude-desktop/mdm.md#update-keys-and-managed-precedence) uses the profile's configuration until its user moves the device to the admin console's configuration. Where you can, remove every such key other than `forceLoginOrgUUID` before users sign in, as described under [Migrate an existing fleet to the admin console](#migrate-an-existing-fleet-to-the-admin-console).
from line 455
430455To move a device to the admin console's configuration:
431456
4324571. If the profile sets an inference provider or bootstrap keys and the app is open on the profile's configuration, choose **Sign out** from the account menu.
4332. If the profile sets an inference provider or bootstrap keys, choose **Or sign in with Claude.ai** on the sign-in screen.
4582. If the profile sets an inference provider or bootstrap keys, choose **Or sign in with Claude.ai** on the sign-in screen. If the screen doesn't offer it, one of these settings hides it: [`deploymentMode`](https://claude.com/docs/third-party/claude-desktop/configuration#deploymentmode) set to `3p` in the profile, or [`disableDeploymentModeChooser`](https://claude.com/docs/third-party/claude-desktop/configuration#disabledeploymentmodechooser) set to `true` in the profile or in your bootstrap server's response. Remove the setting.
4344593. Sign in to your organization.
4354604. If the app asks **Which organization do you want to work in?**, choose your organization. Otherwise, restart the app when it asks, as described under [Onboard users](#onboard-users).
436461
from line 463
438463
439464[**Require this organization in Claude Desktop**](#users-in-more-than-one-claude-organization) doesn't remove the profile from the prompt. To stop the app from offering the profile, remove the profile from the device. After the removal, a device opens the admin console's configuration if its user moved it there and hasn't signed out or switched away since.
440465
441After the move, the device stays on the admin console's configuration at later launches. Deploying the profile again doesn't move it back, except as described under [Remove users or return to MDM](#remove-users-or-return-to-mdm). If the profile sets an inference provider or bootstrap keys, the account menu also lists the profile's configuration.
466After the move, the device stays on the admin console's configuration at later launches. Deploying the profile again doesn't move it back, except as described under [Remove users or return to MDM](#remove-users-or-return-to-mdm). If the profile sets an inference provider or bootstrap keys, the account menu also lists the profile's configuration. If a device kept its profile during the move, remove the profile's inference provider and bootstrap keys once its user has moved. While they stay, a user who signs out can see [the profile's sign-in screen](#remove-users-or-return-to-mdm) at the next launch.
442467
443468### Which settings apply on a device with a managed profile
444469
from line 501
476501
4775021. Update devices to Claude Desktop 2.37337.0 or later. Earlier versions ignore the admin console when this key is set.
4785032. In the admin console, copy the **Key** and the **Value** from the **Allow only this organization with device management (MDM)** row, under **Desktop sign-in** on the **Connection** page.
4793. Add the key and value to the device's managed profile, in one of the [locations the app reads](https://claude.com/docs/third-party/claude-desktop/mdm.md#4-deploy-the-configuration). Enter a single ID without braces or quotation marks. In the Windows registry, make it a String value (`REG_SZ`). For more than one organization, enter a JSON array of IDs as one string value, such as `["ID-1","ID-2"]`.
5043. Add the key and value to the device's managed profile, in one of the [locations the app reads](https://claude.com/docs/third-party/claude-desktop/mdm.md#4-deploy-the-configuration). Enter a single ID without braces or quotation marks. In the Windows registry, make it a String value (`REG_SZ`) in the same hive as the profile's other keys. The app ignores user policy (`HKCU`) when machine policy (`HKLM`) holds any value. For more than one organization, enter a JSON array of IDs as one string value, such as `["ID-1","ID-2"]`.
4805054. Restart Claude Desktop after the profile reaches the device.
481506
482507If the value lists only other IDs, or the app can't read it, the app uses only the profile and the console's settings stop applying. Correct the value and restart Claude Desktop. If the device doesn't return to the console's configuration, its user signs in to your organization again, as described under [Devices with a managed profile](#devices-with-a-managed-profile).
from line 514
489514
490515## Remove users or return to MDM
491516
492A user returns a device to standard Claude Desktop by choosing **Sign out** from the account menu. The app relaunches signed out. On a device whose managed profile sets an inference provider or bootstrap keys, the sign-in screen also offers **Or sign in with your organization** (or with the provider's name), which restarts the app on the profile's configuration.
517A user returns a device to standard Claude Desktop by choosing **Sign out** from the account menu. The app relaunches signed out. On a device whose managed profile sets an inference provider or bootstrap keys, the sign-in screen also offers **Or sign in with your organization** (or with the provider's name), which restarts the app on the profile's configuration. From Claude Desktop 3.1623.0, if the user quits the app on such a device without signing in again, the next launch shows the profile's sign-in screen. To return to the admin console's configuration, the user chooses **Or sign in with Claude.ai** there.
493518
494519When you remove a user from the organization, Anthropic revokes their Claude Desktop sign-in to that organization. A running app isn't interrupted. At its next launch the app can no longer download the organization's configuration. It shows either your organization's sign-in screen, where **Return to Claude.ai sign-in** returns the device to standard Claude Desktop, or a **Restart required** prompt whose **Restart** button does the same.
495520
third-party/claude-desktop/import Changed · +41 / -5 lines
### If the automatic copy ran on an earlier version ### Add the original folder to a copied project
from line 12
1212
1313Claude Desktop can automatically copy into your history the Cowork, Chat, and Code sessions it stored on this computer under an earlier third-party configuration. In an organization managed from the [Enterprise Admin Console](https://claude.com/docs/third-party/claude-desktop/admin-console.md), this automatic copy is on unless it's turned off in your organization's settings. In any other deployment it runs only if your administrator turns it on.
1414
15Along with the sessions, the automatic copy brings over other things you had under the earlier configuration:
15Along with the sessions, the automatic copy brings over other things you had under the earlier configuration. Claude Desktop 5.1231.0 or later brings these items, and [earlier versions bring less](#if-the-automatic-copy-ran-on-an-earlier-version):
1616
17* **Projects**: your Cowork projects. New tasks use a project's instructions only after you accept them.
17* **Projects**: your Cowork projects, with their descriptions, folders, and sidebar pins. New tasks use a project's instructions only after you accept them. A project's links aren't copied. Add them again.
1818* **Memory and instructions**: your Cowork memory, unless you paused it, and your global instructions. New tasks use them right away. Your **Instructions for Claude** (**Settings → General**) come over too. Instructions you already set under the new configuration are kept.
19* **Scheduled tasks**: your scheduled tasks from Cowork and Code. Each stays on or off as it was.
19* **Scheduled tasks**: your scheduled tasks from Cowork and Code. Each stays on or off as it was. A task arrives with **Default model**, and a Cowork task arrives on **Manually approve**. Set the model again, and set the approval mode again where the app offers **Automatically approve**. Until you do, a run waits for you each time it needs an approval. A task starts with no runs, and its earlier runs are listed as ordinary sessions.
2020* **Uploaded plugins**: plugins you uploaded, unless your administrator has turned off plugin uploads ([`userPluginUploadsEnabled`](https://claude.com/docs/third-party/claude-desktop/configuration#userpluginuploadsenabled)). Each stays on or off as it was.
2121* **Saved skills**: skills you saved, unless your administrator has turned off skill creation ([`skillCreationEnabled`](https://claude.com/docs/third-party/claude-desktop/configuration#skillcreationenabled)).
2222* **Your organization's optional plugins**: the ones you had turned on are turned on again, if they come from your organization's plugins directory or from a marketplace hosted at the address of its gateway or bootstrap server. With Claude Desktop 2.42304.0 or later, plugins from other marketplaces, such as a git repository, are turned on again too, if your administrator offers the marketplace from the same repository or URL as before. On a computer where the copy already ran, they're turned on the first time the app starts on 2.42304.0 or later.
23* **Artifacts**: your Cowork artifacts.
23* **Artifacts**: your Cowork artifacts, with their earlier versions.
2424
2525The copy runs once on each computer, in the background shortly after the app starts, and the sessions then appear in the sidebar. Your original sessions stay where they were, and sessions you already imported are skipped. The copy is listed under **Import history** in **Settings → Import & export**, where the **Remove** button deletes the copied sessions and the projects copied with them. The app doesn't copy them again later.
2626
27Copied sessions go back into custom groups of the same name in the sidebar, and Cowork sessions keep their connected folders. Sessions and scheduled tasks arrive unpinned. The copy doesn't bring connector sign-ins, files you attached to sessions, or **Always allow** choices. It also doesn't bring app preferences such as the model, per-tool permissions, and notifications. Set them up again as you need them.
28
2729Use the [import wizard](#open-the-import-wizard) for your claude.ai conversations and projects, and for any local sessions the automatic copy left out.
30
31### If the automatic copy ran on an earlier version
32
33If the copy ran on a Claude Desktop version before 5.1231.0, set up these items yourself:
34
35* **Project descriptions**: enter them again on each project's page
36* **Folders connected to Cowork sessions**: connect them again
37* **Project folders outside the default location**: [add the original folder again](#add-the-original-folder-to-a-copied-project)
38
39The first time the app starts on 5.1231.0 or later, it brings these items:
40
41* **Sidebar pins of your projects and custom groups of your sessions**
42* **Earlier versions of your artifacts**, if the automatic copy is still on
43* **Your projects, scheduled tasks, and instructions**, if you had no earlier sessions and the automatic copy is still on. Before 5.1231.0, the app copies nothing for someone with no sessions. Projects and scheduled tasks that you made again under the new configuration appear twice. Delete the ones you don't need.
44
45### Add the original folder to a copied project
46
47If a copied project's folder shows **Empty folder** when you expand it under **Context** on the project's page, the copy didn't keep the original folder. The original folder and its files stay where they were. Add the original folder once for each of these projects.
48
49Before Claude Desktop 5.1231.0, this happens to every project whose folder isn't directly inside the **Projects** folder of your Cowork files folder. Your Cowork files folder is `~/Claude` by default. To check, go to **Settings > Cowork** and read the path under **Cowork files**.
50
51**1. Open the project**
52
53Go to the **Projects** page and open the copied project.
54
55**2. Add the original folder**
56
57Next to **Context**, click **+**, select **Choose a folder**, then select **Choose a different folder** in the submenu. In the folder dialog, select the project's original folder.
58
59**3. Remove the empty folder**
60
61**Context** now lists both folders, which can have the same name. Click each folder to expand it. Click the **x** on the row of the one that shows **Empty folder**.
62
63New tasks in the project now work in the original folder. Sessions that were copied with the project still use the empty folder. Start a new task to work with your files.
2864
2965## Before you open the import wizard
3066
third-party/claude-desktop/telemetry Changed · +4 / -2 lines
from line 12
1212
1313To find out whether a managed profile's keys apply on a device that uses the [Enterprise Admin Console](https://claude.com/docs/third-party/claude-desktop/admin-console.md), see [Which settings apply on a device with a managed profile](https://claude.com/docs/third-party/claude-desktop/admin-console.md#which-settings-apply-on-a-device-with-a-managed-profile).
1414
15On a device that gets its configuration from a [bootstrap server](https://claude.com/docs/third-party/claude-desktop/bootstrap.md), essential and non-essential telemetry are each off unless the server's response sets the category's key to `false`.
16
1517### Essential telemetry
1618
1719Crash reports, error stack traces, and performance timings. Contains diagnostic metadata (app version, OS, error type, redacted stack frames) but **never prompt or response content**. Attributed to your organization via `deploymentOrganizationUuid` so Anthropic support can find issues you report.
from line 20
1820
1921| Setting | Default | Effect when `true` |
2022| - | - | - |
21| `disableEssentialTelemetry` | `false` | No crash or error data leaves the device. |
23| `disableEssentialTelemetry` | `false` (`true` with a bootstrap server) | No crash or error data leaves the device. |
2224
2325On Claude Desktop 2.7032.0 and later, the [**Keep only your organization ID and restrictions on disk**](https://claude.com/docs/third-party/claude-desktop/admin-console.md#configuration-kept-on-devices) switch in the [Enterprise Admin Console](https://claude.com/docs/third-party/claude-desktop/admin-console.md) also stops the app's crash reports, even while `disableEssentialTelemetry` is `false`. Error stack traces and performance timings still leave the device while `disableEssentialTelemetry` is `false`.
2426
from line 34
3234
3335| Setting | Default | Effect when `true` |
3436| - | - | - |
35| `disableNonessentialTelemetry` | `false` | No product analytics leave the device. |
37| `disableNonessentialTelemetry` | `false` (`true` with a bootstrap server) | No product analytics leave the device. |
3638
3739Claude Code's usage telemetry is part of this category and goes to `api.anthropic.com`. While this category is on, allow that host at the perimeter, as listed under [Non-essential telemetry](#non-essential-telemetry-disablenonessentialtelemetry-false). Claude Code sends this telemetry from outside the agent's sandbox, so the host needs no entry in `coworkEgressAllowedHosts`.
3840
third-party/claude-desktop/code Changed · +1 / -1 lines
from line 30
3030| `otlpEndpoint`, `otlpProtocol`, `otlpHeaders`, `otlpResourceAttributes` | Routes Claude Code's OpenTelemetry metrics and logs to your collector. See [Telemetry](https://claude.com/docs/third-party/claude-desktop/telemetry.md). |
3131| `disableEssentialTelemetry`, `disableNonessentialTelemetry` | Disables Claude Code's crash reporting and usage telemetry to Anthropic, mirroring Cowork. |
3232| `disableAutoUpdates` | The embedded Claude Code engine never self-updates regardless of this key; its version is managed by the app's own updater. |
33| `inferenceMaxTokensPerWindow`, `inferenceTokenWindowHours` | The token budget is shared across Cowork and Code sessions and enforced before each turn. |
33| `inferenceMaxTokensPerWindow`, `inferenceTokenWindowHours` | The token budget is shared across Cowork and Code sessions and enforced before each turn. Tokens from [subagents](https://code.claude.com/docs/en/sub-agents) and [conversation compaction](https://claude.com/docs/third-party/claude-desktop/gateway.md#context-window-and-compaction) count toward it in Claude Desktop 5.1231.0 or later. |
3434
3535[`mcpPersistentAlwaysAllowEnabled`](https://claude.com/docs/third-party/claude-desktop/configuration#mcppersistentalwaysallowenabled) also applies to Code sessions. When it's `false`, the approval prompt for an MCP tool offers **Allow for this session** in place of **Always allow**, and the approval isn't saved to Claude Code's settings files. Allow rules already in those files, and hooks, keep allowing the tool until someone removes them. For scheduled tasks, see [Tool approvals on scheduled tasks](https://claude.com/docs/third-party/claude-desktop/configuration.md#tool-approvals-on-scheduled-tasks).
3636
third-party/claude-desktop/connectors-m365 Changed · +2 / -2 lines
from line 230
230230
231231### Troubleshoot sign-in errors
232232
233These errors can appear during setup.
233These errors can appear during setup. For errors that this connector shares with other remote managed MCP servers, such as `Unexpected content type: text/html` in `main.log`, see [MCP server sign-in](https://claude.com/docs/third-party/claude-desktop/mcp-sign-in.md#troubleshoot-sign-in).
234234
235235| Error | Cause | Fix |
236236| - | - | - |
237| `Connection to server failed. You can try again.` with no Microsoft sign-in page, and the user's [`main.log`](https://claude.com/docs/third-party/claude-desktop/data-storage#where-data-lives) shows an HTML block page from your network, starting at the `[error]` line that contains the entry's `name` (`m365` unless you changed it) and the word `failed` | A firewall or secure web gateway blocked the request to the connector service before sign-in started | Send the block page to your network team and ask them to [allow MCP traffic to the connector service's host](#allow-the-required-network-hosts) |
237| Either `Couldn't connect to <name>. Try again later. If it keeps failing, ask your IT admin whether a firewall or proxy is blocking MCP traffic.` (Claude Desktop 5.1231.0 or later) or `Connection to server failed. You can try again.`, with no Microsoft sign-in page, and the user's [`main.log`](https://claude.com/docs/third-party/claude-desktop/data-storage#where-data-lives) shows an HTML block page from your network, starting at the `[error]` line that contains the entry's `name` (`m365` unless you changed it) and the word `failed` | A firewall or secure web gateway blocked the request to the connector service before sign-in started | Send the block page to your network team and ask them to [allow MCP traffic to the connector service's host](#allow-the-required-network-hosts) |
238238| `AADSTS50011` redirect mismatch | Redirect URI is not exactly `http://127.0.0.1/callback`, or was registered under *Web* instead of *Mobile and desktop applications* | Re-check step 2.1 |
239239| `AADSTS50194` multi-tenant required | Tenant ID is missing from the configuration | Add Tenant ID in step 4 |
240240| `AADSTS65001` admin consent required | Step 1 was not completed, or step 2.4 was skipped | Complete admin consent |
third-party/claude-desktop/mcp-sign-in Changed · +2 / -1 lines
from line 89
8989
9090| What the user sees or `main.log` records | Cause | Fix |
9191| - | - | - |
92| "Connection to server failed. You can try again." with no sign-in window, and `main.log` shows an HTML block page from your network, starting at the `[error]` line that contains the server's name and the word `failed` | A firewall or secure web gateway blocked the request to the MCP server before sign-in started. Such equipment can classify the connection as Model Context Protocol (MCP) traffic and block it even when the server's host is allowed | Send the block page to your network team and ask them to allow MCP traffic to the server's host. Then have the user click **Connect** again |
92| Either "Couldn't connect to \{server}. Try again later. If it keeps failing, ask your IT admin whether a firewall or proxy is blocking MCP traffic." (Claude Desktop 5.1231.0 or later) or "Connection to server failed. You can try again.", with no sign-in window, and `main.log` shows an HTML block page from your network, starting at the `[error]` line that contains the server's name and the word `failed` | A firewall or secure web gateway blocked the request to the MCP server before sign-in started. Such equipment can classify the connection as Model Context Protocol (MCP) traffic and block it even when the server's host is allowed | Send the block page to your network team and ask them to allow MCP traffic to the server's host. Then have the user click **Connect** again |
93| `main.log` shows `Unexpected content type: text/html` on the `[error]` line that contains the server's name and the word `failed` | The request got a web page with a success status in place of the MCP server's response, and `main.log` didn't record the page. The page can be a block page from your network or a website that the entry's **URL** points to | Check that the entry's **URL** is the MCP server's endpoint. If it is, ask your network team whether a firewall or secure web gateway blocks MCP traffic to the server's host. If one does, ask them to allow that traffic |
9394| "Couldn't connect to \{server} because it doesn't support automatic client registration" (Claude Desktop 2.110.0 or later), or `main.log` records that the authorization server does not support dynamic client registration | **OAuth** is **Auto-register** but the identity provider requires a client that you register | Register a public client with redirect URI `http://127.0.0.1:53280/callback`, set **OAuth** to **Bring your own client**, and fill in **Client ID** |
9495| The browser step succeeds, then the connection fails and `main.log` records the token endpoint's error, for example `client_secret is missing` | The entry has a **Client ID** but the identity provider also requires the secret | Add the secret and **Authorization server** as described under [Where the client secret goes](#where-the-client-secret-goes) |
9596| `main.log` names a rejected referrer host during sign-in | The identity provider completes sign-in from a host other than the one in its authorization URL | Add that hostname to **Additional redirect referrer hosts** |