What happened
Anthropic’s Help Center announcement says it is introducing a Claude experience that removes the distinction between Cowork and chat. Instead of choosing which product to use before starting, a user can describe the desired work in a conversation; Claude can decide which tool to use. The company says the experience can cover quick answers as well as research, reports, spreadsheets, and presentations, returning finished files for further editing.
The rollout is gradual. It starts with Pro, Max, and Ultra plans on web, desktop, and mobile. Team plans have the experience in beta, while Enterprise accounts can use it where “Chat and Cowork unified” is turned on. Anthropic says accounts on the same plan may receive it at different times and no action is required to enable it. Once an account moves to the new experience, it cannot switch back to separate Chat and Cowork options. Chats, tasks, projects, and settings move with the account.
The announcement describes tasks that can search the web, read files, run code, and assemble results. More involved work can continue in the cloud after a user closes a laptop or leaves the page. Tasks that use files or applications on the user’s computer require Claude Desktop to remain open. Connected apps such as Google Drive, Gmail, Microsoft 365, and Slack can be used during a task. Claude can also work with folders in Claude Desktop, browse through its built-in browser or Claude in Chrome, and use computer controls; computer use is in beta on Pro, Max, and Ultra. Local-file, browser, and computer-use access works only while Desktop is open, and Anthropic says Claude asks by default before permanently deleting files.
Permission controls are conversation-wide. Auto, the default for Pro, Max, Ultra, and Team, lets Claude continue without asking at each step, with automated safety checks before actions. Manual, the Enterprise default, asks the user before actions. Anthropic says users can change the setting, stop a task, or redirect it, and advises staying close and reviewing work with real consequences. The company says longer agentic tasks generally use more plan usage than quick questions, and usage may be measured slightly differently during rollout. It gives no separate price for the unified experience.
The interface also changes where some work lives. Chats and longer tasks share Recents; projects, memory, and instructions apply across conversations. Anthropic says web search no longer has a toggle and is used when Claude judges it helpful; Research can be started with /deep-research or the plus button. Existing Cowork tasks, projects, connectors, skills, artifacts, and files carry over. The announcement lists limits: adding from GitHub and conversation branching are unsupported; incognito chats remain in the previous experience and cannot create files or run code; search excludes older Cowork tasks; and Dispatch is unavailable to new users.
What the archive adds
New Runtime’s earlier coverage on 2026-08-29 described Claude Memory as shared and user-controlled across Chat and Cowork, a related step toward continuity across work modes. This announcement is a new event: it unifies the interaction surface and documents migration behavior, permissions, and limitations. The earlier note does not establish that every memory detail is unchanged in the new experience.
Trend signal
This supports AI-native organizations move toward review and orchestration: the announcement frames the user as specifying an outcome while Claude handles steps, with permission settings and human review remaining part of consequential work. It is a product-level signal, not evidence that organizations have changed their operating models or that the workflow reliably completes tasks without supervision.
Why now
Anthropic says the experience is rolling out in stages, with no action required from users. It does not explain why the transition is happening now or give a completion date for the rollout.
Connections to other events
New Runtime’s earlier coverage on 2026-11-04 described Anthropic making Chat and Cowork a unified experience for Enterprise plans across web, desktop, and mobile. The Help Center announcement broadens the picture with plan-by-plan rollout details, task behavior, permission defaults, and known limitations. The two accounts are consistent on the direction of travel, but the new page specifies that Enterprise availability depends on the unified option being turned on.
Why it matters
For a team using Claude to produce work rather than just answer questions, one conversation can become the front door for tasks that reach into files, connected services, browsers, and desktop applications. That reduces the need to route a request manually between chat and a work mode, but it also makes the permission setting and review practice more consequential: the same conversation can span low-risk drafting and actions with real effects.
The migration is not a simple cosmetic update. Existing work carries over, but some controls and features move or remain unavailable, and a user cannot return to the separate modes once switched. Teams should treat rollout as a workflow change: verify instructions, understand where files and tasks now appear, and test the right approval mode before relying on long-running jobs. Anthropic’s own warning about usage also means teams should not assume a complex task costs like a short chat.
What happens next
- Anthropic will continue expanding the unified experience to eligible accounts. (3 months, 75%). Watch for: the Help Center stating that staged rollout has reached all Pro, Max, and Ultra accounts.
- Enterprise adoption will depend on administrators enabling unified Chat and Cowork. (6 months, 65%). Watch for: Anthropic documenting broader Enterprise availability or a changed default.
Limits and uncertainty
Anthropic does not give a rollout end date, account-level eligibility schedule, or separate price for the experience. It says usage can be measured slightly differently during rollout but does not quantify the difference. The announcement describes capabilities and defaults, not measured completion rates, error rates, or comparative productivity. It also does not establish how consistently Claude selects the right tools or how often human intervention is needed. These are company-described features and constraints, not independent evaluations.
Skill to build now
Before switching a team workflow, run one bounded task using the exact files and connected apps the team expects to use. Specify the desired deliverable and format, set Auto or Manual deliberately, and inspect the returned file and any actions taken. Then confirm where the task and files appear in Recents or Desktop storage, and record whether the task used more plan usage than a comparable quick question. This makes the migration test concrete without assuming that a unified interface changes the team’s approval obligations.
Reader takeaway
Claude’s Cowork capabilities are moving into the ordinary conversation, not disappearing: users can ask for a result and let Claude work across tools and files. The practical change is a single workflow with plan-dependent rollout and permission defaults. Check access, approval behavior, feature limits, and usage before making it the default for consequential work.