Yes, Claude Cowork runs on Windows. It went generally available on both macOS and Windows on April 9, 2026, after a research preview that started macOS-only back in January. If you sat out the first wave of Cowork coverage because it was all about Macs, you can stop waiting. Claude Cowork on Windows ships today. It is a real product you can install, not a line on a roadmap.
I will keep this practical: how to get it, what you need, and the one behavior that trips up almost everyone on day one.
Is Claude Cowork available for Windows
It is, and the date matters here. The Claude release notes log the milestone plainly: "Claude Cowork generally available on macOS and Windows through the Claude Desktop app" on April 9, 2026. (release notes)
Before that, the story was Mac-first. The research preview launched January 12, 2026 on Claude Desktop for macOS only, on Max plans, then opened to Pro plans on January 16. Through that whole stretch, Windows users had nothing official to install. April 9 closed the gap and put both platforms on equal footing.
Set your expectations on one point. Cowork lives inside the Claude desktop app, next to Chat and Code. It does not have its own icon or its own installer. You install Claude for Windows, and Cowork is a mode you switch into once you are in.
Claude Cowork Windows download
There is exactly one place to download it: claude.com/download. Cowork needs the latest version of Claude for Windows, so even if the app is already on your machine, update it before you go hunting for the Cowork panel. An old build simply will not show it.
Anthropic also publishes a readiness check, which I think is a nice touch, because you can confirm your machine before you commit. The support docs list separate checks for macOS, Windows arm64, and Windows x64. (get started with Cowork) That arm64/x64 split is worth a second look if you are on a Snapdragon or another ARM-based Windows laptop. It tells you Anthropic shipped a native ARM path instead of leaving those machines to emulation, and that usually means a smoother experience. Run the check. A ready machine returns "This computer is ready for Cowork."
How to install Claude Cowork on Windows
The flow is short. Go to claude.com/download, grab the Windows installer, and run it the way you run any Windows app. If Claude for Windows is already installed, let it update to the latest version rather than reinstalling from scratch. Sign in to your account. Open the app and look for Cowork next to Chat and Code.
That is the entire install. No command line, no PATH to edit, no separate Cowork binary to babysit. If you came over from Claude Code expecting a terminal and config files, this is the other door into the same agent engine, and it is deliberately the quieter one.
What if Cowork does not appear after install? Two checks cover most cases. First, confirm you are on the latest app version. Second, confirm your plan includes it, which brings us to the next section.
Which plan you need
Cowork is paid-only. The get-started docs state it is "available for paid plans (Pro, Max, Team, Enterprise) only," and the product page says the same. The free tier does not include it, full stop.
I would not over-think the tier past that. Pro is the entry point for an individual. Team and Enterprise add admin controls and usage analytics that landed alongside the April GA. If you are on a free account today, the upgrade is your gate, not your hardware. So before you assume a missing Cowork panel is some Windows bug, check your current plan in account settings.
The behavior nobody warns you about
The desktop app must stay open while Claude works. Close it and the session ends. The support docs are blunt about it: "The Claude Desktop app must remain open while Claude is working. If you close the app, your session will end."
Scheduled tasks carry the same rule, plus one more. They "only run while your computer is awake and the Claude Desktop app is open." So a Cowork job you set for every Monday morning will quietly skip if your Windows laptop is asleep in a bag, or if the app got closed sometime over the weekend. You have to plan around it. For a recurring task to actually fire, the machine has to be on and the app has to be running at that exact moment.
There is a release valve for the always-open constraint, though it comes with conditions. Dispatch, currently in beta, lets you message Claude from your phone and have it finish work on your desktop. The desktop still does the actual job, and it still has to be open and awake. Think of Dispatch as a trigger and a results channel rather than a way to run Cowork with no live desktop behind it. Handy when you are away from the keyboard, but it does not stand in for the keyboard.
Where to go next
Two articles pick up from here. What is Claude Cowork covers what the agent actually does with your files, in plain terms. How to use Claude Cowork walks through running a real task end to end. Read either one after you have the app installed, because both assume you can open the Cowork panel and follow along.
Here is one thing worth building before you pile up a stack of repeat tasks: a skill. Cowork runs on Anthropic-format Agent Skills, the same SKILL.md folders that work in Claude Code, the Claude apps, Codex, Cursor, and Gemini CLI. Write one, and it runs everywhere those tools do, Cowork included. If you would rather answer a short interview than hand-author the folder yourself, Knack turns that interview into a shippable skill you can drop straight into Cowork. Same standard, no YAML by hand.
Install the app, confirm your plan, keep the window open. That is the whole bar for getting real work out of Claude Cowork on Windows today.