Anthropic shipped Claude Cowork for Windows on February 10, 2026, exactly 29 days after the macOS launch. That gap mattered. Roughly 70% of desktop users run Windows, and for the first month, Cowork was a macOS-exclusive product in a market where most enterprise machines run Windows 10 or 11. The release brings file access, plugin execution, MCP connectors, and sandboxed multi-step task execution to the platform that dominates corporate IT.
This is not just a port. The Windows version launched with the same 11 agentic plugins, the same Opus 4.6 backbone with 1 million tokens of context, and the same containerized sandbox architecture. But it also introduced platform-specific restrictions around file system access that split user opinion on Reddit within hours of launch.
What Shipped: Feature Parity in Practice
Anthropic used the phrase “full feature parity” in the launch announcement, and the claim holds up. Every capability that macOS users had on January 12 works identically on Windows as of February 10.
The Core Agent Loop
Cowork runs on Claude Opus 4.6, the same model that powers Claude Code. It reads local files, writes new ones, executes multi-step business tasks, and coordinates with external services through MCP connectors. The 1 million token context window lets it hold entire project folders in memory during a session, something that separates it from chatbot interfaces where every conversation starts from scratch.
On macOS, the agent runs inside a containerized Linux VM built on Apple’s VZVirtualMachine framework. On Windows, Anthropic replaced this with its own sandboxing layer that achieves the same isolation guarantees. Boris Cherny, Anthropic’s head of Claude Code, described the approach: “We use a virtual machine under the hood. This means you have to say which folders Claude has access to. And if you don’t give it access to a folder, Claude literally cannot see that folder.”
The practical result: Cowork on Windows can create spreadsheets, rewrite documents, process CSV exports, generate reports, and chain these tasks together, all without the user switching applications.
Plugin Ecosystem: All 11 on Day One
The 11 agentic plugins Anthropic released on January 30 shipped simultaneously on Windows. These cover:
- Legal: contract review, NDA triage, compliance checks
- Sales: CRM preparation, call summaries, pipeline analysis
- Finance: spreadsheet analysis, report generation
- Marketing: content planning, campaign analysis
- Data analysis: CSV processing, pattern detection
Each plugin connects through Anthropic’s Model Context Protocol (MCP), the open standard for AI-to-tool communication. On Windows, MCP connectors work the same way: the agent calls external tools through a standardized interface, and each tool responds with structured data the agent can reason about.
Global and Folder-Specific Instructions
A feature that launched quietly alongside the Windows release: users can now set persistent instructions that Claude follows in every Cowork session. You can define global rules (“always use metric units,” “follow our company style guide”) and folder-specific rules (“in this project, use Python 3.12 conventions”). Reddit developers called this out as particularly useful for maintaining context across sessions without re-explaining project conventions each time.
The File Access Restriction Debate
The Windows launch was not universally celebrated. Within hours, users on Reddit and GitHub flagged that Cowork on Windows restricts file access to the user’s home directory. Developers who store code on secondary drives (D:\projects, C:\git) found that Cowork refused to see those directories.
The restriction is deliberate. Anthropic’s sandbox resolves symlinks and junctions to their real paths, then blocks anything outside %USERPROFILE%. A user who created a symlink from C:\Users\name\code pointing to D:\projects found it rejected. The sandbox caught the redirect and denied access.
Why Anthropic Made This Choice
The safety argument is straightforward. When an AI agent can read and write files, limiting the blast radius matters. On macOS, the VZVirtualMachine framework provides natural boundaries. On Windows, where drive letters, network shares, and junction points create a more complex filesystem topology, Anthropic chose to draw a hard line at the home directory.
One Reddit commenter put it bluntly: “To be fair, seeing how many people nuked themselves with Claude Code, it is much safer to limit people to reduce the collateral damage.”
The counterargument is equally valid. Professional developers on Windows routinely work outside their home directory. Enterprise deployments often mandate code on dedicated drives for backup and permissions reasons. A desktop AI agent that cannot access a developer’s actual project files is, for those users, a tool with a significant gap.
The Workaround Situation
As of the launch, there is no official override. Anthropic’s GitHub issue tracker shows multiple open requests for configurable directory access. The likely resolution is a permissions dialog that lets users explicitly grant access to additional paths, similar to how mobile apps handle storage permissions. But at launch, the restriction stands.
How Cowork on Windows Fits the Bigger Picture
The Windows launch changes the competitive dynamics of the desktop AI agent market. Before February 10, Cowork was a Mac-first product competing against tools that already ran everywhere. Now it is a cross-platform agent with consistent capabilities.
The Platform War Context
Microsoft shipped Windows 365 for Agents in early 2026, giving AI agents their own cloud PCs. OpenAI launched Frontier as an enterprise orchestration platform. Google released Gemini extensions for Chrome OS. Every major platform player now has a desktop agent strategy.
Anthropic’s move is different because Cowork runs locally. The agent operates on your machine, reads your files, and uses your credentials to access external services. There is no intermediary cloud layer that sees your documents. For industries with strict data residency requirements (legal, healthcare, finance in the DACH region), this architecture is not just a technical choice. It is a compliance enabler.
Enterprise Adoption Signals
The combination of Windows support and MCP-based plugin architecture positions Cowork for enterprise rollouts where macOS-only was a dealbreaker. Many corporate environments standardize on Windows. IT departments that evaluated Cowork in January and rejected it for platform reasons now need to reassess.
The 11 plugins are also relevant here. They are open-source on GitHub, which means enterprise teams can audit the code, fork it for internal use, and build custom plugins using the same MCP interface. This is a fundamentally different model from closed-source enterprise AI platforms that require vendor integration engagements.
What to Expect Next
Anthropic has not published a Windows-specific roadmap, but the pattern from the macOS side suggests what is coming. The Projects feature, spotted in preparation on desktop, would give Cowork persistent project-level context that survives across sessions. Dispatch, Anthropic’s mobile companion for Cowork, launched on March 17 and lets users initiate and monitor desktop Cowork tasks from a phone.
The file access restriction will almost certainly be relaxed. The GitHub issues have enough traction, and the fix (an explicit permissions dialog) is well understood. The question is when, not if.
For the 70% of desktop users who were locked out for the first month: Cowork on Windows is the real thing. Same model, same plugins, same sandbox architecture. The only open question is whether Anthropic will trust Windows users to manage their own file permissions before enterprises start deploying it at scale.
Frequently Asked Questions
Is Claude Cowork on Windows the same as the Mac version?
Yes. Anthropic launched Cowork on Windows with full feature parity. All 11 plugins, MCP connectors, file access, and the Opus 4.6 model with 1 million token context work identically. The only difference is the sandboxing implementation and tighter file access restrictions on Windows.
Why can’t Claude Cowork access files outside my home directory on Windows?
Anthropic restricts Cowork’s file access to the user’s home directory (%USERPROFILE%) as a safety measure. The sandbox resolves symlinks and junctions to prevent circumvention. This limits blast radius if the agent makes an error, but it also blocks developers who store projects on secondary drives.
What plugins does Claude Cowork support on Windows?
All 11 agentic plugins are available on Windows from day one: legal (contract review, NDA triage), sales (CRM prep, pipeline analysis), finance (spreadsheet analysis), marketing (content planning), and data analysis (CSV processing). Each plugin connects through the Model Context Protocol (MCP).
Does Claude Cowork on Windows send my files to the cloud?
Cowork runs locally on your machine inside a sandboxed environment. It reads and writes files on your local filesystem. The agent does make API calls to Anthropic’s servers for model inference, but your files stay on your machine. This architecture supports data residency requirements.
When did Claude Cowork launch on Windows?
Anthropic released Claude Cowork for Windows on February 10, 2026, exactly 29 days after the initial macOS launch on January 12, 2026. The Windows version launched with full feature parity including all plugins and MCP support.