Your teams no longer pick which Claude to use.

01 · What changed

What Anthropic shipped.

What changed: team members used to choose between chat and Cowork before they started work. Now they are one Claude on web, desktop and mobile, and a quick question and a full project can sit in the same conversation. Chats, projects, connectors, skills and plugins carry over, and cloud work keeps going after someone closes their laptop. Enterprise admins control access by role and manage usage with a new Efficient mode.

1. 1

   One conversation

   Conversations begin as a chat, and a simple question still gets a quick answer. A larger task continues in the same thread.

2. 2

   Work runs in the cloud

   When a task needs code or files, Claude continues in the cloud and returns the finished document, analysis or deck. It keeps going after the laptop closes.

3. 3

   Pick up on any device

   Work started on one device can be picked up on the web, desktop or mobile.

4. 4

   Nothing to rebuild

   Chats, projects, connectors, skills and plugins carry over to the unified experience.

5. 5

   Isolated sessions

   Each cloud session runs in its own isolated virtual machine. Network egress is off by default for Enterprise, and connector credentials stay outside the sandbox.

6. 6

   Existing controls apply

   It builds on SSO and the Compliance API. Anthropic says data is encrypted in transit and at rest and not used for model training by default.

7. 7

   Access by role

   Enterprise admins control who gets access by role.

8. 8

   Efficient mode

   A new mode for admins to manage usage. Enterprise pricing stays usage-based.

02 · What it means

What it means for your seat.

For a firm already on Claude Enterprise, the question of which Claude to use goes away: an analyst can ask about one clause in a credit agreement, then hand over the whole data room for a first-pass summary in the same thread. The controls build on what you have already approved, but cloud agentic work is a new kind of activity, so admins and risk teams should decide who gets it and how usage is managed.

03 · This week

0 of 3 done

1. 01 · Decide which roles get agentic work: Pick the first groups, for example one deal team or the operations team, and set access by role in the admin controls. Note how you will use Efficient mode to manage usage.
2. 02 · Brief risk on the cloud architecture: Share the security best practices guide from the Anthropic Trust Center with risk and compliance. Confirm how the Compliance API and your existing SSO cover the new cloud sessions.
3. 03 · Run one real task end to end: Have one person start a weekly status report or an inbound email triage summary as a chat and let it continue in the cloud. Check that connectors and skills work as before and the returned file is usable.

The short answers.