◈AI Codex
Tools & EcosystemHow It Works

Chat and Cowork merge on Claude Enterprise on November 16: the admin checklist

In brief

On November 16, 2026, Claude Enterprise turns on the unified chat and Cowork experience by default. Conversations start as chats and move into a cloud sandbox when they need code or files. Here is what changes, who can't turn it on, and the settings to check before the date.

5 min read·

Contents

♡Sign in to save

On November 16, 2026, Claude Enterprise switches on the unified chat and Cowork experience by default. If you are an admin and have not chosen yet, Claude chooses for you on that date. You can turn it on earlier, or keep it off.

Last checked: November 3, 2026, against Anthropic's admin help article and launch post (October 23, 2026). Pro and Max got the same change in September.

What changes for your people?

  • There is no chat vs. Cowork choice any more. Every conversation starts as a chat. When a task needs code or files, Claude carries on in a cloud sandbox and hands back the finished work.
  • Work keeps going with the laptop closed and can be picked up on web, desktop or mobile.
  • Nothing is lost. Chats, Projects, connectors, skills and plugins carry over.
  • Linking a computer is optional. People only need the desktop app linked if Claude should reach local folders, local MCP servers or desktop apps.

Each cloud sandbox is its own virtual machine. It pauses after a few idle minutes, is saved as an encrypted snapshot, and expires 30 days after it was created.

Who can't turn it on yet?

Organizations using any of these stay on their current setup and cannot enable it:

  • Zero data retention
  • The HIPAA-ready configuration (support is expected after general availability)
  • Customer-managed encryption keys (planned for a later release)

If you turn on customer-managed keys after enabling it, the unified experience switches off.

What should I check before November 16?

All of these are under Organization settings.

  1. Decide: now, or wait. Owners see a notice with Enable now or Keep disabled. The switch itself is Capabilities > Chat and Cowork unified. It needs Chat and Cloud code execution and file creation turned on. If either is off, nothing changes on the 16th.
  2. Roll out by role if you want a pilot. Turn it on per custom role under Roles > Capabilities. New roles include it by default.
  3. Network egress. Under Capabilities > Code execution, choose off, package managers only, custom domains, or all domains. It is off by default on Enterprise. Most teams want at least package managers.
  4. Approval modes. Decide whether people may use Skip all approvals and Automatically approve. Turning them off means a person approves each action, including in scheduled tasks and the built-in browser.
  5. Connector policies. Set connectors to Blocked or Needs approval per role. These are enforced outside the sandbox on every call.
  6. Sharing. A conversation that used the sandbox can only be shared when both Share chats and Share cloud sessions are on.
  7. Remote control, Trusted Devices and scheduled tasks. Each has its own switch. Turning off Remote control stops web, mobile and scheduled tasks from using a linked computer.
  8. Cost. Set spend limits for the org, groups and members. Efficient mode keeps people on Sonnet and Haiku, and new sessions start on Sonnet 5.5 at low effort.

What happens to data and memory?

  • Cloud sessions started from a conversation are deleted with that conversation, transcripts included.
  • Files Claude gives people in conversations from October 8, 2026 onward are deleted with those conversations.
  • Custom retention (minimum 30 days) covers conversations, Projects and artifacts.
  • Memory moves to a new system. Old memory may be deleted 14 days later.
  • Some things are not removed when a conversation is deleted: sessions started directly in Cowork, scheduled tasks and their runs, local Cowork history, and Claude Code transcripts. Your retention policy should cover these separately.

Will my usage numbers break?

Yes, a little. Usage for people on the unified experience shows up under a new Chat and Cowork unified line, not under Chat or Cowork. Billing does not change.

  • Add the new line when you total Chat and Cowork spend or messages.
  • Count people with the overall active-users number, not per product.
  • In the Cost and Usage API, look for the product value chat_cowork_unified.
  • Top connectors and Top skills don't include it yet.

If you report Cowork adoption to leadership, note the date you switched so the drop in the old Cowork line isn't read as people leaving.

What should I do this week?

  • Pick a date: enable early for one pilot role, or let it switch on the 16th.
  • Set network egress and the two approval modes on purpose, not by default.
  • Tell people that chat and Cowork are now one place, and that closing the laptop no longer stops work.
  • Add the new usage line to your adoption dashboard.

Anthropic is also running an admin webinar on the change on November 4, 2026.


Related: Cowork and chat are now one Claude · Claude admin controls in 2026 · Six metrics that tell you if Cowork is working

Related tools

Weekly brief

For people actually using Claude at work.

Each week: one thing Claude can do in your work that most people haven't figured out yet — plus the failure modes to avoid. No tutorials. No hype.

No spam. Unsubscribe anytime.

What to read next

All articles →