{"version":"2.1.319","anchor":"coworkdesktophome-settings-deprecation-warnings-dated-nov-1","canonical_anchor":"coworkdesktophome-settings-deprecation-warnings-dated-nov-1","heading":"Managed policies warn when desktopHome is not set","tier":"notice","area":"Cowork","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/coworkdesktophome-settings-deprecation-warnings-dated-nov-1","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Managed policies warn when desktopHome is not set\n\nManaged policies with no desktopHome get a new check and warnings that Cowork turns on and settings change from November 10, 2026\n\n**What**\n\nManaged policies are settings an organization's administrator sets for everyone. Policies that have a `desktop` section with no `desktopHome` now go through an additional check. Before, only the `coworkEgressAllowedHosts` check ran.\n\nNew validation warnings say that from November 10, 2026, while `desktopHome` is unset:\n\n- Claude Desktop opens Unified Claude with Cowork on.\n\n- `coworkTabEnabled` no longer keeps Cowork off.\n\n- `chatSessionRetentionDays` no longer deletes Cowork tasks. `coworkSessionRetentionDays` does that.\n\n**Why**\n\nAdministrators who rely on `coworkTabEnabled` or `chatSessionRetentionDays` see in advance that these settings will stop doing what they do now, and can set `desktopHome` or switch to `coworkSessionRetentionDays`.\n\n- Area: Cowork\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: both\n- Heads-up: no"}