Until yesterday, someone in Claude had to deliberately switch into Cowork before an agent built files or ran code. As of today that choice is gone by default for Enterprise customers, and Team plans follow in two weeks. If you didn't set anything, you still made a decision.
Key facts
- Claude Enterprise turns on "Chat and Cowork unified" by default in existing organizations on November 16, 2026, unless an owner already chose a setting.
- Team plans follow on December 1, 2026; the separate Chat and Cowork experience is retired there on February 1, 2027.
- Usage now appears under a new "Chat and Cowork unified" line, per Anthropic; organizations using zero data retention, the HIPAA-ready configuration or customer-managed keys (CMEK) are excluded.
Researched and written with AI, to Luigi's brief, positions and editorial rules. Automatically checked against the sources. How I work →
You know how this goes. A new tool doesn't get rolled out. It just shows up. No kickoff, no training, no approval rule. That's what today looks like for a lot of companies on Claude Enterprise.
What changes today
Anthropic is folding Chat and Cowork into one experience on web, desktop and mobile. According to its help center, nobody picks a mode up front anymore: every conversation starts as a chat. When a task needs code or files, Claude continues in the same conversation inside an isolated cloud environment and hands back the result for review. Anthropic says that work keeps running after someone closes their laptop.
In existing Enterprise organizations the "Chat and Cowork unified" setting was off. On November 16, 2026 it turns on by default, unless an owner already made the call. Prerequisites: chat and cloud code execution with file creation are enabled. Team plans follow on December 1, and the separate experience is retired there on February 1, 2027.
The default is the real decision
Sounds like a UI refresh. It isn't. Everyone who used Claude to polish emails is now one sentence away from an agent that creates files, runs code and touches whatever connectors you allowed. That's a change in use case, not in layout.
My rule from reading Meta's and OpenAI's ad terms applies here too: audit AI features that ship switched on, and set approvals before they scale. Anthropic gives admins the controls. You can disable the "Skip all approvals" and "Automatically approve" modes so every action needs a yes. Network egress for the cloud sandbox is off by default on Enterprise. Connectors can be blocked or gated behind approval. But a switch nobody looks at protects nobody.
The catch is in your cost report
Here's the second-order point, buried in the fine print: per the help center, usage now shows up under a new "Chat and Cowork unified" line instead of Chat or Cowork. As I read it, compare spend month over month and you'll watch the chat curve drop while a new line grows. Anthropic itself notes that agentic work can burn more tokens than a quick chat. Two effects, one chart, wrong conclusions.
Then there's memory. It moves to a new system, and Anthropic says the old memory may be deleted 14 days later. For teams that built up a lot of context in Claude, that's a deadline. AI doesn't fix broken ways of working. Without a rule, it widens the cracks.
What I'd do now
- Enterprise: check Organization settings → Capabilities today and make a deliberate call. Then turn off auto-approval, set connector rules and group budgets.
- Fix the cost report: add the new line to every total, or your November numbers won't compare with October.
- Team plans: use the two weeks until December 1. Write one page of house rules: what the agent may do, who reviews, what never leaves the building.
For a model of handing agents autonomy step by step, see the AT&T case.
Bottom lineThe new Claude isn't a feature update, it's a rollout without a rollout plan, and you have to write that plan yourself today.
Got AI news? Submit news →
FAQ
Can I turn the unified Claude experience off?
Yes. Owners or Primary Owners decide under Organization settings → Capabilities. Choosing "Keep disabled" before the date keeps the separate experience, and a choice already made stays in place.
Does this apply to Team plans?
Yes, later: the setting turns on by default on December 1, 2026, and the separate experience is retired on February 1, 2027.
Source
More sources
- Claude Help Center – Team-Tarif: Standard an ab 1.12.2026, getrennte Oberfläche endet 1.2.2027
- Claude Blog – Ankündigung 23.10.2026: allgemein verfügbar für Enterprise, Efficient mode, Hinweis auf höheren Token-Verbrauch agentischer Arbeit




