SaaS · News
Claude Enterprise Merges Chat and Cowork
Claude Enterprise now runs chat and Cowork as one experience, with agentic work in Anthropic-managed cloud VMs. Admins get a new Efficient mode, per-role model entitlements, spend limits and pooled budgets to keep the token bill in check.
Alex Rivera · Oct 23, 2026 · 8 min read
On this page
Anthropic made its unified chat and Cowork experience generally available for Claude Enterprise on October 23. A conversation starts as chat and moves into a managed cloud environment when the task needs code or files.
For admins, this turns every chat seat into a potential agent seat. The real news is the set of cost and access controls that ship with it.
Image: Claude by Anthropic, Claude Cowork and chat come together for Enterprise, October 23, 2026.
How it works
Users no longer pick between chat and Cowork. Quick questions get quick answers. When work needs to run code or handle files, Claude continues in the cloud and returns the finished document, analysis, or deck. The task keeps running after the laptop closes and can be picked up on web, desktop, or mobile. Chats, projects, connectors, skills, and plugins carry over. Pro and Max plans got the same change in September.
Each cloud session runs in its own isolated virtual machine. For Enterprise, network egress is off by default and connector credentials are kept outside the sandbox. It sits on the controls Enterprise customers already use, including SSO and the Compliance API.
The cost controls, and Anthropic's numbers
Pricing stays usage-based. Anthropic says agentic work can use more tokens than chat, and it ships four controls. Efficient mode keeps the unified experience on Sonnet and Haiku. Model entitlements set which models each role can use. Spend limits apply at the organization, group, and member level. Pooled group budgets give a team one shared monthly amount.
Anthropic's own figures: Claude Opus 5.5 costs 40% less to run than Opus 5 on typical workloads, and Sonnet 5.5 costs up to 30% less than Sonnet 5 for most work. These are vendor claims about typical use; your mix of long agent runs may look different.
What to do this week
Set spend limits and pooled budgets before you flip the rollout in Organization settings, not after the first invoice. Turn on Efficient mode for broad populations and entitle Opus only to the roles that need it. Confirm that egress stays off unless a team has a reason to open it.
Check your exceptions. Organizations using zero data retention for Claude Code, a HIPAA-ready configuration, or customer-managed encryption keys stay on their current setup for now, so those teams will not see the unified experience yet.
Sources
https://claude.com/resources/articles/unified-claude-enterprise