Cowork and chat are now one Claude: what changed and what you need to do
In brief
On September 16, 2026 Anthropic merged Cowork into Claude. The file handling, long-running work, and artifact building that used to require opening Cowork are now available from any conversation. Nothing moves, nothing is deleted, and there is no migration step — but the habit of picking a surface before you start is now the thing to unlearn.
Contents
Until September 16, 2026, using Claude meant answering a question before you asked your actual question: which Claude? Chat for conversation and quick drafts. Cowork for work that touched files, ran long, or produced something you would hand to someone else. Claude Design for visual work. Three surfaces, three sets of habits, and a recurring moment of friction where you started somewhere, realized it was the wrong place, and copied your context across.
Anthropic removed that question. Cowork and chat are now one product. What Cowork and Design could do is available from any conversation, with the skills, connectors, and project context you already had.
What actually changed
One surface. There is no separate Cowork app to open and no mode to switch into. You describe what you want; Claude works out whether it needs to read files, run for twenty minutes, spin up parallel work, or just answer you in a sentence.
Nothing moved. Your chats, projects, artifacts, connectors, and skills are where you left them. Anthropic's phrasing is that when you open the app you pick up where you left off. There is no migration, no export, no re-connecting of connectors.
Design still works standalone. If you use Claude Design on its own, it keeps working as it did. It is now also reachable from inside a conversation.
Work lives at one link. A piece of work is a shareable link you can open on your phone, check on while it runs, and come back to. That was already how Cowork behaved; it now applies to everything.
Three new things shipped alongside it — Claude Docs, Claude Slides, and Design-in-conversation — all in beta on paid plans. Those are covered separately in Claude Docs and Claude Slides.
What did not change
The merge is an interface change, not a capability change. If a task did not work in Cowork last week, merging Cowork into chat does not make it work. Specifically:
- Connector permissions still inherit from the source system. Merging surfaces does not grant Claude access it did not have.
- Skills still need to be written, tested, and maintained. A badly scoped skill fails the same way from a chat box as it did from Cowork. The failure patterns are in the Cowork skills graveyard.
- Long-running work still runs on Anthropic's infrastructure with the same limits and the same need to check on it.
Rollout, by plan
| Plan | When |
|---|---|
| Pro and Max | Rolling out now on web, desktop, and mobile over the coming weeks |
| Free and Team | After Pro and Max |
| Enterprise | 30+ days advance notice before anything changes |
The Enterprise notice period is the part worth flagging internally. If you administer a Claude Enterprise org, you get at least 30 days before the merged experience arrives, and Enterprise admins choose when to turn on the Docs, Slides, and Design betas. That is a window to update internal documentation, not a reason to ignore it.
What to do this week
If you are an individual user: stop picking a surface. The concrete behavior change is that you should start every task in the same place and let Claude escalate. If you have been keeping a mental rule like "anything with a spreadsheet goes in Cowork," delete the rule.
If you run a team: your onboarding docs are now wrong. Anything that says "open Cowork to do X" needs rewriting to "ask Claude to do X." This is small but it matters — new users follow the documented path, and a documented path through a surface that no longer exists as a separate thing is how people conclude the tool is confusing. The general approach is in rolling Claude out to your team.
If you administer Enterprise: decide now whether Docs, Slides, and Design go on at launch or after a pilot, and decide who makes that call. You have the 30-day notice; use it to pick a small group rather than flipping it on for everyone on day one.
If you have been tracking adoption: your metrics baseline breaks. Any measurement that counted "Cowork sessions" as a proxy for serious work is about to stop meaning anything, because that work now happens in conversations that look like every other conversation. Re-anchor on outcomes rather than surface. Measuring Cowork adoption covers which numbers survive this kind of change.
The thing this is actually fixing
The two-surface design assumed you knew, before you started, how big a job was. You usually do not. A question turns into a document. A quick lookup turns into a four-hour analysis. Under the old model, discovering that mid-task meant restarting somewhere else with your context left behind.
Merging the surfaces means the product finds out how big the job is at the same time you do. That is the whole change. Everything else — Docs, Slides, Design in conversation — is a consequence of having one place for work to grow into.