One read of Claude Documentationclaude-docs-20261105T190710Z
3 pages moved out of 281 read.
Pages moved
3
significant first
Pages read
281
in this capture
Captured
19:07 UTC
Corpus hash
068bc7aa57e5
corpus-hash
What this read moved
1-3 of 3third-party/claude-desktop/data-storage Changed · +67 / -5 lines
### When to use an export or a copy ### Turn on export and import ### What can leave and enter a device ### What a copy moves
from line 72
7272
7373## Memory
7474
75During Cowork sessions, Claude writes short Markdown files recording what it has learned about the user (working preferences, project context, and corrections) and reads them at the start of subsequent sessions. In a scheduled Cowork task outside a project, Claude can read these files but doesn't save to them: it lists the notes with their one-line descriptions and chooses which to open. These files live under `local-agent-mode-sessions/.../memory/memory/`, and the app doesn't sync them to a server. What Claude reads from them becomes part of the session, so it goes to your configured inference provider with the rest of the conversation.
75During Cowork sessions, Claude writes short Markdown files recording what it has learned about the user (working preferences, project context, and corrections) and reads them at the start of subsequent sessions. In a scheduled Cowork task outside a project, Claude can read these files but doesn't save to them: it lists the notes with their one-line descriptions and chooses which to open. These files live under `local-agent-mode-sessions/.../memory/memory/`. The app doesn't sync them to a server. The files themselves leave the device if the user [exports them](#turn-on-export-and-import) or you copy them. What Claude reads from them becomes part of the session, so it goes to your configured inference provider with the rest of the conversation.
7676
7777Where sessions run on the device, users find the memory controls in these places:
7878
from line 88
8888
8989## Chat conversations
9090
91[Chat](https://claude.com/docs/third-party/claude-desktop/chat.md) conversations follow the same storage model as Cowork sessions: each conversation is a session state file plus a working directory under `local-agent-mode-sessions/`, in the layout described in the table above. The state file records the conversation; the working directory holds the transcript, an `uploads/` directory with copies (or hard links) of files attached to the conversation, an `outputs/` directory for files Claude creates during the conversation (its scratch space), and the [session audit log](#session-audit-log). Because attachments are hard-linked where the filesystem allows it, edits made to the original file while the conversation is open can be visible to the conversation. Conversation content leaves the device only as inference requests to your configured provider, as web search queries to your configured search backend, through web access your egress configuration allows, through [sandbox network access](https://claude.com/docs/third-party/claude-desktop/chat.md#sandbox-network-access), in connector tool calls permitted by your `toolPolicy` configuration and the user's approvals, and, if you have enabled [content capture](https://claude.com/docs/third-party/claude-desktop/telemetry.md#content-capture), in telemetry to your own collector.
91[Chat](https://claude.com/docs/third-party/claude-desktop/chat.md) conversations follow the same storage model as Cowork sessions: each conversation is a session state file plus a working directory under `local-agent-mode-sessions/`, in the layout described under [Where data lives](#where-data-lives). The state file records the conversation; the working directory holds the transcript, an `uploads/` directory with copies (or hard links) of files attached to the conversation, an `outputs/` directory for files Claude creates during the conversation (its scratch space), and the [session audit log](#session-audit-log). Because attachments are hard-linked where the filesystem allows it, edits made to the original file while the conversation is open can be visible to the conversation. Conversation content leaves the device only as inference requests to your configured provider, as web search queries to your configured search backend, through web access your egress configuration allows, through [sandbox network access](https://claude.com/docs/third-party/claude-desktop/chat.md#sandbox-network-access), in connector tool calls permitted by your `toolPolicy` configuration and the user's approvals, in telemetry to your own collector if you have enabled [content capture](https://claude.com/docs/third-party/claude-desktop/telemetry.md#content-capture), in the zip files that users export if you have [turned on export](#turn-on-export-and-import), and in any copy that you make.
9292
9393For the questions security reviews most often ask about Chat:
9494
from line 205
205205
206206## Move a user to a new device
207207
208You can move a user's Claude Desktop data to a new device with an export or a copy:
209
210* **Export and import**: you [turn on two settings](#turn-on-export-and-import). The user exports their data to a zip file on the old device and imports it on the new device.
211* **[Copy the data](#copy-the-data-to-the-new-device)**: on devices that get their configuration from MDM or from the [Enterprise Admin Console](https://claude.com/docs/third-party/claude-desktop/admin-console.md), you copy the user's [application-data directory](#where-data-lives) and related folders to the same paths on the new device
212
213### When to use an export or a copy
214
215Both ways need the same platform (macOS, Windows, or Linux) on both devices. A copy moves more data.
216
217Copy the data if:
218
219* **The user's Cowork projects and scheduled tasks use many folders.** After an import, the user adds each folder again.
220* **On Windows, the user's Code sessions or Code scheduled tasks use folders on a mapped network drive.** An import leaves out those sessions and tasks.
221* **Your policies don't let users save their conversations and files to a zip file**
222* **Claude Desktop doesn't open on the old device**, so the user can't start an export
223* **You set `allowedOrganizationUuids`** under [`claudeAiImport`](https://claude.com/docs/third-party/claude-desktop/configuration#claudeaiimport), which turns off import from a file
224* **The export dialog says that the export is over the import limit of 20 GB or 5,000,000 files**
225
226Use an export and import if:
227
228* **The new device has a different OS user name or home-directory path.** A copy needs the same user name and path.
229* **The user already works on the new device.** An import adds to their data, and a copy replaces it.
230
231### Turn on export and import
232
233Both settings are off by default.
234
235* **Managed configuration**: set [`claudeAiImport`](https://claude.com/docs/third-party/claude-desktop/configuration#claudeaiimport) to `{"enabled": true, "exportEnabled": true}`, along with any fields you already set in it
236* **[Enterprise Admin Console](https://claude.com/docs/third-party/claude-desktop/admin-console.md)**: go to the **Capabilities** page and turn on the **Enable import** and **Enable export** switches under **Claude.ai data import**. To turn them on for some users, use a [per-group permission policy](https://claude.com/docs/third-party/claude-desktop/admin-console.md#per-group-permission-policies).
237
238Both devices need Claude Desktop 4.23118.0 or later, the same platform, and [the same organization](#requirements-for-the-new-device). Earlier versions export only sessions, their output files, and project names.
239
240If a setting is already on, it applies to [the additional data](#what-can-leave-and-enter-a-device) as soon as a user's app [updates](https://claude.com/docs/third-party/claude-desktop/installation.md#updates) to 4.23118.0 or later. With `enabled`, users can import that data. With `exportEnabled` too, users can export it. To stop either one, turn off that setting.
241
242For the user's steps and the full list of data that moves, see [Move your data to another device](https://claude.com/docs/third-party/claude-desktop/import.md#move-your-data-to-another-device).
243
244### What can leave and enter a device
245
246`exportEnabled` works only when `enabled` is on.
247
248* **`exportEnabled`**: users can export their data to a zip file anywhere they can save files. The file contains sessions with attached and output files, projects, the files of each project whose folder is in the default location (`~/Claude/Projects`), memory, scheduled tasks, saved skills, uploaded plugins, some app preferences, and the commands, arguments, and environment variable names of local MCP servers. It also lists the paths of the other folders that projects use, and of the folders and files that scheduled tasks use. If you set `allowedOrganizationUuids`, it contains only sessions, their files, and project names and instructions.
249* **`enabled`**: users can import an export file from another device, a claude.ai data export, and earlier sessions on the device. Claude Desktop can't verify who made an export file, so it asks the user to confirm that the file is their own. If the user doesn't confirm, only the sessions are imported, with the projects and attached files that they use.
250
251After the user confirms:
252
253* **Memory**: Claude uses it right away, including when scheduled tasks run. Paused memory is in the file but isn't imported.
254* **App preferences**: those that the user hasn't set on the new device apply right away
255* **Project instructions**: Claude uses them after the user accepts them
256* **Project files**: the import copies them into a new folder for each project
257* **Folders**: the import doesn't connect any to a project or a Cowork task. A Code session or a Code scheduled task keeps its folder only if the new device trusts that folder. The last screen lists the folders that the user's projects and scheduled tasks used.
258* **Uploaded plugins, saved skills, and scheduled tasks**: they stay off until the user turns them on. Setting [`userPluginUploadsEnabled`](https://claude.com/docs/third-party/claude-desktop/configuration#userpluginuploadsenabled), [`skillCreationEnabled`](https://claude.com/docs/third-party/claude-desktop/configuration#skillcreationenabled), or [`scheduledTasksEnabled`](https://claude.com/docs/third-party/claude-desktop/configuration#scheduledtasksenabled) to `false` keeps that kind of data out of the import.
259* **Local MCP servers**: for each import, a second dialog lists up to five servers with their full commands and environment variables. Claude Desktop tries to start the servers that the user adds right away. Blocks that the user set on tools on the old device don't apply, because tool permissions aren't imported. The app writes no values of these servers' environment variables into an export. Until the user enters the values, a server might not work, or might run without a limit that the user set in a variable. Setting [`isLocalDevMcpEnabled`](https://claude.com/docs/third-party/claude-desktop/configuration#islocaldevmcpenabled) to `false` keeps local MCP servers out of the export and the import.
260
261> [!WARNING]
262>
263> The zip file isn't encrypted. Sessions, project files, memory, scheduled tasks, skills, plugins, and the arguments of local MCP servers are copied as they are, with any passwords or API keys written in them. Sign-ins, connector tokens, saved provider API keys, and the values of environment variables for the local MCP servers that users added stay on the old device. Tell users to import only their own exports, to keep the file private, and to delete every copy when they no longer need it.
264
265The old device keeps its data until you [remove it](#removing-data).
266
267### What a copy moves
268
208269On devices that get their configuration from MDM or from the [Enterprise Admin Console](https://claude.com/docs/third-party/claude-desktop/admin-console.md), you can move a user to a new device by copying their data. The copy moves:
209270
210271* Chats, Cowork tasks, and Code sessions
from line 272
211272* Projects, project instructions, and memory
212273* Scheduled tasks, skills, and plugins
213274* Attached files
275* Local MCP server settings and app preferences
214276
215277### What the user sets up again
216278
217Ask the user to:
279After a copy, ask the user to:
218280
219281* Sign in to the inference provider, if the app asks
220282* Enter the provider API key again, if the user saved it in the in-app configuration window (see [Unreadable saved API keys](#unreadable-saved-api-keys))
from line 288
226288
227289### Requirements for the new device
228290
229The new device needs:
291For a copy, the new device needs:
230292
231293* The same platform (macOS, Windows, or Linux) and CPU architecture as the old device
232294* The same OS user name and home-directory path. Otherwise, Code sessions, scheduled tasks, plugins, and project folders stop working.
from line 340
278340
279341To return to standard Claude Desktop without removing data, choose the Anthropic sign-in option on the sign-in screen; to also remove the locally authored 3P configuration, delete the `configLibrary/` directory.
280342
281Except for SSH remote sessions, conversation history exists only on this device, so deleting it is unrecoverable. Deleting an SSH remote session in the app doesn't delete its transcript on the remote host.
343Except for SSH remote sessions and any export or copy that was made, conversation history exists only on this device, so deleting it is unrecoverable. Deleting an SSH remote session in the app doesn't delete its transcript on the remote host.
282344
third-party/claude-desktop/import Changed · +139 / -23 lines
## Move your data to another device ### What a Claude Desktop export moves ### Export your data from the old device ### Import your data on the new device ### Turn on imported plugins, skills, and scheduled tasks ### Set up imported local MCP servers ## What a claude.ai import includes ## Troubleshoot an import or export ### The import can’t start until a one-time download finishes ### Import failed with a code under the message ### Problems when you move to another device ## Export sessions to move them to another device ## What is and isn't included ## Troubleshoot the import wizard
from line 1
11# Import history from claude.ai
22
3> Bring conversations, projects, and local Cowork and Code sessions into Claude Desktop on 3P from a claude.ai workspace or an earlier install
3> Bring conversations, projects, and local Cowork and Code sessions into Claude Desktop on 3P from a claude.ai workspace, an earlier install, or another device
44
55Import brings a copy of your claude.ai conversations and projects into Claude Desktop on third-party (3P), along with any Cowork and Claude Code sessions already on this machine from an earlier install. Everything lands in the local session store described in [User identity and local data](https://claude.com/docs/third-party/claude-desktop/data-storage.md), so you can pick up work you started on claude.ai and continue it against your organization's own inference provider.
66
77Each import is a one-time copy. New activity on claude.ai after you import does not appear in Claude Desktop unless you import again, and importing from claude.ai again does not create duplicates.
88
9To take your Claude Desktop data to a new device, see [Move your data to another device](#move-your-data-to-another-device).
10
911## Automatic import of earlier third-party sessions
1012
1113Claude 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.
from line 135
133135
134136The Duplicates step, listing imported projects that match ones you already have.
135137
136* **Merge into existing** moves the imported chats and sessions into your existing project and removes the duplicate. Folders you attached to the duplicate move with them. If your existing project has no instructions of its own, the imported project's instructions are shown there for you to review and accept. Later imports from the same source land in the existing project as well, except from a folder or zip you added, where the wizard asks again.
138* **Merge into existing** moves the imported chats and sessions into your existing project and removes the duplicate. Folders you attached to the duplicate move with them. If your existing project has no instructions of its own, the imported project's instructions are shown there for you to review and accept. Later imports from the same source go into the existing project as well, except from a folder you added, where the wizard asks again. For a [Claude Desktop export](#move-your-data-to-another-device), the wizard also asks again unless you click **Import as my own** each time.
137139* **Keep separate** leaves both projects in place. The imported one keeps a numbered name, such as **Northwind (1)**, and Claude Desktop stops offering to merge it.
138140
139141The **Projects** page offers the same two choices, in a row under the duplicate project's card and at the top of the duplicate project's own page. Decide there if your history was brought over automatically when you signed in, so you never saw the wizard, or if you closed the wizard before choosing.
from line 175
173175
174176Your administrator can also limit which folders Claude reads. See [Project folders in Chat](https://claude.com/docs/third-party/claude-desktop/chat.md#project-folders-in-chat).
175177
176## Export sessions to move them to another device
178## Move your data to another device
177179
178When your administrator also sets `exportEnabled` to `true` under `claudeAiImport`, **Settings → Import & export** offers **Export…**, which writes this computer's chats, Cowork tasks, and Code sessions (not terminal Claude Code sessions) to a zip file. On the other device, open the import wizard and select that zip with **Choose file…**; the wizard lists its sessions in the [Cowork & Code step](#step-2-local-cowork-and-code-sessions). Importing the same zip again works as it does for [an added folder](#step-2-local-cowork-and-code-sessions): sessions marked as already imported are skipped, and the rest are copied. The export is a one-time snapshot, not a sync, and the zip contains full conversation content, so handle it as sensitive data.
180There are two ways to take your work to a new device. Your administrator [copies your data](https://claude.com/docs/third-party/claude-desktop/data-storage.md#move-a-user-to-a-new-device), or you export it to a zip file and import the file on the new device. Ask your administrator which way your organization uses. For an export, they must first [turn on export and import](https://claude.com/docs/third-party/claude-desktop/data-storage.md#turn-on-export-and-import). Your data stays on the old device, so keep that device until you finish the move.
179181
180The zip includes sessions, project names, and each session's output files when they total 100 MB or less. It leaves out project instructions, memory, scheduled tasks, skills, plugins, and attached files. To move those, your administrator can [copy your data to the new device](https://claude.com/docs/third-party/claude-desktop/data-storage.md#move-a-user-to-a-new-device). Sign-ins and connector connections don't move either way.
182For an export, both devices need Claude Desktop 4.23118.0 or later, the same operating system (macOS, Windows, or Linux), and the same organization. If either device runs an earlier version, update it first. Otherwise, the export moves only sessions, their output files, and project names.
181183
182## What is and isn't included
184### What a Claude Desktop export moves
183185
186**Moves:**
187
188* Chats and Cowork tasks
189* Their attached files and output files. If a session has more than 100 MB of either, those files don't move.
190* Memory, including project memory. If you paused memory on the old device, it's in the file but isn't imported.
191* Some app preferences, such as keep-awake settings and prompt suggestions
192
193**Moves, but needs a step from you:**
194
195* Projects. Accept each project's instructions on the project's page.
196* The files of each project whose folder is in the default location, `~/Claude/Projects`, if they total under 100 MB and 10,000 items. To use them in Chat, [add the folder to the project again](#make-an-imported-project-folder-readable-in-chat). Hidden files and symbolic links don't move, and some files arrive under another name, such as `CLAUDE.md.txt`.
197* Code sessions and Code scheduled tasks. [Copy and trust their folders](#import-your-data-on-the-new-device) before you import.
198* Skills you saved, plugins you uploaded, and scheduled tasks. [Turn on the ones you want](#turn-on-imported-plugins-skills-and-scheduled-tasks).
199* Local MCP servers that you added, if your organization allows them. [Enter the values of their environment variables again](#set-up-imported-local-mcp-servers).
200
201**Doesn't move:**
202
203* Other folders that your projects, Cowork tasks, and Cowork scheduled tasks use. Copy them yourself, then choose them again, or ask your administrator to [copy your data](https://claude.com/docs/third-party/claude-desktop/data-storage.md#copy-the-data-to-the-new-device).
204* The settings **Global instructions** (**Settings > Cowork**) and **Instructions for Claude** (**Settings > General**). Copy their text to the new device yourself.
205* Artifacts
206* Sign-ins, saved API keys, connectors, and tool permissions such as **Always allow** and **Blocked**
207* Desktop extensions, other plugins and marketplaces, plugin settings, other app preferences such as language, theme, and notifications, environment variables for Code sessions, and the values of environment variables for the local MCP servers that you added
208* Plugins that you uploaded in the **Code** tab on a version before 4.23118.0. Upload them again on the new device.
209* On Windows, Code sessions and Code scheduled tasks whose folder is on a mapped network drive
210* Claude Code sessions that you started in a terminal, and Claude Code's own settings and plugins
211
212### Export your data from the old device
213
214> [!WARNING]
215>
216> The zip file isn't encrypted. Anyone who opens it can read your data, including any passwords or API keys written in it. Keep the file private, and delete every copy when you no longer need it.
217
2181. Go to **Settings > Import & export** and click **Export…**.
2192. Select how far back to include sessions, then click **Export**.
2203. Choose where to save the zip file.
2214. Check the last screen, which lists what the export left out.
2225. Copy the zip file to the new device in a way that your organization allows.
223
224
225
226The export dialog, with the date range and what the export includes.
227
228If the export shows an error or leaves out something that you need, see [Problems when you move to another device](#problems-when-you-move-to-another-device).
229
230### Import your data on the new device
231
232Set up Claude Desktop on the new device first. The import adds to the data there and replaces nothing. If you import the same file again, you don't get duplicates. If you export again, a session that changed on the old device since the last export arrives as a separate session.
233
2341. If you use the **Code** tab, copy the folders of your Code sessions and Code scheduled tasks to the same paths on the new device, or to the same place under your new home folder if its path changed. Then open each folder in the **Code** tab and click **Trust workspace**.
2352. Go to **Settings > Import & export**, click **Import…**, click **Choose file…**, and select the zip file.
2363. Continue to the **Review** step and click **Import**.
2374. When Claude Desktop asks whether the file is your own export, click **Import as my own**. Click it only for a file that you made yourself. **Import sessions only** imports the sessions, and only the projects and attached files that they use.
2385. If the file has local MCP servers, a second dialog lists up to five of them with their commands. If you click **Add**, Claude Desktop tries to start all the listed servers right away, so click it only if you recognize every command. If a message then says that a server couldn't start, close it and finish the import. If you click **Don’t add**, the rest of the import continues.
2396. Note the folders that the last screen lists. If it lists **Local MCP servers not imported yet**, import the same file again.
2407. Finish the setup:
241 * Accept each project's instructions.
242 * Copy your folders, and add them again under **Context** in each project.
243 * [Turn on the plugins, skills, and scheduled tasks that you want](#turn-on-imported-plugins-skills-and-scheduled-tasks).
244 * [Set up your local MCP servers](#set-up-imported-local-mcp-servers).
245 * Reconnect your connectors.
246
247If the import shows an error, or something is missing afterward, see [Problems when you move to another device](#problems-when-you-move-to-another-device).
248
249### Turn on imported plugins, skills, and scheduled tasks
250
251Plugins, skills, and scheduled tasks from an export file are turned off, even if they were on before. The import's last screen names the ones that were on. Before you turn on a scheduled task, turn it off on the old device, or it runs on both devices.
252
253Turn on the ones you want:
254
255* **Plugins**: go to **Customize > Plugins**. Enter any keys or settings the plugin needs.
256* **Skills**: go to **Customize > Skills**
257* **Cowork scheduled tasks**: go to **Scheduled** in Cowork. If a task used folders or files, choose them again.
258* **Code scheduled tasks**: go to **Routines** in the **Code** tab
259
260### Set up imported local MCP servers
261
262The programs that the servers run don't move, and each server's command keeps the paths of the old device. Install the programs at the same paths, or change the paths in the config file. Tools that you blocked on the old device aren't blocked on the new one. To block them again, go to **Customize > Connectors**.
263
264The export leaves the values of these servers' environment variables empty. Until you enter the values, a server might not work, or might run without a limit that you set in a variable. To enter the values or change a path:
265
2661. Go to **Settings > Developer** and click **Edit config** to find the config file.
2672. Quit Claude Desktop. If you edit the file while the app is open, the app can overwrite your changes.
2683. Open the file in a text editor, make your changes, and save it. The values are in the same file on the old device.
2694. Open Claude Desktop again.
270
271## What a claude.ai import includes
272
273For an export file from another device, see [What a Claude Desktop export moves](#what-a-claude-desktop-export-moves).
274
184275* **Your data only.** An export contains your own conversations, projects, and memory. Other workspace members' content is not included.
185276* **Chats and projects come over.** Each imported project appears on the **Projects** page. If the project has custom instructions, Claude Desktop shows them in the project for you to review and accept before they take effect. In Chat, Claude can't read a folder that the import put on a project until you [add the folder to the project again](#make-an-imported-project-folder-readable-in-chat).
186277* **Artifacts come over as files.** For artifacts Claude created in a conversation, and files Claude wrote with its file-creation tool, the import saves the final version as one of the imported conversation's output files. Earlier versions aren't kept. Past a size limit, the rest of a conversation's artifact content isn't imported, and the conversation says so.
from line 279
188279* **One-time copy.** Imported history does not stay in sync with claude.ai. Run the import again to pick up newer conversations; existing imports are matched and skipped, so you won't get duplicates.
189280* **Download links expire.** The email link from claude.ai is valid for 24 hours. Request a new export if it lapses.
190281
191## Troubleshoot the import wizard
282## Troubleshoot an import or export
192283
193Claude Desktop runs each claude.ai import through the Claude CLI binary, the [helper program](https://claude.com/docs/third-party/claude-desktop/installation.md#endpoint-security-software) that also runs your conversations. Unless your organization deploys the [offline installer](https://claude.com/docs/third-party/claude-desktop/installation.md#offline-installation), Claude Desktop downloads the version of the binary it needs separately from the app, when you start a new conversation or task.
284Claude Desktop runs each claude.ai import through the Claude CLI binary, the [helper program](https://claude.com/docs/third-party/claude-desktop/installation.md#endpoint-security-software) that also runs your conversations. Unless your organization deploys the [offline installer](https://claude.com/docs/third-party/claude-desktop/installation.md#offline-installation), Claude Desktop downloads the version of the binary it needs separately from the app, when you start a new conversation or task. If this computer doesn't have that version when you click **Import**, Claude Desktop 4.23118.0 or later tries to download it first, and the wizard shows **Downloading the program that converts your chats…** while you wait.
194285
286### The import can’t start until a one-time download finishes
287
288The wizard shows this message when this computer has no version of the Claude CLI binary that can import a claude.ai export, and the download isn't finished. A running download continues after the message appears. Running the import again retries a failed download. Wait a few minutes, then run the import again.
289
290If the message comes back, ask your administrator to follow [Cowork workspace or Claude CLI fails to download](https://claude.com/docs/third-party/claude-desktop/installation.md#cowork-workspace-or-claude-cli-fails-to-download) and to leave any earlier version of the binary in place.
291
292### Import failed with a code under the message
293
294When an import fails and the wizard has no specific message for the cause, it shows a code, such as `IMPORTER_EXIT`, with **Import failed**, **Your claude.ai export didn’t import**, or **Couldn’t import this export**. If you can import only by signing in, the message asks you to sign in and fetch the export again. On Claude Desktop versions before 4.23118.0, the wizard shows no code, and if you can choose a file, it shows [That doesn’t look like a claude.ai export](#that-doesn%E2%80%99t-look-like-a-claude-ai-export) for these failures.
295
296Your export can still be valid. If you import with **Choose file…**, use each `.zip` file as you downloaded it, not renamed or compressed again. On Windows, keep each file's full path under 260 characters, for example by moving it to your Downloads folder.
297
298If you signed in to fetch the export and the wizard still shows **Import**, click it again without closing the wizard. Closing the wizard deletes the fetched export. There's a limit on how often you can fetch an export. In any other case, run the import again from **Settings > Import & export**.
299
300If the import still fails, go to **Help > Troubleshooting > Generate Diagnostic Report** before you quit Claude Desktop, and click **Export to file**. Review [what the report contains](https://claude.com/docs/third-party/claude-desktop/installation.md#troubleshooting), then send your administrator the report's `.zip` file and the code, if the wizard shows one. Your administrator can pass them to your Anthropic representative.
301
302### That doesn’t look like a claude.ai export
303
304Choose the `.zip` file of your [claude.ai export](#step-1-claude-ai-chats-and-projects) as you downloaded it. If the export came as more than one `.zip` file, choose all of them together.
305
306On Claude Desktop versions before 4.23118.0, the message can also appear after you click **Import** on the **Review** step. Your export can still be valid. Close the wizard, send any message in a new conversation or task, and wait for the reply, so the import can run on the current version of the Claude CLI binary. Closing the wizard deletes an export that you fetched by signing in, so fetch it again. Then follow the steps in [Import failed with a code under the message](#import-failed-with-a-code-under-the-message). These versions show no code.
307
195308### Importing a claude.ai export needs a newer version of this app
196309
197The wizard shows this message, under **Update Claude to import from claude.ai**, when this computer has only an earlier version of the Claude CLI binary that can't import a claude.ai export. You don't need to update or reinstall Claude Desktop. To download the current version of the binary, follow these steps:
310On Claude Desktop versions before 4.23118.0, the wizard shows this message, under **Update Claude to import from claude.ai**, when this computer has only an earlier version of the Claude CLI binary that can't import a claude.ai export. You don't need to update or reinstall Claude Desktop. To download the current version of the binary, follow these steps:
198311
199312**1. Start a new conversation or task**
200313
from line 323
210323
211324If the message is still there, ask your administrator to follow [Cowork workspace or Claude CLI fails to download](https://claude.com/docs/third-party/claude-desktop/installation.md#cowork-workspace-or-claude-cli-fails-to-download) and to leave the earlier version of the binary in place, because your conversations run on it until the download succeeds.
212325
213### That doesn’t look like a claude.ai export
326### Problems when you move to another device
214327
215If the message appears as soon as you choose a file, choose the `.zip` file of your [claude.ai export](#step-1-claude-ai-chats-and-projects) as you downloaded it. If the export came as more than one `.zip` file, choose all of them together.
328If a [move to another device](#move-your-data-to-another-device) goes wrong, find the message or the problem that you see:
216329
217If the message appears after you click **Import** on the **Review** step, your export can still be valid. Claude Desktop 4.16336.0 and earlier shows this message for other failures too. Before you run the import again from **Settings > Import & export**, do the following:
218
219* **Check the export files**: if you imported with **Choose file…**, use each `.zip` file as you downloaded it, not renamed or compressed again. On Windows, keep its full path under 260 characters, for example by moving it to your Downloads folder.
220* **Start a new conversation or task**: close the wizard, send any message, and wait for the reply, so the import can run on the current version of the Claude CLI binary.
221
222If the import still fails, go to **Help > Troubleshooting > Generate Diagnostic Report** before you quit Claude Desktop, and click **Export to file**. Review [what the report contains](https://claude.com/docs/third-party/claude-desktop/installation.md#troubleshooting), then send the report's `.zip` file to your administrator, who can pass it to your Anthropic representative.
330* **Settings > Import & export has no Export… button.** Ask your administrator to [turn on export and import](https://claude.com/docs/third-party/claude-desktop/data-storage.md#turn-on-export-and-import).
331* **This export is over the import limit of 20 GB or 5,000,000 files.** If the dialog offers **Shorten date range**, click it, select a shorter range, and click **Export**. If it doesn't, delete sessions from the last 30 days that you no longer need and export again. To move all your sessions, ask your administrator to [copy your data](https://claude.com/docs/third-party/claude-desktop/data-storage.md#copy-the-data-to-the-new-device).
332* **The export stopped before it finished, and no file was saved.** Click **Try again**. If it stops again, ask your administrator to [copy your data](https://claude.com/docs/third-party/claude-desktop/data-storage.md#copy-the-data-to-the-new-device).
333* **The export's last screen lists items that you need.** On Windows, close other programs and export again, because the export can leave out a file that another program has open. If the items are still listed, ask your administrator to [copy your data](https://claude.com/docs/third-party/claude-desktop/data-storage.md#copy-the-data-to-the-new-device).
334* **Couldn’t read that file. Choose a different zip.** On Windows, if you chose the file from a network path such as `\\server\share`, copy the file to a local folder on the new device, or choose it from a mapped network drive such as `Z:\`. Otherwise, copy the file from the old device again, or export again.
335* **That export was made in another organization. Choose an export made in this organization.** Ask your administrator to check that both devices are in the same organization.
336* **Only your sessions were imported.** Import the same file again, and click **Import as my own** when Claude Desktop asks. If it doesn't ask, update both devices to Claude Desktop 4.23118.0 or later and export again.
337* **Sessions that you imported before are missing their attached files.** An export from a version before 4.23118.0 has no attached files, and a later import doesn't add files to a session that's already there. Under **Import history** in **Settings > Import & export**, remove the earlier import, then import the new file. This also deletes the projects that the earlier import made and anything that you added to those sessions since. A session that isn't in the new file doesn't come back.
338* **A Code session or a Code scheduled task is missing.** On Windows, if its folder is on a mapped network drive, it doesn't move. Ask your administrator to [copy your data](https://claude.com/docs/third-party/claude-desktop/data-storage.md#copy-the-data-to-the-new-device), or create the task again. Otherwise, [copy its folder and trust it](#import-your-data-on-the-new-device), then import the file again. If a Code scheduled task is still missing, create it again.
223339
third-party/claude-desktop/chat Changed · +1 / -1 lines
from line 60
6060* The sandbox doesn't see project folders in a conversation that starts while a rule for `"Read"`, `"Grep"`, or `"Glob"` is set in `disabledBuiltinTools`, in `builtinToolPolicy` with a value other than `"allow"`, or as a deny or ask rule in Claude Code's own managed settings on the device.
6161* Each command runs independently; results land in the scratch directory, where Claude can offer them to the user as downloads or artifacts.
6262
63The data flow end to end: an attached file is copied into the conversation's local uploads directory, mounted read-only into the sandbox when analysis runs, and any outputs are written to the conversation's scratch directory on local disk. File content leaves the device only as conversation context sent to your configured inference provider, in web search queries to your configured search backend, through web fetches your egress allowlist permits, through [sandbox network access](#sandbox-network-access), in a connector tool call permitted by your `toolPolicy` configuration and the user's approvals, or, if you have enabled [content capture](https://claude.com/docs/third-party/claude-desktop/telemetry.md#content-capture), in telemetry to your own collector.
63The data flow end to end: an attached file is copied into the conversation's local uploads directory, mounted read-only into the sandbox when analysis runs, and any outputs are written to the conversation's scratch directory on local disk. File content leaves the device only as conversation context sent to your configured inference provider, in web search queries to your configured search backend, through web fetches your egress allowlist permits, through [sandbox network access](#sandbox-network-access), in a connector tool call permitted by your `toolPolicy` configuration and the user's approvals, in telemetry to your own collector if you have enabled [content capture](https://claude.com/docs/third-party/claude-desktop/telemetry.md#content-capture), in the zip files that users export if you have [turned on export](https://claude.com/docs/third-party/claude-desktop/data-storage.md#turn-on-export-and-import), or in any copy that you make.
6464
6565> [!NOTE]
6666>