Configuration implementation changedthird-party/claude-desktop/configuration-format
Nearest release: v2.1.319, published 20 hours before 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 6 Nov 2026 21:13 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 6 Nov 2026 21:37 UTC.
Upstream edited
Recorded here
Lines+1added
Lines−1removed
From line
60
where the diff opens
First seen
22 Oct 2026
this site's first read of the page
Recorded edits10to this page, all time
The whole hunk
from line 60, old and new numbered
/
from line 60
6060
6161### Value types in a profile or registry policy
6262
63Write every value as a **string** in the OS preference store, even booleans and arrays. This rule applies to plist and registry sources. [The Linux file](#the-linux-configuration-file) and a [bootstrap response](https://claude.com/docs/third-party/claude-desktop/bootstrap.md#response-schema) take JSON values. Each key's entry in the [configuration reference](https://claude.com/docs/third-party/claude-desktop/configuration.md) gives the key's type and the values or fields it accepts.
63In a plist or registry source, every value can be a **string**, even booleans and arrays. The app also reads a native boolean or integer (`<true/>`, `<false/>`, or `<integer>` in a profile, `REG_DWORD` in the registry), which is what its own export writes. [The Linux file](#the-linux-configuration-file) and a [bootstrap response](https://claude.com/docs/third-party/claude-desktop/bootstrap.md#response-schema) take JSON values. Each key's entry in the [configuration reference](https://claude.com/docs/third-party/claude-desktop/configuration.md) gives the key's type and the values or fields it accepts.
6464
6565| Documented type | What to write | Example |
6666| - | - | - |
No line in this hunk matches that.