Claude Enterprise users can now begin with a chat and continue into file creation or code execution within the same conversation. Anthropic's October 23 announcement makes the unified chat and Cowork experience generally available for Enterprise plans.
Enterprise owners must enable the combined capability and include its new usage category in reporting. Existing account access alone does not establish that an employee can use cloud execution.
The announcement says agentic work runs in Anthropic-managed cloud sessions and can continue after a laptop closes. Chats, projects, connectors, skills and plugins carry into the experience.
Review the switch before the pilot
| Check | Why it belongs in the rollout |
|---|---|
| Chat plus cloud code execution | Both capabilities are required |
| Organization and custom-role access | Access depends on both settings |
| Connector and network permissions | The task may reach files or services |
| Usage reporting | Unified work receives its own reporting category |
Anthropic's setup guide says Owners can enable the capability in Organization settings. It recommends beginning with a sandbox organization or pilot group and reviewing network, connector and sharing controls.
Organizations using zero data retention, the HIPAA-ready configuration or customer-managed encryption keys are excluded from the new experience for now. Their existing setup remains the relevant route.
That reporting change can affect internal comparisons before any employee does more work. If a department previously counted $100 in chat and $100 in Cowork, then recorded $200 in the unified category after migration, its combined total would remain $200. Comparing only the two older categories would show an artificial drop. This hypothetical example explains the accounting issue; it is not Anthropic usage data.
Anthropic labels the new reporting category Chat and Cowork unified. Spending comparisons across the transition need to include it alongside the older categories.
Efficient mode limits the unified experience to Sonnet and Haiku models, another constraint for organizations deciding which employees should receive access.
