Installation and setup changedthird-party/claude-desktop/installation
Nearest release: v2.1.305, published 2 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 20 Oct 2026 17: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 20 Oct 2026 17:37 UTC.
Upstream edited
Recorded here
Lines+13added
Lines−0removed
From line
209
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits22to this page, all time
The whole hunk
from line 209, old and new numbered
/
from line 209
209209In 3P deployments you can:
210210
211211* **Leave auto-update enabled** (recommended) so fixes reach users without IT intervention. Set `autoUpdaterEnforcementHours` to shorten the enforcement window (1 to 72 hours; values above 72 are rejected). Setting the key also makes the window strict: the restart fires as soon as the window elapses, without waiting for a pause in user activity.
212* **Take releases later** by setting [`releaseChannel`](/docs/third-party/claude-desktop/configuration#releasechannel) to `staggered`, the slower channel. Devices on the default, `stable`, take each release as it rolls out. Devices on `staggered` update to the release that Anthropic has marked for that channel. On Thursdays, Anthropic marks a release that has fully rolled out on `stable`, a tested production build from at least one week prior. A device on a release newer than the marked one stays on it until Anthropic marks a release newer than its own. Features and fixes, including security fixes, reach `staggered` devices later.
212213* **Disable auto-update** (`disableAutoUpdates`) and redistribute new builds through your MDM on your own cadence. This is required for [air-gapped environments](#offline-installation) but means your IT team owns the update pipeline.
214
215<Warning>
216 Moving a device from `staggered` to `stable` updates it to a newer release, and setting `staggered` again doesn't take it back to the older one. A device also follows `stable` if you remove `releaseChannel` or set it only where the device doesn't read it.
217</Warning>
218
219Set `releaseChannel` in the first of these that the device has:
220
221* **An MDM profile that sets only [app-behavior keys](/docs/third-party/claude-desktop/mdm#update-keys-and-managed-precedence)**, such as an update policy, a restart window, or a network proxy: put the key in that profile
222* **A [bootstrap server](/docs/third-party/claude-desktop/bootstrap) or the [admin console](/docs/third-party/claude-desktop/admin-console)**: return the key in the server's response, or set it in the console
223* **Any other configuration**, such as an MDM profile that sets the inference provider: put the key with the rest of that configuration
224
225`releaseChannel` has no effect on devices where something else installs updates, such as Linux devices, which [update through apt](/docs/third-party/claude-desktop/telemetry#auto-updates), and devices that installed Claude Desktop from the Microsoft Store.
213226
214227See [Telemetry and egress](/docs/third-party/claude-desktop/telemetry) for the network paths the updater uses.
215228
No line in this hunk matches that.