Claude Cowork and chat are now one Claude. Docs and Slides have also been introduced at the same time.

2026-09-17
28min read
Updated: 2026-09-18
cowork-is-now-claude.webp

Table of Contents

Hello. On September 16, 2026 (US time), Anthropic announced "Claude Cowork and chat are now one Claude." The announcement explains that Cowork, which previously existed as a separate workspace, is being eliminated and integrated into regular conversations (chat).

At the same time, two new features, Claude Docs and Claude Slides, were introduced, and Claude Design, which was previously a standalone tool, can now be used directly within conversations. While this is not a model announcement, it is a change that directly affects the experience of how we use Claude, so I would like to organize the details here.

In this article, based on the official announcement, we will look at what is changing, how it is changing, and what it means for those who use Claude Code.

Cowork and chat become one Claude

The core of the announcement is very clear. Previously, Cowork was provided as a "separate space for larger tasks," but they are discontinuing that and consolidating everything into a single Claude.

Whether you are asking a quick question or handing over an entire report that you want finished by noon, everything is completed within the same conversation. The official announcement highlights the ability to step away after handing over a task, writing that "Claude keeps working even after you close your laptop."

In previous Anthropic announcements, it was standard to list three destinations when showing where features were available: "Claude.ai, Claude Code, and Claude Cowork." In the Opus 5 announcement in July, these three were listed alongside the API as available platforms, and in the Fable 5.1 announcement on September 1, the default effort values were explained separately as High for Claude Code and Medium for Claude Cowork and Claude.ai. With this integration, this list is likely to get a bit shorter.

The reason for the integration: "Forcing users to decide where to work"

The reason for the integration is also clearly stated.

Cowork was created as a space for larger tasks, and Design was built for visual work. While both were being used, what users found frustrating was being forced to decide "which one should I use for this task?" Furthermore, work started in one could not be carried over to the other.

Therefore, the decision this time was to "stop making users choose." Claude will determine what is needed for a task, making what was possible in Cowork and Design available from any conversation. Moreover, it is explained that this will be done in a way that allows users to use their existing context, skills, and connectors as they are.

I think the defining characteristic of this announcement is that it is not about adding features, but rather about reducing the number of places to work.

Newly introduced Claude Docs and Claude Slides

On the same date, two new features, Claude Docs and Claude Slides, were released.

Docs allows you to write documents collaboratively with Claude. Slides lets you ask for a presentation, and Claude will draft the slides for you. In both cases, you can edit the finished product directly, or present directly from Claude. You can also download them as PowerPoint or PDF files.

Both are provided as betas in paid plans. For Enterprise, administrators can decide when to enable them.

Claude Design is now available within conversations

Claude Design was previously offered as a standalone tool. Now, it will also function within conversations.

If you are using Design as a standalone tool as before, you can continue to use it without any changes. The standalone version is not being taken away, so you can rest assured on that front.

Outputs are consolidated into a single shared link

Creations made with Design, Slides, and Docs are consolidated into a single shared link, which can also be opened from smartphones.

Two ways of editing are also shown: you can select elements and move them yourself, or you can tell Claude to "change this here." This means you can go back and forth between manual editing and verbal requests on the same screen.

Example of usage shown by the official announcement

A specific workflow is introduced in the announcement. To summarize, it is a scenario like this:

Suppose you have a weekly report deadline at noon. Before leaving, you ask Claude what ran in the pipeline last week, and then ask it to: summarize it in the usual format, flag anything that is delayed, and turn the highlights into a 5-slide presentation. If anything is unclear, Claude will ask you questions.

On your commute to work, you can check the progress from your smartphone. By the time you arrive at your desk, the report is completed as a document with comments from colleagues, and the slides are ready to be opened, adjusted, and downloaded. Since both were generated from the same conversation, the content of the slides is aligned with the report from the start.

You manually correct any sentences you are concerned about, leave comments for Claude on the slides, and share them. Furthermore, if you set it to "run every Monday," Claude will start working on the report from then on without you having to ask.

You can choose how far Claude proceeds on its own

You can also choose how the work proceeds.

By default, Claude will ask for confirmation before taking any action. However, you can switch to a mode where it "proceeds without stopping every time, and only prompts you when you should take a close look." The official announcement concludes by adding, "you retain final judgment."

