Anthropic has retired the wall between Claude’s chat experience and its Cowork agent workspace, merging both into a single home screen on the Windows desktop app and the web. The change, announced on July 7, 2026, lets you pick between a traditional back-and-forth conversation and an autonomous assistant that reads, writes, and creates files on your PC—all from the same message box.
What actually changed
Until now, Claude users who wanted to ask a question and users who wanted to hand the AI a multi-step task were forced into separate tabs. Chat handled prompts and replies; Cowork handled agentic assignments like building a report or cleaning up a folder. That architectural split is gone. When you launch the Claude desktop app for Windows or open the web interface, you will now see a single starting point where you choose Chat or Cowork mode before you begin typing.
Projects, artifacts, and conversation memory persist across both modes. That means a brainstorming session in Chat can seamlessly feed into a Cowork task without rebuilding context. Anthropic says this unified design makes it easier to move from planning in a conversation to handing off the actual work to an agent.
The distinction between the two modes remains significant, however. Chat is the conventional prompt-and-response engine: it drafts text, answers questions, and helps with ideation. Cowork acts more like an autonomous employee. It can work with selected local files, use tools, carry out multi-step assignments, and generate final outputs—documents, spreadsheets, presentations—for your review.
What it means for Windows users
For anyone running Claude on a Windows machine, the desktop app is the vehicle that unlocks Cowork’s most powerful feature: local file access. The web and mobile versions of Cowork (which began rolling out in beta alongside the interface update) can start and monitor cloud-run tasks, but they cannot reach the files on your hard drive. The desktop app can—if you grant it permission.
When you switch to Cowork mode inside the Windows app, you can designate specific folders for the assistant to work in. It can then read, edit, and create files inside those folders. This opens up a new class of on-device automation that was previously out of reach for a ChatGPT-style interface: organizing documents, generating reports from spreadsheets stored locally, compiling research from a folder of PDFs, or performing routine file cleanup.
Cowork tasks can also continue running after you close your laptop. Anthropic says that scheduled jobs execute without your device needing to be online, and that questions requiring human decisions are pushed back to you for approval. The assistant logs which files it opened, which tools it used, and what choices it made, giving you a way to review its work.
For home users and power users, the immediate win is delegation. A to-do list that once required manual attention—compiling quarterly expenses, extracting data from a set of CSVs, converting a batch of images—can now be handed to an agent that sees your local files.
For IT administrators, the picture is more nuanced. Cowork’s ability to touch local data, browser sessions, and connected SaaS services means the same security considerations that apply to any tool granted local access apply here too. Anthropic states that Cowork is limited to the folders and tools a user explicitly selects, and that file deletion requires user approval. Its “computer use” functions, a research preview that allows Claude to interact with applications, request permission before taking any action.
Those safeguards reduce risk, but they do not eliminate the need for policy controls. Organizations handling sensitive documents, shared network folders, regulated data, or accounts with broad connector permissions should evaluate how Cowork fits into their existing data governance.
A critical limitation for enterprise shops: as of this writing, Anthropic’s product documentation says that Cowork activity is not captured in audit logs or the Compliance API. Admins who rely on those systems for monitoring and retention should treat that as a deployment blocker, not a footnote. The company says enterprise administrators can disable Cowork outright and control access through role-based settings, which is the prudent path for most managed environments until comprehensive audit capabilities ship.
How we got here
The roots of this release trace back to Anthropic’s project capabilities, first introduced in 2024. Those earlier features let users organize conversations around specific goals. Cowork workspaces, which appeared later in a separate tab, added the ability to give Claude persistent context and tools. The announcement on July 7, 2026, accompanied by a detailed post on Threads, acknowledged that “projects and artifacts now live together across Chat and Cowork,” formalizing a marriage that had been in the works for months.
The rollout was staggered. Anthropic first publicized the update via social channels and its blog, then the web and mobile beta began appearing to paid users, initially prioritizing Max plan subscribers, according to a Crypto Briefing report from July 18 that summarized the features. The company has not yet announced a date for general availability of the beta versions, but the desktop app with the unified interface is available now for Windows and Windows on Arm systems.
What to do now
If you want to try Cowork on your Windows PC, take these steps:
- Download the Claude desktop app from Anthropic’s site if you haven’t already. The unified interface is available in the latest version; there is no separate download for Cowork.
- Start a Chat as you normally would, then select “Cowork” from the mode picker in the message box.
- Grant folder access when prompted. Choose folders explicitly—create a dedicated workspace directory rather than allowing access to your entire user profile.
- Be mindful of usage limits. Anthropic warns that agentic Cowork tasks consume your monthly quota faster than ordinary chats. If you’re on a paid plan, check your account settings to see your remaining allowance.
Enterprise administrators should:
- Review role-based access controls and consider disabling Cowork for groups that don’t need it until audit logs are available.
- Audit connected integrations (SaaS apps, cloud storage) that Cowork could potentially reach through your organization’s Claude account.
- Monitor the status of the Compliance API for updates that add Cowork activity visibility.
For mobile or browser-only scenarios, the Cowork web beta—accessible by starting a task from the web interface and letting it run in the cloud—can be a handy complement, but it will not read files stored on your PC. To integrate local documents, use the desktop app.
What to watch next
The unified interface is here, but Cowork itself is still labeled beta and rolling out progressively. The real milestone for Windows users will come when the agentic mode exits preview and gains full parity across all platforms, including the same local file capabilities on Windows on Arm that the standard desktop app already provides. And for enterprises, the lack of audit logging is a clear signal that Anthropic still sees this as a product for early adopters, not heavily regulated environments. Once logging and compliance features land, expect organizations to start building the same kind of governance around AI assistants that they already apply to other local-file tools. Until then, Windows users willing to carefully choose which folders to share will find a capable, file-aware agent living right next to their chat window.