Claude Merges Chat and Cowork, Adds Docs and Slides Beta

Introduction

On September 16, 2026, Anthropic announced that Claude Cowork and chat are merging into one Claude. Until now, users picked a place for their work before starting: chat for conversation, Cowork for bigger and longer-running tasks, and Claude Design for visual output. In the new experience that choice disappears. According to Anthropic's announcement, Claude "can now figure out what a task needs," so what Cowork and Design can do is available from any conversation, with the context, skills, and connectors a user already has. The same announcement introduced Claude Docs and Claude Slides and brought Claude Design inside conversations. The rollout starts with Pro and Max plans on web, desktop, and mobile over the coming weeks. For regular Claude users, the change matters because it removes a routing decision that Anthropic says people found frustrating, and it puts agentic task handling in the conversation they already use.

Feature Overview

One conversation for quick questions and long tasks

Anthropic's blog explains the reasoning directly. It built Cowork as a separate place for bigger work and Design for visual work; people used both, and "told us the frustrating part was deciding where a task belonged." Work started in one also did not carry into the other. Under the merged model, a user describes the outcome they want and Claude works through the steps on its own, including searching the web, reading files, and running code, according to the Help Center. A quick question still gets a quick answer, and several tasks can run at the same time. More involved tasks keep running in the cloud even after the laptop is closed, although tasks that use files or apps on the user's computer need Claude Desktop open.

Claude Docs, Claude Slides, and Design inside the conversation

Ask for a document and, in Anthropic's words, "you and Claude write it together." Ask for a presentation and Claude drafts the slides. Results can be edited directly, presented straight from Claude, or downloaded as PowerPoint or PDF. Anything made with Design, Slides, or Docs lives at one shareable link that can be opened on a phone. Users can select an element and move it, or tell Claude what to change. All three are in beta on paid plans, and Enterprise admins choose when to turn them on. Standalone Claude Design, which Anthropic launched in April 2026, keeps working as before.

Connected apps, local access, and scheduling

The Help Center lists the capabilities that now sit in the default conversation: connected apps such as Google Drive, Gmail, Microsoft 365, and Slack; folder access in Claude Desktop; browsing through the built-in browser or Claude in Chrome; computer use, in beta on Pro and Max plans; scheduled recurring tasks that can run in the cloud; and skills and plugins. A task started at a desk also shows up in Claude Mobile, where the user can follow progress, answer Claude's questions, and redirect the work.

A permission setting for check-ins

A setting in the message box controls how independently Claude works. In Manual mode, the default, "Claude asks before it takes actions," and the user decides whether to allow each one. In Auto mode, Claude keeps working without stopping to ask about each step, "and automated safety checks run before it takes an action." The blog sums up the intent in one line: "You keep the final say."

Usability Analysis

Anthropic's own example shows the workflow it is aiming for. A weekly report is due at noon. Before heading out, the user asks Claude what moved in the pipeline last week and to "flag anything that slipped, and put the highlights in five slides." Progress can be checked from a phone on the way in, the report arrives as a doc, the slides can be downloaded as PowerPoint, and the whole job can be scheduled to run every Monday. A customer quote in the post, from Senior Economist Andrew Keller, describes Claude pulling cases from his legal research database, reading them, working out which other cases he might need, and downloading them into a folder for his review.

The migration is designed to be low-friction. Existing Cowork chats, projects, artifacts, connectors, skills, and files carry over, and the model picker and the "Code" tab stay where they were. There is no web search toggle anymore, since Claude searches when it helps, and Research is reached through /deep-research or the "+" button. Nothing needs to be switched on; accounts receive the change gradually, so two users on the same plan may see it at different times.

Two points deserve attention before the switch arrives. Once an account has the new experience, it cannot go back to separate "Chat" and "Cowork" options. And everything counts toward the plan's usage limits: longer agentic tasks generally use more than a quick question, and the Help Center notes that during the rollout, usage "may be measured slightly differently" for accounts with and without the new experience.

The Help Center also lists current gaps. "Add from GitHub" is not supported, a conversation cannot be branched from an earlier point, Incognito chats open in the previous experience without file creation or code execution, search does not include older Cowork tasks, and Dispatch is not available to new users.

Pros & Cons

Strengths

• Users no longer need to decide up front whether a task belongs in chat or Cowork.
• Docs, Slides, and Design output share one link that works on a phone and exports to PowerPoint or PDF.
• Existing Cowork data carries over, and familiar controls such as the model picker and the Code tab stay put.
• Manual approval is the default, so Claude asks before acting unless the user opts into Auto.

Limitations

• The change is one-way for each account.
• Several functions are missing at launch, including Add from GitHub, conversation branching, and file work in Incognito chats.
• Docs, Slides, and Design are beta features on paid plans, and Team and Free plans have no announced date.
• Longer agentic tasks draw more heavily on usage limits than quick questions.

Outlook

Folding Cowork into chat follows Anthropic's August 25, 2026 update, which unified memory across chat and Cowork. With cloud execution, scheduled tasks, and the permission setting now living in the default conversation, the line between a chat assistant and an agent workspace becomes a routing decision Claude makes rather than one the user makes. The practical test will be how well that routing works: whether Claude reliably judges when a request needs a multi-step task and when it needs a short answer, and how usage limits hold up once longer tasks start from ordinary conversations. Team and Free plans "will follow soon," per Anthropic, and Enterprise organizations have a notice period of at least 30 days before anything changes.

Conclusion

This update is a product consolidation rather than a new model: Anthropic is moving Cowork and Design capabilities into the conversation people already use and adding Docs and Slides in beta. For Pro and Max subscribers who split work between chat and Cowork, it removes friction and keeps existing data intact. Users who depend on GitHub imports, conversation branching, or file work in Incognito chats should review the listed limitations, and heavy users should expect longer tasks to consume more of their plan.

Editor's Verdict

Claude Merges Chat and Cowork, Adds Docs and Slides Beta earns a solid recommendation within the Claude space.

The strongest case for paying attention: the single conversation removes the need to decide up front whether a task belongs in chat or Cowork. That alone raises the bar for what readers should expect in this space. Reinforcing that, a shared link for Docs, Slides, and Design output makes results viewable and editable on a phone, with PowerPoint and PDF export — practical value rather than just headline appeal. The broader signal worth registering is straightforward: the merge removes the step of choosing between chat and Cowork, a decision Anthropic says users found frustrating because work started in one did not carry into the other. On the other side of the ledger, one constraint is real rather than a marketing footnote: the switch is one-way — once an account has the new experience, it cannot go back to separate Chat and Cowork options. It should factor into any serious decision. Layered on top of that, several functions are missing at launch, including Add from GitHub, conversation branching, file creation in Incognito chats, and search over older Cowork tasks — which narrows the set of teams for whom this is an obvious yes.

For Anthropic and Claude users, alignment-focused teams, and developers already invested in the Claude ecosystem, this is a serious evaluation candidate, not just a curiosity to bookmark. For everyone else, the safer posture is to monitor coverage and revisit once the use cases that matter to your team are demonstrated in the wild.