{"slug": "claude-chat-and-cowork-are-now-one-app-what-teams-should-do", "title": "Claude Chat and Cowork Are Now One App: What Teams Should Do", "summary": "Anthropic announced on September 16, 2026 that Claude chat and Claude Cowork are merging into a single app, with Pro and Max users getting the merged experience on web, desktop and mobile \"over the coming weeks\" while Team and Free plans \"will follow soon\" and Enterprise admins receive at least 30 days' notice before any change. The merge adds Claude Docs and Claude Slides in beta on paid plans and folds Claude Design into conversations, with chats, projects, artifacts, connectors and skills carrying over for Cowork users. By default Claude asks before taking an action, and users can instead have it check in only when something needs a closer look, a setting Anthropic says preserves the user's final say.", "body_md": "On September 16, 2026 Anthropic announced that Claude chat and Claude Cowork are merging into one app. Cowork was the separate place where Claude took on longer jobs in the background. Now a quick question and a report due at noon start in the same conversation, and Claude works out which kind of task it has been given.\n\nThis post is for the owner or team lead already paying for Claude. It covers what [Anthropic's announcement](https://claude.com/blog/cowork-is-now-claude) says, who gets it when, and the one decision the merge puts in front of every user: whether Claude asks before it acts. A disclosure: this blog is produced with Anthropic's models. We have kept to what the announcement states.\n\n1. 01Chat-only users do nothing.Anthropic says that if you mostly use chat, you do not have to do anything different, and there is nothing to turn on.\n2. 02Cowork users keep everything.Chats, projects, artifacts, connectors and skills carry over, according to the announcement.\n3. 03Docs, Slides and Design are beta on paid plans.Claude Docs and Claude Slides are new. Claude Design now works inside conversations. Enterprise admins choose when to turn the three on.\n4. 04The default is ask-first.Claude asks before taking an action unless the user switches to checking in only when something needs a closer look.\n\n## 01 — The releaseWhat changed\n\nAnthropic's explanation is that people used chat, Cowork and Design as three places and found the annoying part was deciding where a task belonged. Work started in one also did not carry into the others. Its answer is that \"Claude can now figure out what a task needs\", so the background work Cowork did and the visual work Design did are available from any conversation, using the context, skills and connectors the user already has.\n\nTwo products are new. Claude Docs lets you and Claude write a document together. Claude Slides drafts a presentation. Anthropic says you can edit directly, present from inside Claude, or download as PowerPoint or PDF, and that anything made with Design, Slides or Docs lives at one shareable link. If you use Claude Design on its own, it keeps working as before.\n\nThe announcement's example is a weekly pipeline report requested before leaving home, checked from a phone on the way in, and ready as a document plus five slides on arrival. The detail that matters for a team is the last one: the task can be scheduled for every Monday, and Claude then starts it without being asked.\n\n## 02 — DatesRollout by *plan*\n\nAnthropic gives windows, not dates. The table uses its wording.\n\n| Source: Anthropic, \"Claude Cowork and chat are now one Claude\", September 16, 2026. |  |  | \n|---|---|---|\n| Plan | Merged app | Docs, Slides, Design (beta) | \n|---|---|---|\n| Pro and Max | First. Web, desktop and mobile, \"over the coming weeks\", for existing and new users. Nothing to turn on. | In beta on paid plans | \n| Team | \"Will follow soon\". No date given. | In beta on paid plans | \n| Enterprise | Admins \"will hear from us at least 30 days before anything changes\" for their organisation. | In beta; admins choose when to turn them on | \n| Free | \"Will follow soon\". No date given. | Not stated for the free plan | \n\nFor a small business the practical reading is this. Individuals on Pro or Max may see the change any day, and the announcement describes no way to defer it. A Team workspace has an undated wait. Only Enterprise gets a guaranteed notice period.\n\n## 03 — The decisionAsk first or report after\n\nWhen chat and background work were separate apps, opening Cowork was itself a decision to delegate. With one app, that signal is gone, so the approval setting carries more weight. Anthropic describes it this way: by default Claude asks before taking an action, and a user who would prefer it to keep working can have it check in only when something needs a closer look. \"You keep the final say.\"\n\nThe announcement does not define what counts as an action or list exceptions. Until the help documentation is read against your own use, we suggest setting policy by task type, not by person.\n\n| Editorial recommendation. The setting and its default are as Anthropic describes them on September 16, 2026. |  |  | \n|---|---|---|\n| Task type | Setting | Why | \n|---|---|---|\n| Anything that sends, pays, deletes or publishes | Ask first (the default) | The result leaves your account and cannot be pulled back. One confirmation is cheap. | \n| Research, drafting, building a document or deck | Report after is reasonable | The output is a draft you will read before it goes anywhere. Interruptions cost more than mistakes. | \n| Scheduled recurring tasks | Ask first until three clean runs, then review | Nobody is watching a Monday 6 a.m. run. Earn the autonomy with a track record, and recheck when connectors change. | \n\nFor a sense of how ordinary users behave, a July 2026 survey found that 32% of US AI users have already let AI act for them at least once without a final sign-off. The figure and its caveats are in our [reference on what people let AI agents access](https://www.digitalapplied.com/blog/ai-agent-access-permissions-consumer-survey-statistics-2026). Expect some of your team to switch the default off on day one. Decide the rule before they do.\n\n## 04 — ChecklistWhat to review before it arrives\n\nThe merge means Cowork's abilities are reachable from any conversation, \"with the context, skills, and connectors you already have\". Access granted months ago for one project is now available to every chat. Three reviews are worth an hour:\n\n- **Connectors.** List which accounts each person has connected: mail, calendar, drive, CRM, finance tools. Remove any that were added for a finished project.\n- **Skills.** Check which skills are installed and who wrote them. A skill is a set of instructions Claude follows, so an outdated one produces outdated work at scale.\n- **Shared projects and links.** Documents and decks now live at shareable links. Agree who may share outside the company and whether client material belongs there during a beta.\n\nOur earlier [guide to Cowork plugins, connectors and tasks](https://www.digitalapplied.com/blog/claude-cowork-enterprise-plugins-connectors-tasks-guide) explains what each of those does. For the wider question of which permissions an agent should hold by default, see [default-deny versus default-allow](https://www.digitalapplied.com/blog/default-deny-vs-default-allow-agent-permissions).\n\nDocs, Slides and Design inside conversations are labelled beta. Treat exported PowerPoint and PDF files as drafts to check, especially numbers carried from a report into slides. Keep your existing document tools for anything contractual until the beta label is gone. Most office suites now offer similar AI drafting, so there is no urgency to move.\n\n## 05 — GapsWhat is not stated\n\nWe read the announcement on September 17 for four things a team would want and did not find them:\n\n- **Usage limits.** Nothing on whether background tasks, Docs or Slides draw on the same allowance as chat.\n- **Pricing.** No change is announced and none is ruled out.\n- **Dates for Team and Free.** Only \"soon\".\n- **Admin controls below Enterprise.** Enterprise admins choose when to enable the beta tools. The post does not say whether Team owners get the same switch.\n\nAnthropic points to its Help Center for the full capability list. Check there before you promise a client or a colleague a feature. If you want help setting sensible defaults for a team, that is part of our [AI transformation work](https://www.digitalapplied.com/services/ai-transformation).\n\n## 06 — Next stepDelegation is now the default surface\n\n### Write a three-line approval rule and review connectors\n\nBefore the update reaches your plan, agree three lines with your team: actions that send, pay, delete or publish stay on ask-first; drafting and research may run unattended; scheduled tasks earn autonomy after clean runs. Then spend an hour removing connectors nobody needs. Both jobs are small, and both are easier before the change than after.", "url": "https://wpnews.pro/news/claude-chat-and-cowork-are-now-one-app-what-teams-should-do", "canonical_source": "https://www.digitalapplied.com/blog/claude-chat-cowork-merge-docs-slides-what-teams-set", "published_at": "2026-09-16 00:00:00+00:00", "updated_at": "2026-09-17 14:25:59.058243+00:00", "lang": "en", "topics": ["ai-products", "ai-agents", "artificial-intelligence", "ai-tools"], "entities": ["Anthropic", "Claude", "Claude Cowork", "Claude Docs", "Claude Slides", "Claude Design", "Pro", "Enterprise"], "alternates": {"html": "https://wpnews.pro/news/claude-chat-and-cowork-are-now-one-app-what-teams-should-do", "markdown": "https://wpnews.pro/news/claude-chat-and-cowork-are-now-one-app-what-teams-should-do.md", "text": "https://wpnews.pro/news/claude-chat-and-cowork-are-now-one-app-what-teams-should-do.txt", "jsonld": "https://wpnews.pro/news/claude-chat-and-cowork-are-now-one-app-what-teams-should-do.jsonld"}}