Deploy with MDM changedthird-party/claude-desktop/mdm
Nearest release: v2.1.315, 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 30 Oct 2026 17:36 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 30 Oct 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+24added
Lines−24removed
From line
99
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits30to this page, all time
The whole hunk
from line 99, old and new numbered
/
from line 99
9999
100100Push the exported configuration through your MDM. The app reads from these locations:
101101
102**macOS**
103
104| Source | Path | Precedence |
105| - | - | - |
106| Managed (per-user) | `/Library/Managed Preferences/<user>/com.anthropic.claudefordesktop.plist` | Highest |
107| Managed (machine) | `/Library/Managed Preferences/com.anthropic.claudefordesktop.plist` | |
108| Local (user) | `~/Library/Application Support/Claude-3p/configLibrary/` | Lowest |
109
110A `.mobileconfig` profile delivered by MDM lands in the Managed Preferences locations automatically. Both managed paths are read; where a key appears in both, the per-user value wins.
111
112**Windows**
113
114| Source | Path | Precedence |
115| - | - | - |
116| Machine policy | `HKLM\SOFTWARE\Policies\Claude` | Highest |
117| User policy | `HKCU\SOFTWARE\Policies\Claude` | |
118| Local (user) | `%LOCALAPPDATA%\Claude-3p\configLibrary\` | Lowest |
119
120A Group Policy Object or Intune configuration profile writes to the registry policy paths. The hives are not merged: when machine policy is present (any `REG_SZ`, `REG_EXPAND_SZ`, or `REG_DWORD` value directly under `HKLM\SOFTWARE\Policies\Claude`, including an empty string, and the key's unnamed default value when set), the app ignores `HKCU\SOFTWARE\Policies\Claude` entirely. Deploy the complete configuration to one hive; machine policy (`HKLM`) is the recommended location.
121
122> [!WARNING]
102> [tab] macOS
123103>
124> Values must sit directly under `HKLM\SOFTWARE\Policies\Claude` or `HKCU\SOFTWARE\Policies\Claude`. The app never reads values nested in a subkey, as some ADMX-based and Policy CSP tooling writes them: they do not apply as configuration and do not count as machine policy being present. Write values as `REG_SZ` (`REG_DWORD` is also accepted for boolean and integer keys and is read as its decimal value). Avoid `REG_EXPAND_SZ`: the app counts it as machine policy being present but cannot read its contents, so a single `REG_EXPAND_SZ` value under `HKLM` disables user policy without supplying any configuration. The app cannot see `REG_QWORD`, `REG_MULTI_SZ`, or `REG_BINARY` values at all.
104> | Source | Path | Precedence |
105> | - | - | - |
106> | Managed (per-user) | `/Library/Managed Preferences/<user>/com.anthropic.claudefordesktop.plist` | Highest |
107> | Managed (machine) | `/Library/Managed Preferences/com.anthropic.claudefordesktop.plist` | |
108> | Local (user) | `~/Library/Application Support/Claude-3p/configLibrary/` | Lowest |
109>
110> A `.mobileconfig` profile delivered by MDM lands in the Managed Preferences locations automatically. Both managed paths are read; where a key appears in both, the per-user value wins.
125111
126> [!NOTE]
112> [tab] Windows
127113>
128> In releases before v1.19367.0, the app read both hives and merged them key by key, with the `HKLM` value winning where a key appeared in both. Fleets that split keys across both hives must consolidate the full configuration into one hive before updating to v1.19367.0 or later.
114> | Source | Path | Precedence |
115> | - | - | - |
116> | Machine policy | `HKLM\SOFTWARE\Policies\Claude` | Highest |
117> | User policy | `HKCU\SOFTWARE\Policies\Claude` | |
118> | Local (user) | `%LOCALAPPDATA%\Claude-3p\configLibrary\` | Lowest |
119>
120> A Group Policy Object or Intune configuration profile writes to the registry policy paths. The hives are not merged: when machine policy is present (any `REG_SZ`, `REG_EXPAND_SZ`, or `REG_DWORD` value directly under `HKLM\SOFTWARE\Policies\Claude`, including an empty string, and the key's unnamed default value when set), the app ignores `HKCU\SOFTWARE\Policies\Claude` entirely. Deploy the complete configuration to one hive; machine policy (`HKLM`) is the recommended location.
121>
122> > [!WARNING]
123> >
124> > Values must sit directly under `HKLM\SOFTWARE\Policies\Claude` or `HKCU\SOFTWARE\Policies\Claude`. The app never reads values nested in a subkey, as some ADMX-based and Policy CSP tooling writes them: they do not apply as configuration and do not count as machine policy being present. Write values as `REG_SZ` (`REG_DWORD` is also accepted for boolean and integer keys and is read as its decimal value). Avoid `REG_EXPAND_SZ`: the app counts it as machine policy being present but cannot read its contents, so a single `REG_EXPAND_SZ` value under `HKLM` disables user policy without supplying any configuration. The app cannot see `REG_QWORD`, `REG_MULTI_SZ`, or `REG_BINARY` values at all.
125>
126> > [!NOTE]
127> >
128> > In releases before v1.19367.0, the app read both hives and merged them key by key, with the `HKLM` value winning where a key appeared in both. Fleets that split keys across both hives must consolidate the full configuration into one hive before updating to v1.19367.0 or later.
129129
130130When a managed source sets any key other than the [app-behavior keys](#update-keys-and-managed-precedence) listed below, the managed configuration takes effect, the in-app configuration window becomes read-only, and locally authored values in `configLibrary/` are ignored.
131131
No line in this hunk matches that.