{"version":"2.1.300","anchor":"self-hosted-desktop-settings-retired-and-refused-by-gateway","canonical_anchor":"self-hosted-desktop-settings-retired-and-refused-by-gateway","heading":"Gateways refuse self-hosted Claude Desktop session settings","tier":"notice","area":"Managed Settings","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/self-hosted-desktop-settings-retired-and-refused-by-gateway","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Gateways refuse self-hosted Claude Desktop session settings\n\n`deviceToolsEnabled` and the `selfHosted` credential keys are retired, and gateways now reject settings that run Desktop sessions off the device\n\n**What**\n\nThis applies to organizations that run Claude Desktop through their own gateway, a server that hands out managed configuration. Several settings change:\n\n- `deviceToolsEnabled` is retired\n\n- the `selfHosted` credential keys are retired and point to the `inference` keys instead\n\n- the gateway rejects any setting meant to run Claude Desktop sessions somewhere other than the device, with an error beginning \"this gateway does not serve settings that run Claude Desktop sessions off the device\"\n\n- unknown keys starting with `selfhosted` are skipped at start-up\n\nThe sign-in for the session host stays in the operating system's secure storage.\n\n**Why**\n\nAdministrators of these gateway setups who still set the retired keys now get a hard error instead of having them accepted, and should move to the `inference` keys.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: yes"}