# Claude computer use on Windows: Desktop, Claude Code, Codex and MCP > Where Claude computer use works on Windows (Claude Desktop, not the Claude Code CLI), how Codex handles Windows, and how an MCP server gives any agent its own cursor on a Windows PC. Updated 2026-10-23 ยท https://shadowcursor.com/guides/claude-computer-use-windows/ > **Short answer:** On Windows, Claude computer use works in the Claude Desktop app (Cowork and Claude Code inside the app) as a research preview for Pro and Max plans; you turn on **Enable computer use** in Settings and it takes effect immediately. The Claude Code CLI has no computer use on Windows, and Anthropic documents the background mode for macOS only. Codex computer use also runs on Windows, but on the active desktop, where it takes over the pointer and keyboard. For other clients, other plans or several agents at once, connect a computer use MCP server such as the ShadowCursor beta for Windows. ## What runs on Windows today Computer use on Windows depends on which app you use, more than on the model. As documented by Anthropic and OpenAI in October 2026: | Tool | On Windows | While it works | Plans and clients | | --- | --- | --- | --- | | Claude Desktop (Cowork, Code tab) | Yes, research preview | Background mode is documented for macOS only; outside it, Claude hides your other windows | Pro or Max, not Team or Enterprise | | Claude Code CLI | No, macOS only | No built-in computer use | Anthropic points Windows users to the Desktop app | | Codex in the ChatGPT desktop app | Yes | Runs on the active desktop and takes over foreground input | ChatGPT Work and Codex, in supported regions | | ShadowCursor for Windows (beta) | Yes, Windows 10 and 11 | Each agent works in its own windows, also covered ones, with its own cursor | Any MCP client, any Claude plan | Sources: [Claude Desktop docs](https://code.claude.com/docs/en/desktop), [Claude Code computer use docs](https://code.claude.com/docs/en/computer-use), [ChatGPT computer use docs](https://learn.chatgpt.com/docs/computer-use). ## Claude Desktop on Windows This is Anthropic's supported path on Windows. To turn it on: 1. Update Claude Desktop to the latest version from claude.com/download and restart it. 2. Open Settings and turn on **Enable computer use**. The Desktop docs place the switch under **This computer > System**, the Help Center under **General**. On Windows it takes effect immediately; the Accessibility and Screen Recording step only exists on macOS. 3. Start a Cowork or Code session and ask for a task in an app. Claude asks for permission the first time it needs each app in a session. Claude tries connectors, the shell and Claude in Chrome first and uses the screen only when nothing else reaches the app. Browsers and trading platforms are view only, terminals and IDEs are click only, and everything else gets full control; these tiers cannot be changed. Apps with broad reach, such as File Explorer and Settings, show an extra warning before you approve them. The PC has to stay awake with Claude Desktop open. What Anthropic does not document for Windows is the background mode. On macOS, Claude works in approved apps while you keep working. Outside that mode, Claude hides your other windows while it works and restores them when it finishes. If your Claude Desktop on Windows offers no background mode, expect Claude to need the screen while it works. The [guide to Claude computer use on the Mac](https://shadowcursor.com/guides/claude-computer-use-mac/) covers the macOS side in detail. ## Claude Code on Windows The built-in `computer-use` server of the Claude Code CLI is macOS only. Anthropic's troubleshooting page says it is not available on Linux or Windows and points to the Desktop app instead. That leaves two options if you work in Claude Code on Windows: - Use the **Code tab of Claude Desktop**, which has computer use on Windows with a Pro or Max plan. - Add a **computer use MCP server** to the CLI. Claude Code calls it like any other tool, on any plan and also with an API key, which matters because Anthropic's built-in computer use excludes Team, Enterprise and third-party providers ([details for Team and Enterprise](https://shadowcursor.com/guides/claude-computer-use-team-enterprise-api/)). ## Codex on Windows OpenAI's computer use lives in the ChatGPT desktop app (Codex, or ChatGPT in Work mode) with the Computer Use plugin. On Windows it runs on the active desktop and cannot work in the background while you use the same session: it takes over foreground input, and the target app has to stay visible. OpenAI suggests a second device or a Windows virtual machine if you want to keep using the PC. Missing plugin, region rollout and other causes are covered in [Codex computer use not working](https://shadowcursor.com/guides/codex-computer-use-not-working/). ## Why background computer use is harder on Windows Windows has one foreground window and one keyboard focus. A tool that uses the real mouse and keyboard can only reach the window in front. Working in the background means sending input to one specific window while others cover it, and capturing that window instead of the screen. The [guide to background computer use](https://shadowcursor.com/guides/background-computer-use-mac/) explains the idea. ## ShadowCursor for Windows (beta) ShadowCursor is a computer use MCP server that gives every connected agent its own cursor, drawn on screen with a name tag, its own keyboard input that only reaches its window, its own clipboard, and its own windows. The Windows version is in beta for Windows 10 and 11, on x64 and ARM PCs, with the same tools as the Mac app: - **Reading windows:** the agent gets a screenshot of the window it works in, also when it is covered, plus the window's controls through UI Automation (Java apps through the Java Access Bridge). - **Input:** clicks, typing and controls go to the target app's window, with human timing for pointer movement and typing. Input to the window you are working in is refused; an agent can use another window of the same app. - **Hidden windows:** a hidden app window is used in place and stays invisible to you, without a virtual machine, driver or extra monitor. - **Opening apps:** apps, files and URLs open behind your windows, and browsers open a new window instead of a tab in yours. - **Several agents:** each connection has its own cursor and state, so Claude Code and Codex can work side by side. Setup needs no administrator rights: 1. Download the ZIP for your PC (x64 or ARM) and extract all files into one folder. 2. Open shadowcursorw.exe. The beta is not code-signed yet, so Windows SmartScreen asks once; choose "More info" and "Run anyway". The download page lists SHA-256 checksums. 3. Choose "Install for me", then "Connect automatically". ShadowCursor adds itself to Claude Code, Claude Desktop, Codex, Cursor and VS Code where they are installed. Setup reopens from the Start menu. Claude and ChatGPT in the browser can connect too, through the "Claude or ChatGPT online" option in setup; [this guide](https://shadowcursor.com/guides/chatgpt-claude-control-your-mac/) explains how custom connectors work. The price is the same as on the Mac: a 7-day free trial without a card, then $12.99 per month or $69.99 per year, on up to three devices. ## Limits of the Windows beta The Windows version is younger than the Mac app, and its own documentation says that full background isolation and parity with the Mac are not achieved. Isolation was measured with tested app types (Notepad, WinForms, WPF, Edge and Explorer), not with every app. Known limits: - Minimized windows are not restored in the background. - Chrome and Edge can stop drawing pages in hidden or fully covered windows, so the agent's screenshot can be stale or blank. - Typing into Edge's address bar does not land; agents open URLs with the launch tool instead. - In WPF apps, drags and other pointer gestures fail with an explanation, and setting text works only in standard text boxes. - System drag and drop is not supported (file copy and move in Explorer have their own path). - The agent clipboard holds text, with formatting only between rich text controls; app-specific copy buttons still write to the Windows clipboard. - Apps that need administrator rights and some sandboxed apps cannot be operated. - The PC must be signed in with the desktop available. ShadowCursor does not bypass the Windows sign-in. ## Open-source option: Windows-MCP [Windows-MCP](https://github.com/CursorTouch/Windows-MCP) is an MIT-licensed MCP server for Windows 10 and 11 built on UI Automation. Its README describes desktop actions as taking ownership of the desktop, calls user takeover "best-effort", and says it uses the real Windows clipboard. It collects anonymized usage data unless you set `ANONYMIZED_TELEMETRY` to false. Its README describes no support for several agents with separate cursors. ## FAQ ### Does Claude computer use work on Windows 11? Yes, in the Claude Desktop app with a Pro or Max plan. Anthropic lists computer use as a research preview on macOS and Windows and names no minimum Windows version. It is not in the Claude Code CLI on Windows. ### Can Claude work in the background on Windows? Anthropic documents the background mode only for macOS. Outside that mode, Claude hides your other windows while it works and restores them afterwards. A computer use MCP server that works in background windows, such as ShadowCursor, lets the agent work in its own windows instead. ### Why does Codex take over my mouse on Windows? On Windows, OpenAI's computer use runs on the active desktop and works in the foreground. OpenAI recommends a second device or a Windows virtual machine if you want to keep using your PC during a task. ### Can I use computer use on Windows with Claude Team or Enterprise? Not with Anthropic's built-in computer use, which needs Pro or Max. Claude Code on a Team or Enterprise plan, or with an API key, can use a computer use MCP server instead. ### Do I need administrator rights for ShadowCursor on Windows? No. "Install for me" installs it for your Windows user only. Apps that themselves run with administrator rights cannot be operated by an agent.