One read of Claude Documentation
5 pages moved out of 214 read.
cowork/changelog Changed · +35 / -1 lines
> Release notes for Claude Desktop +<Update label="v1.32885.1" description="2026-08-18"> + **General** + + * Added message queueing during Research: a message sent while a Research run is in progress is queued and sent when the report is ready. + * Fixed 1Password credential requests failing when Claude in Chrome is signed in from more than one browser profile. + * Fixed a crash on Windows when installing an update while a background update check was still running, and fixed update installs repeatedly failing after a newer update replaced one already staged. + * Fixed a message sent immediately after stopping a reply sometimes being put back into the input box instead of sending. + * Fixed reloading or reopening a temporary chat rebuilding the page a moment after it loads, which could discard text typed early. + * Fixed the computer-use permission prompts in Cowork and Claude Code sessions accepting a keyboard shortcut aimed at the message box or another surface, and added a brief delay so a send keystroke that lands just as the prompt appears cannot approve it. + + **Code** + + * Fixed automatic continuation after a rate limit firing into the imported-session confirmation prompt or a stale sign-in state, and it now waits out the server's limit reset and sends a clearer continuation message. + * Fixed inline bash commands being silently captured as input by a previous command still waiting for a response, such as an interactive login; a stuck command is now noted in the transcript and cleared before the next command runs. + * Fixed messages sent from one session to another sometimes being silently dropped, which left the sending session showing a thinking state for many minutes. + * Fixed slow session starts for people with MCP servers configured in `~/.claude.json`. + * Fixed the Code tab wrongly asking you to install Git on Macs that have Apple's Command Line Tools but not Xcode. + * Fixed worktree sessions failing with a "path contains control characters" error when a `WorktreeCreate` hook prints status output before the path. + + **Cowork** + + * Fixed an occasional "Something went wrong" error when a session's question card from Claude changed to a new set of questions. + * Fixed Claude sometimes reporting a file as saved when it had been written to a temporary location you could not open. + * Fixed Cowork failing to start on Intel Macs. + + **3P** + + * Added `bootstrapHeaders` and `bootstrapHeadersHelper` for authenticating the bootstrap configuration fetch with a service-account credential, the supported replacement for embedding `user:password@` in `bootstrapUrl` (rejected since 1.32352.0): `bootstrapHeaders` is a set of static headers sent on every fetch, and `bootstrapHeadersHelper` is the absolute path of an executable that prints headers as JSON, for a rotating token; helper output is merged over the static headers. When either is set and no `bootstrapOidc` provider is configured, the headers count as sufficient authentication for the fetch and no per-user sign-in is required for it; a per-user sign-in bearer, when also present, still wins on `Authorization`. Header values are masked in diagnostics, and both keys are accepted only from device management or a local configuration file. + * Added the option to sign in to claude.ai directly from the import wizard to fetch your data export, with no manual zip download needed. + * Changed new Cowork sessions to store Claude Code transcripts under a short fixed folder name, now that the bundled Claude Code (2.1.234) supports it, further shortening file paths on Windows; existing sessions are unchanged. + * Changed organization plugin delivery: when the organization plugins endpoint is removed from your configuration, the plugins it had installed are removed from members' devices, as already happens for a removed plugin marketplace. + * Fixed admin-configured plugin marketplaces and organization plugins not re-syncing until the next periodic refresh after signing in or after a delayed configuration fetch applied. +</Update> + <Update label="v1.32352.1" description="2026-08-18"> **General**
**3P** - * **Breaking:** Managed-config URL settings now reject values that embed credentials (`https://user:password@host…`). Configurations that relied on this fail to load until the credentials are removed; use `bootstrapHeaders` / `bootstrapHeadersHelper` (arriving in an upcoming release) to send authentication instead. + * **Breaking:** Managed-config URL settings now reject values that embed credentials (`https://user:password@host…`). Configurations that relied on this fail to load until the credentials are removed; use `bootstrapHeaders` / `bootstrapHeadersHelper` (available from 1.32885.1) to send authentication instead. * Added `claudeAiImport.exportEnabled`. With it and `claudeAiImport.enabled` both `true`, users can export this computer's chats, Cowork tasks, and Code sessions from Settings > Import & export as a zip that another install can import. Off by default. * Added a `url` source for `allowedPluginMarketplaces` (beta): a hosted `marketplace.json` that delivers plugins as zip archives over HTTPS, with no git on the device. Set `manifestSha256` to pin the exact manifest; it is required for automatically installed plugins. * Added `inferenceCredential` as a `credentialKind` for `allowedPluginMarketplaces` (beta): a `url` marketplace hosted on your inference gateway is fetched with the same credential the app already uses for inference.
third-party/claude-desktop/bootstrap Changed · +10 / -0 lines
| <span id="bootstrapenabled" />Use bootstrap config<br />`bootstrapEnabled` | `boolean` | MDM only | `true` | Fetch and apply the URL above at launch. Turn off to keep the URL saved but skip the fetch. Defaults to `true`. | | <span id="bootstrapurl" />Bootstrap config URL<br />`bootstrapUrl` | `string` | MDM only | — | HTTPS endpoint that returns a per-user JSON config overlay. Values from the response override local settings and become read-only. | | <span id="bootstrapoidc" />Bootstrap OIDC parameters<br />`bootstrapOidc` | `object` | MDM only | — | When set, the bootstrap request sends a Bearer token from a browser sign-in (authorization-code-with-PKCE). | +| <span id="bootstrapheaders" />Bootstrap request headers<br />`bootstrapHeaders` | `object` | MDM only | — | HTTP headers sent on every bootstrap config fetch. Use this instead of embedding user:pass@ in the URL. | +| <span id="bootstrapheadershelper" />Bootstrap headers helper script<br />`bootstrapHeadersHelper` | `string` | MDM only | — | Absolute path to an executable that prints a JSON object of bootstrap request headers. Merged over the static headers; the helper wins. | | <span id="trustbootstrapdelivery" />Trust bootstrap-delivered settings<br />`trustBootstrapDelivery` | `boolean` | MDM only | `false` | Skip the per-user consent prompt for sign-in targets, inference endpoints, helper scripts, and connectors the bootstrap server delivers. Defaults to `false`. Previously named `trustBootstrapLocalExec`. | <AccordionGroup>
| `scopes` | `string` | — | Space-separated; the token’s audience must match what your bootstrap server validates. | | `redirectPort` | `integer` | — | Fixed loopback port for the sign-in redirect ([http://127.0.0.1:PORT/callback](http://127.0.0.1:PORT/callback)). Leave unset to use a free port each time. | | `additionalRedirectReferrerHosts` | `string` | — | Space-separated hostnames also accepted as the referrer of the sign-in callback. Only needed when the IdP completes sign-in from a different host. | + </Accordion> + + <Accordion title="bootstrapHeaders details"> + Static headers sent on every request to the bootstrap config URL — for a service-account credential (`Authorization: Basic …`, an API key header) or a routing/tenant header. When either this or the headers helper script is set and no separate `bootstrapOidc` provider is configured, the app treats the headers as sufficient auth and does not require a per-user sign-in for the bootstrap fetch. Header values are masked in diagnostics and telemetry. For a rotating token, use the headers helper script instead. + </Accordion> + + <Accordion title="bootstrapHeadersHelper details"> + Absolute path to an executable that prints a single JSON object of HTTP headers on stdout, e.g. `{"Authorization": "Bearer …"}`. The app runs it (no arguments; output cached for a few minutes) before each bootstrap config fetch and merges the result over **Bootstrap request headers** (the helper wins on conflict). Use this instead of embedding `user:pass@` in the bootstrap URL, or when the bootstrap server needs a rotating token from a secrets manager. When either this or the static headers are set and no separate `bootstrapOidc` provider is configured, the app treats them as sufficient auth and does not require a per-user sign-in for the bootstrap fetch. If a per-user sign-in also runs (`bootstrapOidc` or the server’s own device-code flow), that Bearer token wins on `Authorization`. </Accordion> </AccordionGroup>
third-party/claude-desktop/configuration Changed · +11 / -1 lines
| `readOnly` | `boolean` | — | Offer only read tools — the server registers no write tools at all. | | `transport` | `enum` | — | How the app connects: Streamable HTTP or legacy SSE for remote servers, or a local command over stdio. One of: `http`, `sse`, `stdio`. | | `url` | `string` | — | HTTPS endpoint of the remote MCP server. | - | `oauth` | `object` | — | OAuth settings for a remote server: true to auto-register a client, or an object with a pre-registered client ID, tenant, and scope. | + | `oauth` | `object` | — | OAuth for a remote server: true to auto-register a client, a pre-registered client ID with tenant and scope, or mode “hosted” for an Anthropic-signed identity. | | `oauth.clientId` | `string` | — | OAuth client ID from your IdP app registration. Leave unset to auto-register (dynamic client registration) and only narrow scopes. | | `oauth.clientSecret` | `string` | — | Only for IdPs whose token endpoint requires a client secret (e.g. Box). Leave blank for PKCE-only public clients. | | `oauth.clientSecretHelper` | `string` | — | Executable that prints the client secret on stdout. Overrides the inline value. |
| <span id="bootstrapenabled" />Use bootstrap config<br />`bootstrapEnabled` | `boolean` | MDM only | `true` | Fetch and apply the URL above at launch. Turn off to keep the URL saved but skip the fetch. Defaults to `true`. | | <span id="bootstrapurl" />Bootstrap config URL<br />`bootstrapUrl` | `string` | MDM only | — | HTTPS endpoint that returns a per-user JSON config overlay. Values from the response override local settings and become read-only. | | <span id="bootstrapoidc" />Bootstrap OIDC parameters<br />`bootstrapOidc` | `object` | MDM only | — | When set, the bootstrap request sends a Bearer token from a browser sign-in (authorization-code-with-PKCE). | +| <span id="bootstrapheaders" />Bootstrap request headers<br />`bootstrapHeaders` | `object` | MDM only | — | HTTP headers sent on every bootstrap config fetch. Use this instead of embedding user:pass@ in the URL. | +| <span id="bootstrapheadershelper" />Bootstrap headers helper script<br />`bootstrapHeadersHelper` | `string` | MDM only | — | Absolute path to an executable that prints a JSON object of bootstrap request headers. Merged over the static headers; the helper wins. | | <span id="trustbootstrapdelivery" />Trust bootstrap-delivered settings<br />`trustBootstrapDelivery` | `boolean` | MDM only | `false` | Skip the per-user consent prompt for sign-in targets, inference endpoints, helper scripts, and connectors the bootstrap server delivers. Defaults to `false`. Previously named `trustBootstrapLocalExec`. | <AccordionGroup>
| `scopes` | `string` | — | Space-separated; the token’s audience must match what your bootstrap server validates. | | `redirectPort` | `integer` | — | Fixed loopback port for the sign-in redirect ([http://127.0.0.1:PORT/callback](http://127.0.0.1:PORT/callback)). Leave unset to use a free port each time. | | `additionalRedirectReferrerHosts` | `string` | — | Space-separated hostnames also accepted as the referrer of the sign-in callback. Only needed when the IdP completes sign-in from a different host. | + </Accordion> + + <Accordion title="bootstrapHeaders details"> + Static headers sent on every request to the bootstrap config URL — for a service-account credential (`Authorization: Basic …`, an API key header) or a routing/tenant header. When either this or the headers helper script is set and no separate `bootstrapOidc` provider is configured, the app treats the headers as sufficient auth and does not require a per-user sign-in for the bootstrap fetch. Header values are masked in diagnostics and telemetry. For a rotating token, use the headers helper script instead. + </Accordion> + + <Accordion title="bootstrapHeadersHelper details"> + Absolute path to an executable that prints a single JSON object of HTTP headers on stdout, e.g. `{"Authorization": "Bearer …"}`. The app runs it (no arguments; output cached for a few minutes) before each bootstrap config fetch and merges the result over **Bootstrap request headers** (the helper wins on conflict). Use this instead of embedding `user:pass@` in the bootstrap URL, or when the bootstrap server needs a rotating token from a secrets manager. When either this or the static headers are set and no separate `bootstrapOidc` provider is configured, the app treats them as sufficient auth and does not require a per-user sign-in for the bootstrap fetch. If a per-user sign-in also runs (`bootstrapOidc` or the server’s own device-code flow), that Bearer token wins on `Authorization`. </Accordion> </AccordionGroup>
third-party/claude-desktop/configuration-changelog Changed · +25 / -1 lines
Configuration keys by Claude Desktop release. Each section lists keys added in that release, with the MDM key name (for plist/registry deployment) and the equivalent JSON shape (for local-file or bootstrap remote configuration). +<Update label="v1.32885.1" description="2026-08-18"> + <div className="cfg-keys"> + | MDM key | Type | Description | + | -------------------------------------------------------------------------------------------- | -------- | ------------------------------- | + | [`bootstrapHeaders`](/docs/third-party/claude-desktop/configuration#bootstrapheaders) | `object` | Bootstrap request headers | + | [`bootstrapHeadersHelper`](/docs/third-party/claude-desktop/configuration#bootstrapheadershelper) | `string` | Bootstrap headers helper script | + </div> + + **JSON (e.g. for non-MDM users or Bootstrap):** + + ```json theme={null} + { + "bootstrap": { + "headers": "<object>", + "headersHelper": "<string>" + } + } + ``` + + **Changed:** + + * `managedMcpServers[].oauth` accepts a new `mode` value, `hosted`: the app signs in to that MCP server with an Anthropic-hosted client identity (Anthropic vouches for the client on each token request) instead of a client you register yourself, pinned to the exact issuer URL(s) you list in `authorizationServer`; it requires the Claude.ai sign-in and is available once the hosted signer is enabled for your organization. +</Update> + <Update label="v1.32352.1" description="2026-08-18"> No configuration changes in this release. </Update>
**Changed:** - * **Breaking:** Managed-config URL settings now reject values that embed credentials (`https://user:password@host…`). Configurations that relied on this fail to load until the credentials are removed; use `bootstrapHeaders` / `bootstrapHeadersHelper` (arriving in an upcoming release) to send authentication instead. + * **Breaking:** Managed-config URL settings now reject values that embed credentials (`https://user:password@host…`). Configurations that relied on this fail to load until the credentials are removed; use `bootstrapHeaders` / `bootstrapHeadersHelper` (available from 1.32885.1) to send authentication instead. * `allowedPluginMarketplaces[].source` (beta) accepts a new `url` value: a hosted `marketplace.json` whose plugins are zip archives, fetched over HTTPS with no git on the device; set `url` to the manifest address (`repo`, `ref`, and `path` do not apply). * `allowedPluginMarketplaces[].credentialKind` (beta) accepts a new `inferenceCredential` value, for `url` marketplaces on the inference gateway's own origin: fetches carry the same bearer credential the app already sends the gateway for inference. </Update>
third-party/claude-desktop/import New page · 115 lines, new page
# Import history from claude.ai ## Before you start ## Enable member data export (admins) ## Open the import wizard ## Step 1: claude.ai chats and projects ## Step 2: local Cowork and Code sessions ## Step 3: review and import ## Continue an imported conversation ## What is and isn't included
A whole new page. There's nothing to diff it against, so here is what it says.
# Import history from claude.ai
> Bring conversations, projects, and local Cowork and Code sessions into Claude Desktop on 3P from a claude.ai workspace or an earlier install
Import 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](/docs/third-party/claude-desktop/data-storage), so you can pick up work you started on claude.ai and continue it against your organization's own inference provider.
Each 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 re-running the import does not create duplicates.
## Before you start
* Claude Desktop is installed and running in third-party mode. See [Installation and setup](/docs/third-party/claude-desktop/installation).
* To bring history over from a claude.ai Team or Enterprise workspace, an owner of that workspace has enabled member data export (next section). Personal claude.ai accounts can always export.
## Enable member data export (admins)
On Team and Enterprise workspaces, member data export is off by default. A workspace owner enables it on claude.ai under **Settings → Organization → Data and privacy → Allow members to export their own data**.
<Frame caption="The member data export toggle in claude.ai organization settings. Only workspace owners see this control.">
<img src="https://mintcdn.com/claude-ai/HpR2FaaZXZXkiUcV/images/third-party/import/import-admin-toggle.png?fit=max&auto=format&n=HpR2FaaZXZXkiUcV&q=85&s=f1f4696a2124cd36ee9a7366cb1c4772" alt="claude.ai organization settings, Data and privacy page, with the Allow members to export their own data toggle turned on and a confirmation toast reading Member data export enabled." width="1800" height="1125" data-path="images/third-party/import/import-admin-toggle.png" />
</Frame>
Members of the workspace can then export their own conversations. The toggle does not expose one member's data to another; each member can download only their own history.
## Open the import wizard
In Claude Desktop, go to **Settings → Import & export** and click **Import…** to open the **Import from Claude** wizard.
<Frame caption="Step 1 of the import wizard, before a source is chosen.">
<img src="https://mintcdn.com/claude-ai/HpR2FaaZXZXkiUcV/images/third-party/import/import-wizard-start.png?fit=max&auto=format&n=HpR2FaaZXZXkiUcV&q=85&s=526562f1c9c0abd66e9b56d0328808db" alt="Claude Desktop settings with Import and export selected and the Import from Claude wizard open on step 1, showing Sign in to claude.ai and Choose file buttons." width="1920" height="1440" data-path="images/third-party/import/import-wizard-start.png" />
</Frame>
The wizard has three steps: **Chats** (your claude.ai export), **Cowork & Code** (local sessions on this machine), and **Review**. Skip any step you don't need.
## Step 1: claude.ai chats and projects
You can pull your claude.ai history straight into the wizard by signing in, or download it from claude.ai yourself and choose the file.
<Tabs>
<Tab title="Sign in to claude.ai (recommended)">
Click **Sign in to claude.ai…**. Your browser opens to claude.ai; sign in if prompted, choose your organization if you belong to more than one, and click **Authorize**.
<Frame caption="The organization selector, shown if your claude.ai account belongs to more than one workspace.">
<img src="https://mintcdn.com/claude-ai/HpR2FaaZXZXkiUcV/images/third-party/import/import-consent-org.png?fit=max&auto=format&n=HpR2FaaZXZXkiUcV&q=85&s=1657a03028a7ceb3d173e71ba27f591d" alt="claude.ai organization selector titled Select organization, listing one organization." width="1600" height="720" data-path="images/third-party/import/import-consent-org.png" />
</Frame>
<Frame caption="The authorization prompt. The only permission granted is a one-time export of your own data.">
<img src="https://mintcdn.com/claude-ai/HpR2FaaZXZXkiUcV/images/third-party/import/import-consent-authorize.png?fit=max&auto=format&n=HpR2FaaZXZXkiUcV&q=85&s=55be3501d41c9e61b49154db66b71d5b" alt="claude.ai authorization card reading Claude Desktop Import would like to connect to your Claude chat account, with an Authorize button." width="1400" height="1300" data-path="images/third-party/import/import-consent-authorize.png" />
</Frame>
Back in Claude Desktop, click **Fetch export**. The wizard requests an export from claude.ai, downloads it, and shows what it found.
<Frame caption="The wizard after the export finishes downloading.">
<img src="https://mintcdn.com/claude-ai/HpR2FaaZXZXkiUcV/images/third-party/import/import-signed-in.png?fit=max&auto=format&n=HpR2FaaZXZXkiUcV&q=85&s=dafc4cbfffd685321442cbd72fd73993" alt="Import from Claude wizard step 1 showing a claude.ai export row with the account email and a summary of 7 chats and 1 project." width="1920" height="1440" data-path="images/third-party/import/import-signed-in.png" />
</Frame>
</Tab>
<Tab title="Choose a downloaded file">
On claude.ai, go to **Settings → Privacy → Export data** and click **Export**. If you don't see **Export data**, ask a workspace owner to [enable member data export](#enable-member-data-export-admins).
<Frame caption="The Export data page in claude.ai personal settings.">
<img src="https://mintcdn.com/claude-ai/HpR2FaaZXZXkiUcV/images/third-party/import/import-web-export.png?fit=max&auto=format&n=HpR2FaaZXZXkiUcV&q=85&s=1ed4aa5a08469420020d3ff83579c0de" alt="claude.ai settings Privacy page with the Export data subpage open, showing an Export button and a note that a download link will be sent by email." width="1800" height="1125" data-path="images/third-party/import/import-web-export.png" />
</Frame>
claude.ai emails you a download link when the export is ready. The link expires after 24 hours.
<Frame caption="The export-ready email.">
<img src="https://mintcdn.com/claude-ai/HpR2FaaZXZXkiUcV/images/third-party/import/import-email.png?fit=max&auto=format&n=HpR2FaaZXZXkiUcV&q=85&s=cf883e9c401401686568c77cb6ac45c1" alt="Email from Claude titled Your data is ready for download with a Download data button." width="1800" height="1125" data-path="images/third-party/import/import-email.png" />
</Frame>
Download the `.zip`, then in the import wizard click **Choose file…** and select it.
<Frame caption="Step 1 with a downloaded export selected.">
<img src="https://mintcdn.com/claude-ai/HpR2FaaZXZXkiUcV/images/third-party/import/import-choose-file.png?fit=max&auto=format&n=HpR2FaaZXZXkiUcV&q=85&s=5cb868969ebed88801296f696796d0f1" alt="Import from Claude wizard step 1 showing a selected member-data zip file with a summary of 7 chats and 1 project." width="1920" height="1440" data-path="images/third-party/import/import-choose-file.png" />
</Frame>
</Tab>
</Tabs>
Click **Continue**, or **Skip this step** if you only want to bring in local sessions.
## Step 2: local Cowork and Code sessions
The wizard scans this machine for Cowork and Claude Code sessions from an earlier Claude Desktop install and lists what it finds. Choose how far back to include, and add any other folder that holds sessions (for example, a backup or a folder copied from another machine).
<Frame caption="Local sessions found on this machine.">
<img src="https://mintcdn.com/claude-ai/HpR2FaaZXZXkiUcV/images/third-party/import/import-local-sessions.png?fit=max&auto=format&n=HpR2FaaZXZXkiUcV&q=85&s=e17511922a814b0355cb540688a5c949" alt="Import from Claude wizard step 2, Cowork and Code, listing 5 local sessions with a time-range selector and an option to add another location." width="1920" height="1440" data-path="images/third-party/import/import-local-sessions.png" />
</Frame>
Sessions are copied, not moved. Your original history stays where it is.
## Step 3: review and import
The **Review** step summarizes what will be added. Click **Import** to copy everything into your local session store.
<Frame caption="The review summary before import.">
<img src="https://mintcdn.com/claude-ai/HpR2FaaZXZXkiUcV/images/third-party/import/import-review.png?fit=max&auto=format&n=HpR2FaaZXZXkiUcV&q=85&s=c7939485c7185afbf1ef7518a94db2d6" alt="Import from Claude wizard step 3 showing a claude.ai export summary of 7 chats and 1 project alongside 5 local Cowork and Code sessions, with an Import button." width="1920" height="1440" data-path="images/third-party/import/import-review.png" />
</Frame>
<Frame caption="Import complete. Imported chats appear in the sidebar and imported projects appear as Spaces.">
<img src="https://mintcdn.com/claude-ai/HpR2FaaZXZXkiUcV/images/third-party/import/import-success.png?fit=max&auto=format&n=HpR2FaaZXZXkiUcV&q=85&s=c878c70886ff9a0fd2b3d046bf916375" alt="Import from Claude wizard success screen reading Imported 12 sessions and 1 Space, with a note that re-running import will not create duplicates." width="1920" height="1440" data-path="images/third-party/import/import-success.png" />
</Frame>
## Continue an imported conversation
Open any imported conversation from the sidebar and keep chatting. The first time you send a message in an imported session, Claude Desktop shows a **Resume imported session?** prompt. Click **Trust and resume** to continue; the reply comes from your configured inference provider, not from claude.ai.
<Frame caption="The trust prompt shown the first time you resume an imported session.">
<img src="https://mintcdn.com/claude-ai/HpR2FaaZXZXkiUcV/images/third-party/import/import-trust-resume.png?fit=max&auto=format&n=HpR2FaaZXZXkiUcV&q=85&s=806d0d2018d7fc0f10afb71035b1f807" alt="An imported conversation open in Cowork with a yellow Resume imported session card offering Go back and Trust and resume buttons." width="1800" height="688" data-path="images/third-party/import/import-trust-resume.png" />
</Frame>
## What is and isn't included
* **Your data only.** An export contains your own conversations, projects, and memory. Other workspace members' content is not included.
* **Attachment bytes are not fetched over sign-in.** When you use **Sign in to claude.ai**, the export contains chats and projects only. To include the files you uploaded to conversations, use the **Choose a downloaded file** path instead.
* **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.
* **Download links expire.** The email link from claude.ai is valid for 24 hours. Request a new export if it lapses.