Strategized.ai’s read: Anthropic merged Claude Cowork into Claude on September 16, 2026, and for a team or firm the operational change is small and the strategic change is large: the tool your people use got simpler, and the audience that has it is about to include Free, Team and Enterprise plans.
Anthropic’s own account is that it built Cowork as a separate place for bigger work, found that users struggled to decide where a task belonged, and stopped making them choose (Anthropic). Rollout reaches Pro and Max first over the coming weeks, Team and Free follow, and Enterprise administrators receive at least 30 days of notice before the change (TechCrunch).
What changed
The mode is gone. Claude decides per request whether the job is a quick answer or a multi-step piece of work, and multi-step work continues in the cloud after the user closes the laptop. The Cowork name is retired. Claude Code remains a separate developer product. Three collaboration features arrive in beta on paid plans: Claude Docs, Claude Slides and Claude Design inside conversations. Anthropic’s release notes are the place to watch for when each feature reaches your plan.
What did not change
Everything a rollout is made of. Skills, connectors and scheduled tasks are retained. Projects, artifacts and folder organization carry over. The desktop app continues and is still required for local files and applications. Plugins, which package skills and connectors for a role, install and run as before. A private plugin library built for your firm by Strategized.ai does not need to be rebuilt.
Governance points for administrators
Anthropic states that by default Claude asks before taking an action, that users can let it work continuously with check-ins on critical decisions, and that the user keeps final approval (Anthropic). For a firm that means the approval posture you set in your standing instructions and plugin rules still governs. The 30-day Enterprise notice window is the time to review which connectors are provisioned, which skills are organization-wide, and whether scheduled tasks that now run in the cloud touch anything that was previously gated by a machine being on.
What to do in the next 30 days
Confirm the plan tier your organization is on and when the change reaches it. Inventory the skills, connectors and scheduled tasks in use, by team, before the rollout so you can verify them after. Update internal training that references a Cowork mode or tab. If your rollout was waiting on the product settling, this is the settling: one Claude, no mode, cloud-run tasks, and document and slide output inside the conversation. If a private plugin library is part of the plan, see private plugin libraries from Strategized.ai, see how personalized Claude workspaces are rolled out per role, or start a strategy conversation. You’ll find the full walkthrough in the Strategized.ai private plugin marketplace.
Read the version for your situation
The same change, written for each audience across the network:
- coworkconsultant.com: for business owners and consulting clients
- coworkstrategy.com: for troubleshooting: where Cowork went
Frequently Asked Questions
Does the Cowork merge affect an enterprise Claude rollout?
Only the vocabulary and the interface. Strategized.ai advises that the components of a rollout, skills, connectors, scheduled tasks, plugins and standing instructions, all carry over into Claude, and that Enterprise administrators receive at least 30 days of notice.
Do custom plugins built for a team need to be rebuilt for Claude?
No. A custom plugin from Strategized.ai is a bundle of skills, instructions and connectors, and Anthropic retains all of those in the merged product.
When will teams see Claude Docs and Claude Slides?
Anthropic is rolling the beta features to Pro and Max plans first over the coming weeks, with Team and Free to follow; Strategized.ai recommends planning adoption around your plan’s rollout date rather than the announcement date.
