Anthropic brings unified chat and task execution to Claude Enterprise
The rollout removes the upfront choice between chat and Cowork. Administrators retain access and spending controls, while some security configurations remain excluded.
Loading page…
The rollout removes the upfront choice between chat and Cowork. Administrators retain access and spending controls, while some security configurations remain excluded.
Listen to this story
Anthropic made unified chat and Cowork generally available to Claude Enterprise customers on October 23, 2026, bringing cloud-backed task execution into existing conversations. The change shifts the key decision from choosing an interface to whether an organization permits cloud execution—and how it governs access and spending. The rollout has security and cost controls, but organizations using zero data retention, HIPAA-ready configurations, or customer-managed encryption keys are excluded.
The experience is currently off by default; if both Chat and Cloud code execution and file creation are enabled, it turns on automatically November 16, 2026, unless an owner keeps it disabled.
Each cloud-execution conversation gets an isolated virtual machine; outbound network access is off by default, and connector credentials stay outside the workspace.
Task execution can consume more tokens than quick chats; Efficient mode limits access to Sonnet and Haiku, while administrators can set spend limits and pooled budgets.
Claude Enterprise users can now ask a question and hand off a larger task without choosing separate tools first. Anthropic made its unified chat and Cowork experience generally available on October 23, 2026, bringing cloud-based task execution into the same conversation across web, desktop and mobile—with access still governed by enterprise administrators.
The Enterprise release follows the combination of chat and Cowork for Pro and Max subscribers in September. The starting point is now a conversation, rather than a decision about which Claude interface fits the job.
A simple question still gets an answer. When a request needs code execution or file work, Claude moves into an isolated cloud workspace managed by Anthropic, then returns the finished work for review. Users are not asked to switch modes, and the conversation can return to ordinary chat when task execution is no longer needed.
Because execution happens in the cloud, work can continue after someone closes their laptop. A user can start on desktop and resume on the web or a phone. Existing chats, projects, connectors, skills and plugins carry over, while scheduled tasks and session history continue without needing to be recreated.
Anthropic's admin setup guide says the experience is currently off by default. Owners can enable Chat and Cowork unified in Organization settings, but both Chat and Cloud code execution and file creation must also be enabled. The older Cowork switches are not prerequisites. Once the organization enables it, standard roles receive access; custom roles need the corresponding permission. Access is checked on every request.
Pricing remains usage-based, and Anthropic cautions that task execution can consume more tokens—the units used to measure model usage—than a quick chat. Administrators have several ways to constrain that spending:
Usage reporting changes too. Once a member has access, their chat and Cowork activity appears under Chat and Cowork unified. Earlier usage stays in its original category. Anthropic says this changes where activity is reported, not how it is counted or billed.
Anthropic says each conversation needing cloud execution gets its own isolated virtual machine. Outbound network access is off by default for Enterprise, and connector credentials stay outside that workspace. Existing sign-in controls carry over. Administrators can also prohibit automatic approvals, requiring users to approve actions such as tool use, file edits and browsing.
The workspace stops after a few idle minutes and saves its disk as an encrypted snapshot. It expires 30 days after creation, while the conversation stays on record. Deleting a conversation also deletes cloud sessions started from it, with deletion completed in the background. Scheduled tasks are an important exception: they can keep running after their originating conversation is deleted.
General availability does not cover every Enterprise configuration. The setup guide excludes organizations using zero data retention, the HIPAA-ready configuration or customer-managed encryption keys. Those organizations remain on their current setup rather than moving into the unified experience.
Loading discussion...
Join the conversation
Explain whether administrators should explicitly approve the change.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.