Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Teams

Claude Desktop Unified turns on Nov 10

Written November 10, 2026

Unified Claude combines Chat and Cowork into one screen. It switches on by default today, and two settings admins thought they had set will stop doing what they expected.

The problem

A team admin who disabled Cowork, or who set a chat retention period, has both decisions quietly overridden by today's default. Under Unified Claude, a message sent from the home screen starts a Cowork session on any device that can run Cowork's virtual machine, with Cowork-level tools: Claude can create and change files in folders the user attaches, and create scheduled tasks. Earlier chats and Cowork tasks stay where they are, listed together in the sidebar.

What switches on, and when

Anthropic's Unified Claude page says the change is opt-in until November 10, 2026. When a current version of Claude Desktop starts after 12:00 PM Pacific Time on that date, it reads an unset desktopHome key as standard, the value that turns on Unified Claude. The configuration changelog puts it the same way: at launches after 12:00 PM PT on November 10, 2026, an unset key reads as standard, even where chatSessionRetentionDays is set, and Unified Claude opens with Cowork on even where coworkTabEnabled is false.

The retention trap

This is the part that costs teams data they meant to delete. New conversations that are Cowork sessions are deleted by coworkSessionRetentionDays, not by chatSessionRetentionDays. The chat period still covers earlier Chat conversations, but every new conversation started from the home screen on a Cowork-capable device is a Cowork session, so it follows the Cowork period. A fleet that set only the chat period will hold those new conversations longer than intended. Anthropic's own advice is to set both, before November 10, and administrators see a configuration warning where the two differ.

Settings that stop working

Claude Desktop ignores chatTabEnabled, chatAdvancedFileAnalysisEnabled, and coworkTabEnabled when the configuration sets desktopHome, whether to standard or to off, and it ignores them while Unified Claude is on by default. The changelog adds the end date: this release and later versions ignore those three keys from 12:00 PM PT on December 17, 2026, and users see an in-app warning from November 17, 2026 while one is still set. Other settings still apply, including the ones that limit what Claude can do in Cowork, such as disabledBuiltinTools and allowedWorkspaceFolders.

The download to plan for

With Unified Claude on, a device that can run Cowork needs the VM workspace bundle that Cowork uses. A device that does not have it downloads it, more than 1 GB, from downloads.claude.ai when the user starts their first new conversation. If a proxy or firewall limits downloads on the network, that change needs to be made before the first conversation, not after users start reporting failures.

What to do today

  1. Set both retention periods. Set coworkSessionRetentionDays to the same number of days as chatSessionRetentionDays, unless the team has a reason to keep Cowork sessions longer.
  2. Drop the three dead keys. Remove chatTabEnabled, chatAdvancedFileAnalysisEnabled, and coworkTabEnabled from the configuration; they have no effect under standard and are ignored entirely from December 17, 2026.
  3. Allow the bundle download. Make sure downloads.claude.ai is reachable through the proxy and firewall, or the first new conversation on each device will stall on a download of more than 1 GB.
  4. Limit Cowork tools where needed. Use disabledBuiltinTools and allowedWorkspaceFolders to bound what Cowork sessions can do; the old tab toggles no longer do that job.

Limits

Related playbooks

Sources

Back to: Teams playbooks hub · Also: Claude Code hardens its sandbox ahead of Nov 10