This way of thinking is very similar to the permission design in Claude Code. It is a format where the user decides whether to confirm everything or delegate to some extent.

Existing work for Cowork users remains intact

Information about the transition is also provided.

Those who usually focus on using chat do not need to do anything special. The guidance is simply to try handing over reports or slides that you would normally create yourself when you want to delegate a larger task.

For those who were working in Cowork, all chats, projects, artifacts, connectors, and skills will remain in their original places. You will just open the app and resume from where you left off.

Note that the fate of the Cowork brand name itself is not mentioned in the body of the official blog post. However, according to a VentureBeat article on the same day, Anthropic explained that the Cowork name will eventually disappear. While you might see it during the transition, it will ultimately not remain.

Rollout starts with Pro and Max

The rollout order is as follows:

  • First, it will be rolled out to the Pro and Max plans over the coming weeks.
  • It applies to the Claude app on web, desktop, and mobile.
  • It applies to both existing and new users, with no activation required.
  • Team and Free plans will follow shortly after.
  • For Enterprise, administrators will be contacted at least 30 days before any changes are made to the organization.

All three—Docs, Slides, and Design—are provided as betas in paid plans. It is noted that a list of features is compiled in the Help Center.

Claude Code is not included in this announcement

For those who use Claude Code on a daily basis, this is probably the most concerning part.

The targets mentioned in this announcement are the Claude app on web, desktop, and mobile. Claude Code does not appear in the body of the official blog post.

And we have a clear answer on this. According to the aforementioned VentureBeat article, Anthropic explained that Claude Code is for developers interacting with codebases from terminals or IDEs, and is not subject to this integration. It seems there is no need to worry about terminal-side usability changing because of this.

This was also confirmed from the screen. In the desktop app in my environment, the entry points are split into two: "Chat" and "Code." It is visually apparent that only the "Chat" side has been consolidated, while "Code" remains as a separate entry point as before.

However, I feel the direction is similar. Handing over work from a conversation, having it proceed while you are away, and confirming only when necessary. Setting up scheduled executions. These are concepts already familiar in Claude Code. You could view it as the app side moving closer to that approach.

What caught my attention

What I personally found interesting was that this was not an announcement about "adding features," but rather about "reducing choices."

When Cowork was released, to be honest, I couldn't quite grasp how to use it differently from chat. Even if told it was for larger tasks, I had to decide for myself what counted as "larger." In the end, I barely used it and got by with regular conversations and Claude Code. Reading the explanation this time, I realized that quite a few people felt the same way, which makes a lot of sense to me now.

Another point that interests me is being able to see the progress from a smartphone. I regularly interact with Claude Code from the outside, and I have two ways of doing so. One is via a Telegram channel, and the other is Remote Control. With Remote Control, I can take the session I was running at my desk directly onto my smartphone, so I often use it when I want to check the continuation while on the go. Being able to see things progressing while away is actually incredibly convenient when you try it. If the app side becomes capable of doing the same, I think I will find myself using it more often.

As for Docs and Slides, since they are still in beta, I can't say much until I actually try them. Especially for slides, I think the evaluation will depend on whether you can manually correct them when fine adjustments are needed. Since it says you can select and move elements, I look forward to seeing how that works.

Summary

To summarize this announcement:

  • Claude Cowork and chat are integrated to become one Claude.
  • Claude Docs and Claude Slides are newly introduced, and Claude Design becomes available from within conversations.
  • All three are provided as betas in paid plans, and for Enterprise, administrators will decide on activation.
  • Created documents, slides, and designs are consolidated into a single shared link.
  • You can choose whether to confirm every step or delegate to some extent.
  • Rollout starts with Pro and Max over the coming weeks, with Team and Free to follow.
  • Work done in Cowork remains intact. The Cowork name itself is expected to disappear eventually.
  • Claude Code is not subject to this integration.

I think eliminating the hassle of choosing where to work is a genuinely welcome change. It has already rolled out to my environment, and the desktop app now has only two buttons: "Chat" and "Code." The "Chat" button is accompanied by "Chat & Cowork," making it visually clear that they have been integrated here. For now, I plan to try handing over my weekly summary once. If I discover anything after trying it out, I will write about it again.

Reference Links

Share this article

Related Articles