Configuration changelog changedthird-party/claude-desktop/configuration-changelog
Nearest release: v2.1.318, published 3 hours after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 3 Nov 2026 18:29 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 3 Nov 2026 18:37 UTC.
Upstream edited
Recorded here
Lines+37added
Lines−1removed
From line
4
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits55to this page, all time
The whole hunk
from line 4, old and new numbered
/
from line 4
44
55Configuration 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).
66
7**v4.16336.0**
8
92026-11-03
10
11| MDM key | Type | Description |
12| - | - | - |
13| [`inferenceGatewayAutoModeServerChecks`](https://claude.com/docs/third-party/claude-desktop/configuration#inferencegatewayautomodeserverchecks) | `boolean` | Server-side Auto mode checks |
14| [`deploymentMode`](https://claude.com/docs/third-party/claude-desktop/configuration#deploymentmode) | `enum` | Deployment mode |
15
16**JSON (e.g. for non-MDM users or Bootstrap):**
17
18```json theme={null}
19{
20 "inference": {
21 "autoModeServerChecks": "<boolean>"
22 },
23 "authentication": {
24 "deploymentMode": "<any|3p|1p>"
25 }
26}
27```
28
29`deploymentMode` is read from device management or a local configuration file only. A value served by a bootstrap server is ignored. Setup in this version offers only `deploymentMode`, so a profile made there with `3p` still offers Claude.ai sign-in on earlier versions, which read only `disableDeploymentModeChooser`. Until all devices are updated, also set that key to `true` in the profile.
30
31**Changed:**
32
33* **Breaking:** `desktopHome`: at launches after 12:00 PM PT on November 10, 2026, an unset key reads as `standard` even where `chatSessionRetentionDays` is set. New conversations that are Cowork tasks are deleted by `coworkSessionRetentionDays`, not by `chatSessionRetentionDays`, so set both. Administrators see a configuration warning where the two differ.
34* `sessionStatusLine`: a new member, `platformOverrides`, sets a different program for `win32`, `darwin` or `linux`. Devices on a system you leave out run the setting's own program. An older version rejects the whole setting when `platformOverrides` is present and shows no status line, so add it only after all devices are updated.
35* `coworkEgressAllowedHosts`: unset no longer keeps the Code tab's shell commands off the network on a device whose only configuration is a local file, even one copied by a script, unless `blockReadsOutsideWorkingDirectories` is on. An empty list still allows no host, for shell commands where Claude Code's sandbox runs. Cowork and Chat are unchanged.
36* A setting past its deprecation date, such as `organizationPluginsUrl`, is now ignored, not a configuration error. A device profile that holds only such settings now has no effect, where it locked local settings and set aside a served configuration. If the Enterprise Admin Console delivers the device's configuration, it applies again, and its retention periods then delete idle sessions for good.
37
38**Deprecated:**
39
40* `coworkTabEnabled`, `chatTabEnabled` and `chatAdvancedFileAnalysisEnabled`: use `desktopHome`. This release and later ignore them from 12:00 PM PT on December 17, 2026, and earlier releases go on reading them. Users see an in-app warning from November 17, 2026 while one is still set. They are no longer in the policy templates.
41* `sessionRetentionHold`: this release and later ignore it from 12:00 PM PT on December 17, 2026, and retention periods then permanently delete the idle sessions it kept. To keep those sessions, first set all three retention periods to 3650 days in the configuration that sets them (with a configuration server or the Enterprise Admin Console, set them there, not in the device profile), wait until devices have the new periods, then remove the key. Users see no warning in the app. The key is no longer in the configuration reference or the policy templates, so a device profile rebuilt from the new templates drops it: set the periods first.
42
743**v4.4212.0**
844
9452026-10-29
from line 542
506542| [`chatSessionRetentionDays`](https://claude.com/docs/third-party/claude-desktop/configuration#chatsessionretentiondays) | `integer` | Chat retention period |
507543| [`coworkSessionRetentionDays`](https://claude.com/docs/third-party/claude-desktop/configuration#coworksessionretentiondays) | `integer` | Cowork retention period |
508544| [`codeSessionRetentionDays`](https://claude.com/docs/third-party/claude-desktop/configuration#codesessionretentiondays) | `integer` | Code retention period |
509| [`sessionRetentionHold`](https://claude.com/docs/third-party/claude-desktop/configuration#sessionretentionhold) | `boolean` | Suspend session deletion |
545| `sessionRetentionHold` | `boolean` | Suspend session deletion |
510546| [`coworkVmIpv6Enabled`](https://claude.com/docs/third-party/claude-desktop/configuration#coworkvmipv6enabled) | `boolean` | Enable IPv6 in the workspace VM |
511547
512548**JSON (e.g. for non-MDM users or Bootstrap):**
No line in this hunk matches that.