Unified Claude is in beta. It is opt-in until November 10, when it becomes enforced for all Desktop 3P deployments. New Enterprise Admin Console organizations start with Unified Claude on.
What users see with Unified Claude
With Unified Claude on, users type into the message box on the home screen without first choosing between Chat and Cowork. On a device that can run Cowork, each message sent from the home screen starts a Cowork session. On a device that can’t run Cowork, the message starts a Chat conversation instead. A Claude session started this way has Cowork-level tools and follows your Cowork settings. For example, Claude can create and change files in folders the user attaches, and create scheduled tasks. Users keep their earlier chats and Cowork tasks, and the sidebar lists them together.Enabling Unified Claude
Unified Claude is opt-in today. To enable it, follow the instructions below:- Enterprise Admin Console: Go to Capabilities and toggle on “Opt into the new Chat and Cowork unified view.”
- MDM or a bootstrap server: For MDM and bootstrap deployments, the
desktopHomekey controls Unified Claude. Create and setdesktopHometostandardin your MDM profile or bootstrap response. Claude Desktop reads a value it doesn’t recognize asoff. Remove the key to disable the Unified Claude experience.
How Unified Claude interacts with Chat and Cowork settings
When Unified Claude is enabled, Claude Desktop ignoreschatTabEnabled, chatAdvancedFileAnalysisEnabled, and coworkTabEnabled. New conversations follow the Cowork retention period. The Chat retention period still covers Chat conversations, such as earlier chats.
Your other settings still apply while desktopHome has a value, including isClaudeCodeForDesktopEnabled, which controls Code.