What does the unified Claude Chat and Cowork experience mean for Enterprise teams?

Short answer: Anthropic has merged Claude chat and Cowork into one experience for Claude Enterprise, so a conversation starts as a normal chat and moves into a cloud workspace on its own when a task needs to run code or work with files. It is off by default in existing organisations but switches on by default on 16 November 2026, so IT, L&D and HR leaders have a few weeks to decide how to roll it out and prepare staff.

What Anthropic has announced

On 23 October 2026, Anthropic announced on its website that the unified Claude experience is now generally available for Claude Enterprise plans. It says chat and Cowork first came together for Pro and Max plans in September.

According to Anthropic's admin setup guide:

• people no longer choose between chat and Cowork before they start, because every conversation begins as a chat
• 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
• work keeps going in the cloud, and people can start a task on the desktop app and pick it up on web or mobile
• the setting appears as "Chat and Cowork unified" in Organization settings > Capabilities, and needs both Chat and Cloud code execution and file creation switched on
• it is off by default in existing organisations and turns on by default on 16 November 2026, unless an Owner chooses Keep disabled
• organisations using zero data retention, the HIPAA-ready configuration or customer-managed encryption keys can't use it yet

Anthropic's Claude Academy tutorial for admins adds that Claude usually stays in chat for questions, brainstorming and summarising something you paste in, and moves to a workspace when a task needs it to do something, such as create or edit files, analyse a dataset or work across connected tools.

Why this matters for your Claude rollout

Until now, staff had to decide between chat and Cowork before they started. Removing that choice means people can meet agentic work, where Claude plans and carries out several steps, without deciding to.

That is good news for adoption, and it changes what people need to know:

• Briefing, not just prompting. A request can now come back as a finished report, spreadsheet or deck. People get better results when they explain the goal, the audience and what a good result looks like.
• Checking the work. A longer piece of finished work has more places for a mistake to hide. Staff need a simple habit for reviewing output before it goes anywhere.
• Approvals. Anthropic's guide lists settings that control whether Claude must ask before using tools, editing files or browsing, including whether people can let Claude approve actions on its own. Staff should understand what they are approving. Anthropic's admin tutorial also notes that "shell and file work inside the cloud sandbox doesn't ask", so checking the finished work matters even with approvals switched on.
• Memory. Anthropic says memory moves to a new system and the old memory may be deleted 14 days later. People who rely on Claude remembering their preferences should know this.

Practical takeaways by role

IT leaders: Decide before 16 November whether to enable it now, keep it disabled for a while, or start with a pilot group using custom roles. Anthropic's admin tutorial says that on mobile, admins "can't yet limit access to selected roles", but can block mobile access through the identity provider, so plan how a role-based pilot will work on phones. Anthropic recommends sharing its guide with IT, security and procurement, completing a security review, and checking network egress, connector, sharing and remote control settings first. It also describes spend limits at organisation, group and member level, and a new Efficient mode that keeps the unified experience on Sonnet and Haiku models.

L&D leaders: Plan a short, hands-on session for the pilot group that covers writing a clear brief, spotting when Claude has moved into a workspace, and reviewing finished files. Use real tasks from each team rather than generic examples. Our Claude training is built around this kind of everyday work, and our Claude Essentials course suits people who want to learn at their own pace.

HR leaders: Agentic tools raise fair questions from staff about how their work will change. Explain what is changing and why, and update guidance on what information people can share with Claude. Our page on AI training for HR teams covers the people side, and our guide to writing an employee AI policy can help with the rules.

Transformation leaders: Anthropic's guide recommends monitoring usage and feedback for two to four weeks before expanding in waves. Use that window to measure a handful of tasks before and after, such as time to first draft and rework needed. Our guide to measuring AI training ROI explains how to set a baseline.

A simple plan for the next three weeks

1. Check your settings. Confirm whether the change will reach your organisation and what your Owners plan to do before 16 November. Anthropic's tutorial says it turns on "on the date in your general availability email", so check that email as well.
2. Pick a pilot group. Choose people with varied roles and real, repeatable tasks.
3. Train before you switch on. A short session on briefing and checking work helps people get more from the first weeks.
4. Collect feedback. Ask what worked, what went wrong and which tasks saved time.
5. Expand in waves. Use what the pilot taught you to brief the next group.

If you use more than one assistant, our comparison of Claude vs ChatGPT for business may help you decide where each fits.

What this means for your team

Claude no longer asks people to pick between a chat tool and an agentic one. That makes it easier to use and more capable, which is exactly why training matters. Teams that learn to brief Claude clearly and check what it hands back will get real value from the change, while teams that just wake up to it on 16 November may find it confusing.

Not sure where your team stands today? Our free AI readiness scorecard takes a few minutes. To see how we help teams use Claude well in their day-to-day work, take a look at our Claude training. We also run sessions in person, including AI training in Leeds.

Talk to us

If you would like help planning a Claude rollout or training your pilot group, book a short chat with Day Seven.