Anthropic merges chat and task work in Claude Desktop’s third-party deployments

Users of Claude Desktop’s third-party deployments will no longer choose between a quick chat and a tool-equipped task before sending a message. Anthropic’s Unified Claude beta combines those starting points, making Cowork sessions the default on supported devices. The company has documented a phased move from optional adoption to mandatory deployment.

Anthropic lists November 10 as the point when Unified Claude becomes mandatory for all Desktop 3P deployments, but does not specify a year. Until that deadline, the experience is opt-in. Newly created Enterprise Admin Console organizations already start with Unified Claude enabled rather than requiring an administrator to turn it on.

One message box, different tools

The unified home screen removes the initial Chat-versus-Cowork selection. A message starts a Cowork session when the computer can launch Cowork’s virtual machine, the environment needed for its tools. If that environment cannot launch, the same message box starts a Chat conversation instead. The fallback depends on the device’s ability to run Cowork, not a separate mode selected before typing.

These sessions use the capabilities already available in Cowork on Desktop 3P. Anthropic lists bash execution, which runs shell commands; subagents, which are additional agents used within a task; and scheduled tasks. This is a change to how users enter that tool-equipped experience, rather than a newly listed set of Cowork capabilities.

A session can create or change files in folders the user attaches and create scheduled tasks, subject to the organization’s Cowork settings. The attached-folder detail is important: the documented file workflow concerns folders supplied by the user, while administrators can restrict specific capabilities through settings and tool policies.

Earlier chats and Cowork tasks remain available and appear together in the sidebar. Code stays separate from the combined experience; the unification covers Chat and Cowork, not every Claude Desktop workspace.

The switches administrators need to revisit

Anthropic’s enabling instructions provide two routes into the beta. One uses an Enterprise Admin Console toggle. The other uses a configuration key delivered through mobile device management, or MDM, or a bootstrap server. The documented choices are:

• Enterprise Admin Console: Open Capabilities and enable the toggle labeled “Opt into the new Chat and Cowork unified view.”
• MDM or bootstrap deployment: Create the desktopHome key and set its value to standard in the management profile or bootstrap response.
• Configuration handling: An unrecognized value is treated as off. Anthropic instructs administrators to remove the key to disable the unified experience during the opt-in phase.

Once Unified Claude is enabled, three existing settings no longer govern the experience: chatTabEnabled, chatAdvancedFileAnalysisEnabled, and coworkTabEnabled. Anthropic says Claude Desktop ignores them. Restrictions on particular Cowork tools remain available through other settings and tool policies, rather than through those Chat and Cowork tab controls.

Retention also follows the new session type. New conversations use the Cowork retention period, while the Chat retention period continues to cover Chat conversations, including earlier chats. Other settings still apply when desktopHome has a value, including isClaudeCodeForDesktopEnabled, the separate control for Code.