The new unified Claude experience brings chat and Cowork together on web, desktop, and mobile. Members no longer choose between chat and Cowork before they start. Every conversation starts as a chat, and when a task needs to run code or work with files, Claude continues the same conversation in an isolated cloud sandbox managed by Anthropic, then returns the finished work for review.
This article explains how admins turn on the new unified Claude experience, which settings apply to it, and how it fits your security, compliance, and data retention setup.
The new unified Claude experience is in public beta for Claude Enterprise plans. In your admin settings it appears as Chat and Cowork unified (beta). The new unified Claude experience is off by default. Nothing changes for your organization until an admin turns it on.
How the new unified Claude experience works
One conversation, two modes. The new unified Claude experience starts as a chat and moves into a Cowork cloud session when a task needs agentic work, and goes back to chat when it doesn't. Members aren't asked to switch modes.
Agentic work runs in an isolated cloud sandbox. Each conversation that needs one gets its own virtual machine, managed by Anthropic. After a few minutes idle, the virtual machine is stopped and its disk is saved as an encrypted snapshot. The sandbox environment expires 30 days after it was created.
The conversation stays on record. Chat history, sharing, export, the Compliance API, and your data retention setting all work from the conversation.
Work moves across devices. Members can start a task on the desktop app and pick it up on web or mobile.
Local access stays optional. Through the Claude desktop app, members can link their computers so Claude can work with local folders, local MCP servers, and applications. Your Remote control and device policies govern this.
Before you begin
The new unified Claude experience requires two capabilities to be on for your organization:
Chat, since chat is where every conversation starts.
Cloud code execution and file creation, since agentic work runs remotely.
It doesn't require Cowork or Cowork in the cloud to be on. It is meant to replace both over time.
Your organization today | What to do |
Chat only | Turn on Chat and Cowork unified (beta). You don't need to turn on Cowork or Cowork in the cloud separately. Make sure Cloud code execution and file creation is on. |
Cowork only, or Cowork and Cowork in the cloud | Turn on the Chat capability, then turn on Chat and Cowork unified (beta). Make sure Cloud code execution and file creation is on. |
Chat and Cowork | Make sure Cloud code execution and file creation is on, then turn on Chat and Cowork unified (beta). |
The new unified Claude experience isn't available yet for organizations that use zero data retention (ZDR), the HIPAA-ready configuration, or customer-managed encryption keys (CMEK). See Current limitations below.
Turn on the new unified Claude experience
For your whole organization
Sign in to Claude as an Owner or Primary Owner.
Turn on Chat and Cowork unified (beta).
Ask members to refresh the Claude app if they don't see the new experience right away.
This turns on the new unified Claude experience for every member of your organization. To limit access to specific members, use roles instead.
Scheduled tasks and session history will continue working after the change. You don’t need to update or recreate anything.
For specific members, using roles
If your organization uses custom roles, you can grant the new unified Claude experience to specific roles:
Open the role you want to update and go to “Capabilities.”
Turn on Chat and Cowork unified (beta) for that role.
Assign the role to the members who should have access. You can sync role membership through SCIM to add members in waves.
Access is checked on every request. If you remove a member's role or turn the setting off, they lose access to the new unified Claude experience.
To learn how to create a role, see Set up role-based permissions on Enterprise plans.
Recommended rollout
Share this article with your IT, security, and procurement teams.
Complete your security review. Most teams review two components they already know: Claude chat and Cowork in the cloud. If a review of Cowork in the cloud is already underway, it carries over.
Start in your sandbox organization, if you have one, or with a pilot group through a role.
Review your network egress, connector, sharing, and remote control settings before you turn the experience on.
Monitor usage and gather feedback for two to four weeks, then expand in waves.
Admin settings that apply to the new unified Claude experience
Setting | Where | How it applies to the new unified Claude experience |
Chat and Cowork unified (beta) | Organization settings > Capabilities | Turns the new unified Claude experience on for the organization. Off by default. Changes are recorded in the activity feed. |
Chat and Cowork unified (per role) | Organization settings > Roles > Capabilities | Grants the new unified Claude experience to members of a role. |
Allow network egress | Organization settings > Capabilities > Code execution | Controls which internet destinations code in the sandbox can reach: off, package managers only, a custom list of domains, or all domains. Off by default for Enterprise. |
Connector policies (Blocked, Needs approval, per-role restrictions) | Organization settings | Enforced by Anthropic outside the sandbox, on every connector call. |
Always allow for connector tools | Organization settings | When off, members can't give a connector tool a standing approval, and Claude asks each time. |
Allow "Skip all approvals" mode | Organization settings | When off, users can’t let Claude act without asking for approval — including using tools, editing files, and browsing websites. This specifically applies to scheduled tasks and the built-in browser in the unified experience. |
Allow “Automatically approve” mode | Organization settings | When off, users can’t let Claude approve actions on its own. The user must approve each one — including using tools, editing files, and browsing websites. |
Share chats and Share cloud sessions | Organization settings | A conversation that has used its sandbox can be shared only when both settings are on. The more restrictive setting applies. |
Remote control | Organization settings | When off, web and mobile can't use a member's linked computer. |
Require Trusted Devices | Organization settings | Require members to verify each new device before it can connect to Claude on their computer remotely. |
Scheduled tasks | Organization settings | When off, scheduled tasks that execute remotely are disabled for your org. Users will not be able to create new scheduled tasks in the cloud. |
Custom data retention | Organization settings | Governs conversations and projects. See Data retention and deletion below. |
Compliance API | Organization settings | Covers conversations in the new unified Claude experience with your existing access keys. For setup and endpoint reference, see Access the Compliance API and the Compliance API documentation. |
Analytics API | Organization settings | Covers analytics for the new unified Claude experience with your existing access keys. Please refer to the Analytics API documentation.
|
Admin API | Organization settings | Works with your existing access keys. The new unified Claude experience appears as the chat_cowork_unified permission when you list a custom role's permissions. For endpoint reference, see the Admin API documentation. |
Open Telemetry (OTEL) | Organization settings | If you've set up OpenTelemetry export, a conversation's cloud session sends the same events as other cloud sessions (metadata only, by default). Anthropic recommends using Compliance API. |
Device policy for the Claude desktop app | Your device management (MDM) tool | On managed computers, limits which folders can be connected, disables user-added local MCP servers and extensions, and can require sign-in to your organization. See Enterprise configuration for Claude Desktop. |
Identity settings carry over unchanged. Members sign in to Claude as members of your organization, and your SSO (SAML/OIDC), SCIM provisioning, and tenant restrictions apply. The new unified Claude experience adds no separate sign-in.
For recommended Security settings and architecture, see Unified Claude and Cowork security best practices.
Data retention and deletion
Conversations. Conversations are kept until the member deletes them or according to your organization's custom data retention setting (30-day minimum). See custom data retention.
Cloud sessions started from a conversation. When Claude starts a cloud session in a conversation, that session is deleted together with the conversation per our data retention practices: when a member deletes the conversation or its project, or when it reaches your custom retention period. The sandbox environment expires 30 days after it was created, and the conversation then continues in a fresh environment.
Cloud sessions started outside a conversation. Cowork cloud sessions that a member starts on their own, whether or not they're in a project, and scheduled task runs don't belong to a conversation. Custom data retention doesn't cover them.
Once the new unified Claude experience is turned on, memory will no longer be deleted according to your organization’s custom data retention setting for the public beta. Memory deletion will be covered by custom data retention when the new unified Claude experience is generally available.
Manage access and spend
Pricing stays usage-based, and the spend controls you have today apply.
Spend limits can be set at the organization, group, and member level.
Usage analytics break out chat, Cowork, and the new unified Claude experience.
Models: The model allowlist you set applies to both chat and agentic work in the new unified Claude experience.
Usage and analytics
The new unified Claude experience gets its own line in your reports. When a member has access to the new unified Claude experience, their chat and Cowork usage is reported under Chat and Cowork unified (beta), not under Chat or Cowork. Think of it as a new folder for the same work: only where the usage is filed changes, so moving usage to this line doesn't change how it's counted or billed.
How usage is counted
Counting follows each member. Usage counts toward the new unified Claude experience if the member has access to it when the usage happens. If you turn it on for some roles first, your reports can show Chat, Cowork, and Chat and Cowork unified (beta) on the same day.
It covers chat and Cowork. A member's chats, their cloud sessions, and their use of the Cowork desktop app count toward the new unified Claude experience.
Other products keep their own line. For example, Claude Code and Claude in Chrome usage is still reported under those products.
Past usage stays where it is. Data for the new unified Claude experience starts the day a member first gets access. Usage from before then stays under Chat or Cowork. If you turn the new unified Claude experience off, past unified usage keeps its Chat and Cowork unified (beta) label, and new usage goes back to Chat and Cowork.
Include it when you add things up. When you add up spend, tokens, or messages for Chat and Cowork, include Chat and Cowork unified (beta) too. Otherwise your Chat and Cowork numbers will seem to drop as members move over. For the number of people, use the overall active users count rather than adding products together, since one person can be active in more than one.
In the analytics dashboard
A page of its own. Admins who can view analytics will find a Chat and Cowork unified page under Apps, marked Beta. It shows daily active users.
Across the dashboard. You can pick "Chat and Cowork unified (beta)" in the Active users, Active members, Total spend, and Spend by model charts. The See all members table on the Overview page has a "Messages in Chat and Cowork unified (beta)" column. The Top connectors and Top skills cards don't include it yet.
Who sees it. The page appears for every organization that can turn on the new unified Claude experience, whether or not it is on yet.
Give it a day or two. New activity can take up to two days to show up.
In the APIs
Your keys already work. If you already use these APIs, your existing access keys work. If your scripts check responses against a fixed list of fields or products, add the new ones.
Cost and Usage API. Tokens and spend for the new unified Claude experience are reported under the product value
chat_cowork_unified. You can filter to it withproducts[]. Thechatandcoworkvalues still work, and cover usage from members who didn't have the new unified Claude experience at the time.Analytics API. Member, skill, and connector rows have a
chat_cowork_unified_metricsobject with two parts:chat, for chat activity, andsessions, for cloud sessions and the Cowork desktop app. Daily summaries add daily, weekly, and monthly active user counts for the new unified Claude experience, such aschat_cowork_unified_daily_active_user_count.
What members see
Members with usage-based seats see their own usage of the new unified Claude experience on their usage page, listed as Chat and Cowork unified (beta).
Unified smart report and analytics chat
To learn how to create a smart report, refer to Get started with smart reports. When choosing products to run the report for, choose “Chat and Cowork unified (beta)” to run the report against the new unified Claude experience.
Efficient mode for the new unified Claude experience
When on, org members can use only Sonnet and Haiku models in the new unified Claude experience, and new sessions start on Claude Sonnet 5.5 at low effort. Other products aren’t affected. As lower-cost models become available, Anthropic may update the default model and effort level to keep the best balance of performance and cost.
How to access it: Owners can turn it on for the whole org on the Models page, or for specific custom roles on each role's Models tab.
Current limitations
ZDR, HIPAA, and CMEK. The new unified Claude experience isn't available to organizations with zero data retention, the HIPAA-ready configuration, or customer-managed encryption keys. These organizations stay on their current configuration. HIPAA and CMEK support is expected after general availability.
Per-role access for Remote control and scheduled tasks. These are set for the whole organization, not per role.