One read of Claude Documentationclaude-docs-20261109T193001Z
3 pages moved out of 281 read.
Pages moved
3
significant first
Pages read
281
in this capture
Captured
19:30 UTC
Corpus hash
b2bc5e9220f1
corpus-hash
What this read moved
1-3 of 3third-party/claude-desktop/data-storage Changed · +20 / -1 lines
### Data shared with standard Claude Desktop
from line 12
1212
1313## Where data lives
1414
15Claude Desktop on 3P stores everything under a dedicated directory, separate from standard Claude Desktop, so the two modes can coexist on one machine without interfering.
15Claude Desktop on 3P keeps its application data and logs in directories of its own, separate from those of standard Claude Desktop. A few locations in the user's home directory are outside these directories, and [standard Claude Desktop uses them too](#data-shared-with-standard-claude-desktop).
1616
1717| Platform | Application data | Logs |
1818| - | - | - |
from line 50
5050
5151Separately from the application-data directory, Claude Desktop writes user-visible outputs (Artifacts and scheduled-task results) to `~/Claude/` in your home directory, or `~/Documents/Claude/` on legacy installs. This folder is intended for you to browse directly and is not removed when you delete the application-data directory. To back up a user's data, copy every location listed under [Copy the data to the new device](#copy-the-data-to-the-new-device).
5252
53### Data shared with standard Claude Desktop
54
55Unless you [restrict a device to one deployment mode](https://claude.com/docs/third-party/claude-desktop/mdm.md#restrict-a-device-to-one-deployment-mode), a user can switch, in the same OS user account, between Claude Desktop on 3P and standard Claude Desktop, where users sign in to claude.ai. On a device where you haven't turned on the [migration to Claude Enterprise](https://claude.com/docs/third-party/claude-desktop/move-to-claude-enterprise.md), the two modes handle the user's data as follows:
56
57* **Chats, Cowork tasks, projects, and memory**: standard Claude Desktop doesn't show, import, or upload those stored in the 3P [application-data directory](#where-data-lives). It reads and writes some settings files in that directory, such as the user's choice of mode. It also reads the Code session records in `claude-code-sessions/`, so that it doesn't list those sessions or delete their folders.
58* **Code sessions**: each mode lists only its own, but **Code** in both modes and Claude Code in the terminal keep their transcripts in the same folder, `~/.claude/`. Each mode reads the transcripts there to count usage, and the figures that standard Claude Desktop shows for `/stats` in **Code** include sessions from both modes and the terminal. Claude Code in the terminal can resume a session from either mode, and then sends the earlier conversation to the provider that the terminal uses.
59* **Claude Code setup**: `~/.claude/` and `~/.claude.json` also hold Claude Code's setup, such as skills, plugins, hooks, permission rules, trusted folders, and MCP servers, shared by **Code** in both modes and Claude Code in the terminal. Sign-ins to MCP servers made in **Code** are in [Claude Code's own credential store](https://code.claude.com/docs/en/authentication#credential-management), which they share too.
60* **Connectors**: standard Claude Desktop doesn't load the connectors, plugins, or extensions that users added outside **Code**. From your [`managedMcpServers`](https://claude.com/docs/third-party/claude-desktop/configuration#managedmcpservers) entries, it loads only a built-in Microsoft 365 connector set in the device's managed profile.
61* **Connector sign-ins**: on a device configured by MDM, a local file, or a bootstrap server, switching modes leaves [connector sign-ins](#credentials) made outside **Code** in place and doesn't revoke them. Standard Claude Desktop doesn't use them, and Claude Desktop on 3P uses them again when the user switches back.
62* **Files in `~/Claude/`**: by default, both modes write Artifacts, scheduled tasks, and project files here, and each lists only its own. To give Claude Desktop on 3P a folder of its own, have the user go to **Settings > Cowork** and click **Change** next to **Cowork files**. The app copies everything in the current folder, the other mode's files included, to the new location and leaves the old folder in place.
63
64With the migration on, standard Claude Desktop also copies what [What is migrated](https://claude.com/docs/third-party/claude-desktop/move-to-claude-enterprise.md#what-is-migrated) lists, and `~/.claude/`, `~/.claude.json`, and `~/Claude/` are still shared.
65
66No configuration key moves these three locations. They are in the user's home directory, so each OS user account has its own.
67
68A [diagnostic report](https://claude.com/docs/third-party/claude-desktop/installation.md#troubleshooting), or the `.zip` file from **Help > Troubleshooting > Show Logs in Finder** (**Show Logs in File Explorer** on Windows), includes app log lines from both modes, whichever mode the user creates it in.
69
5370### Session audit log
5471
5572As a Cowork session or Chat conversation runs on the device, the app writes an `audit.jsonl` file in the session's working directory, under `local-agent-mode-sessions/` in the [application-data directory](#where-data-lives). The file holds the conversation's content. The session's transcript, under the same directory, holds it too. The app appends the full text of:
from line 353
336353## Removing data
337354
338355To fully reset a device's Claude Desktop on 3P state, delete the application-data directory above and the `~/Claude/` user-files folder. Code session transcripts are in Claude Code's store at `~/.claude/projects/`, which Claude Code in the terminal also uses, so delete them there separately if you need to remove them. For [SSH remote sessions](https://claude.com/docs/third-party/claude-desktop/ssh-remote-sessions.md#host-requirements), transcripts are in `~/.claude/projects/` and attached files in `~/.claude/uploads/` in the SSH user's home directory on the remote host. Claude Desktop also copies those transcripts to the device, into folders in `~/.claude/projects/` whose names start with `ssh-`, so delete them in both places.
356
357On a device that also runs standard Claude Desktop, `~/Claude/` and `~/.claude/` hold that mode's files too, so deleting them deletes those as well. See [Data shared with standard Claude Desktop](#data-shared-with-standard-claude-desktop).
339358
340359> [!NOTE]
341360>
third-party/claude-desktop/mdm Changed · +1 / -1 lines
from line 137
137137
138138* **`3p`**: the app uses the connection that the managed source sets, such as an inference provider or bootstrap keys. The sign-in screen doesn't offer **Or sign in with Claude.ai**. With nothing to connect to in the same managed source, the app opens standard Claude Desktop, so set a connection there to keep users from signing in to claude.ai.
139139* **`1p`**: the app always runs as standard Claude Desktop and ignores inference provider and bootstrap keys.
140* **`any`**: the same as leaving the key unset.
140* **`any`**: the same as leaving the key unset. Where users can switch, the two modes [share some data on the device](https://claude.com/docs/third-party/claude-desktop/data-storage.md#data-shared-with-standard-claude-desktop).
141141
142142With `3p` or `1p`, a user can't [move the device to an Enterprise Admin Console organization](https://claude.com/docs/third-party/claude-desktop/admin-console.md#keep-a-device-on-its-managed-profile), and the app doesn't offer or accept the [Claude API account sign-in](https://claude.com/docs/third-party/claude-desktop/claude-api.md#which-devices-offer-the-claude-api-account-sign-in). To allow the move only to your organization, set [`forceLoginOrgUUID`](https://claude.com/docs/third-party/claude-desktop/admin-console#keep-a-device-on-its-managed-profile) instead. The app ignores `deploymentMode` in a bootstrap response. It treats a misspelled value as `3p`.
143143
third-party/claude-desktop/move-to-claude-enterprise Changed · +2 / -2 lines
from line 8
88
99## What is migrated
1010
11The migration never changes or deletes the Claude (third-party) data.
11The migration never changes or deletes the Claude (third-party) data. Nothing migrates until you turn the migration on, as described under [Migrate your fleet](#migrate-your-fleet).
1212
1313**Migrated automatically:**
1414
from line 68
6868Choose one option for the keys that connect Claude to your cloud provider, such as keys that start with `inference` or `bootstrap`:
6969
7070* **To move everyone to Claude Enterprise**, remove those keys. Also remove [`disableDeploymentModeChooser`](https://claude.com/docs/third-party/claude-desktop/configuration#disabledeploymentmodechooser), [`deploymentMode`](https://claude.com/docs/third-party/claude-desktop/mdm#restrict-a-device-to-one-deployment-mode), and [`deploymentOrganizationUuid`](https://claude.com/docs/third-party/claude-desktop/configuration#deploymentorganizationuuid). If your settings come from a [bootstrap server](https://claude.com/docs/third-party/claude-desktop/bootstrap.md), copy the keys you want to keep into the policy or profile itself.
71* **To let each user switch between your cloud provider and Claude Enterprise**, keep those keys and `deploymentOrganizationUuid`. They must be in the same `HKEY_LOCAL_MACHINE` policy or configuration profile as `importThirdPartyHistoryIntoOrgUUID`, because on Windows Claude [reads one policy location](https://claude.com/docs/third-party/claude-desktop/mdm.md#4-deploy-the-configuration). Make sure [`disableDeploymentModeChooser`](https://claude.com/docs/third-party/claude-desktop/configuration#disabledeploymentmodechooser) isn't set in the policy or profile, or by your bootstrap server, and that [`deploymentMode`](https://claude.com/docs/third-party/claude-desktop/mdm#restrict-a-device-to-one-deployment-mode) is unset or `any`. Claude's welcome screen then offers **Or sign in with Claude.ai**. Your cloud provider settings still apply while a user works with your cloud provider.
71* **To let each user switch between your cloud provider and Claude Enterprise**, keep those keys and `deploymentOrganizationUuid`. They must be in the same `HKEY_LOCAL_MACHINE` policy or configuration profile as `importThirdPartyHistoryIntoOrgUUID`, because on Windows Claude [reads one policy location](https://claude.com/docs/third-party/claude-desktop/mdm.md#4-deploy-the-configuration). Make sure [`disableDeploymentModeChooser`](https://claude.com/docs/third-party/claude-desktop/configuration#disabledeploymentmodechooser) isn't set in the policy or profile, or by your bootstrap server, and that [`deploymentMode`](https://claude.com/docs/third-party/claude-desktop/mdm#restrict-a-device-to-one-deployment-mode) is unset or `any`. Claude's welcome screen then offers **Or sign in with Claude.ai**. Your cloud provider settings still apply while a user works with your cloud provider. With your cloud provider and with Claude Enterprise, Claude uses some of the same folders on the computer, as described under [Data shared with standard Claude Desktop](https://claude.com/docs/third-party/claude-desktop/data-storage.md#data-shared-with-standard-claude-desktop).
7272
7373Leave other keys in place. In Claude Enterprise, the desktop extensions feature is on unless [`isDesktopExtensionEnabled`](https://claude.com/docs/third-party/claude-desktop/configuration#isdesktopextensionenabled) is set to `false`.
7474