Claude Desktop on 3P Moves to a Merged Chat and Cowork by Default on November 10 - Without desktopHome, Turning Cowork Off Stops Working
According to Anthropic's documentation, Claude Desktop on 3P, which uses providers such as Bedrock or Google Cloud for inference, defaults to Unified Claude at launches after noon Pacific on November 10. On devices with no desktopHome key, Cowork comes on even if coworkTabEnabled is false.
Organizations that hand out Claude Desktop internally with Amazon Bedrock, Google Cloud, Microsoft Foundry, or their own gateway behind it should review their managed settings before this takes effect. Anthropic’s documentation says that once a current build launches after noon Pacific on November 10 (20:00 UTC; 5 a.m. on November 11 in Japan), Unified Claude, the combined Chat and Cowork experience, is on by default1. A device where the desktopHome key has not been set gets Cowork even if an administrator disabled it.
The change applies to Claude Desktop on 3P, a deployment mode that sends model inference to a provider the organization chooses and keeps conversation history on each person’s device4. Anthropic aims it at organizations that cannot pass data through its own services for security, regulatory, or contractual reasons.
An Empty desktopHome Will Count as “On”
What changes is how the app treats a device with no desktopHome managed setting. The key takes two values, standard and off, and standard enables Unified Claude2. Until now, three other keys have decided what such a device shows: chatTabEnabled, chatAdvancedFileAnalysisEnabled, and coworkTabEnabled. For launches after noon Pacific on November 10, the empty key is read as standard, and that holds even when those three are false1.
The behavior has shifted across recent releases. The configuration changelog records the following3.
| Release (date) | Handling of an unset desktopHome at launches after noon PT on November 10 |
|---|---|
| Before 4.29.0 | No change |
| 4.29.0 (October 27) | standard where Cowork is on. A deployment that sets chatSessionRetentionDays but does not match it in coworkSessionRetentionDays stays on its present view |
| 4.4212.0 (October 29) | standard even when coworkTabEnabled is false |
| 4.16336.0 (November 3) | standard even when chatSessionRetentionDays is set |
Once it is on, people no longer pick between Chat and Cowork before typing on the home screen. On hardware able to run Cowork, a message from that screen opens a Cowork session; where the virtual machine cannot start, it opens a Chat conversation instead1. Past conversations and tasks remain and appear together in the sidebar. The Code tab is handled separately and follows isClaudeCodeForDesktopEnabled.
What Chat-Only Deployments Gain
The largest effect is likely on deployments that blocked Cowork and allowed only Chat. The documentation calls Chat’s set of tools deliberately small, and code execution there is off by default7. Unified Claude instead carries Cowork’s full capabilities, among them shell commands, subagents, and scheduled tasks1. It can also create and edit files in folders a person attaches.
Cowork’s shell commands run inside a dedicated virtual machine, with files confined to permitted folders and web fetches confined to an allowlist4. But allowedWorkspaceFolders, the key that sets those folders, covers every folder when left empty2. Any item an organization never filled in because Cowork was disabled would stay empty as the capabilities switch on.
Setting desktopHome to off stops both Chat and Cowork, with Code as the one remaining surface (and no surface at all if Code is disabled too)2. The documentation says Chat as a separate experience is being retired, which reads as meaning no value preserves a Chat-only setup as it stands. The route it offers instead is narrowing Cowork with disabledBuiltinTools, builtinToolPolicy, allowedWorkspaceFolders, and scheduledTasksEnabled1. Blocking shell commands, for example, means adding Bash to disabledBuiltinTools, though that entry also affects Code sessions.
Typos carry a cost too. An unrecognized value counts as off, and the documentation gives Standard as its example2. A capital letter alone would shut down Chat and Cowork.
Retention Periods and a Download Over 1 GB
Organizations using automatic deletion have one more item to check. New conversations that become Cowork tasks are removed under coworkSessionRetentionDays, not chatSessionRetentionDays3, and the former deletes nothing when unset2. If only the Chat period is configured, a new conversation that became a Cowork task would not be deleted once that period passes. The documentation asks administrators to set both by November 101.
Networks may need preparation as well. A Cowork-capable device without the virtual machine workspace fetches a bundle larger than 1 GB from downloads.claude.ai the first time someone starts a new conversation1. Environments that restrict downloads through a proxy or firewall are told to allow it ahead of the date.
Organizations on the Enterprise Admin Console control this from the Capabilities screen, while MDM and bootstrap-server deployments use the desktopHome key1. Admin Console organizations created from now on begin with it enabled. For the Claude apps gateway, Claude Code 2.1.319 added a warning at start-up for policies that lack desktopHome and depend on coworkTabEnabled: false or chatSessionRetentionDays5.
Older Keys Stop Being Read on December 17
November 10 is not the last date. coworkTabEnabled, chatTabEnabled, and chatAdvancedFileAnalysisEnabled are deprecated, and from noon Pacific on December 17, newer releases will disregard them while older ones keep reading them3. An in-app warning begins on November 17 on devices that still have any of the three.
Easier to miss is sessionRetentionHold, which suspends retention-based deletion and will be disregarded on the same day. If retention periods are in place at that point, the idle sessions the key had preserved are deleted for good3. No in-app warning appears. To keep them, the guidance is to raise each of the three retention settings to 3,650 days first and only then remove the key. Organizations relying on this key need to work through that procedure separately from the November 10 change.
A Merger That Reached the Standard App First
Chat and Cowork came together earlier in the regular Claude app. Anthropic announced the merger on September 16 and later added that it became generally available for Claude Enterprise on October 236. New Cowork tasks on Pro and Max plans moved to cloud-only execution on October 6, and on November 5 Claude Enterprise administrators gained the ability to change key Claude Desktop settings from organization settings. This change makes the combined layout the standard on 3P as well, the mode meant for organizations that cannot pass data through Anthropic’s own services.
A sensible order is to check which app versions are deployed and whether desktopHome exists, then either set it to off where Cowork is not permitted or test settings that narrow its capabilities. With little time left, an organization that has not settled its policy could also set desktopHome to off explicitly, accepting that Chat stops as well.
Sources
- Unified Claude in Claude Desktop on 3P - Anthropic documentation (checked November 9, 2026)
- Configuration reference - Anthropic documentation (checked November 9, 2026)
- Configuration changelog - Anthropic documentation (checked November 9, 2026)
- Claude Desktop on 3P overview - Anthropic documentation (checked November 9, 2026)
- Claude Code CHANGELOG - Anthropic changelog (checked November 9, 2026)
- Claude Cowork and chat are now one Claude - Anthropic blog (September 16, 2026; updated October 23)
- Chat in Claude Desktop on 3P - Anthropic documentation (checked November 9, 2026)
Was this article helpful?
Thank you!
Received. Thank you!