claude-code - 💡(How to fix) Fix [FEATURE] Computer Use support in Claude Code CLI on Windows [1 participants]

Preflight Checklist

• I have searched existing requests and this feature hasn't been requested yet
• This is a single feature request (not multiple features)

Problem Statement

Windows users cannot use Computer Use in the Claude Code CLI/terminal workflow.

I use Claude Code from a native Windows terminal and need it to test GUI apps, interact with windows and dialogs, and verify desktop workflows without switching to the Desktop app. Right now, the CLI flow stops at terminal-only tasks, so I have to leave the shell-based workflow to do screen control and app interaction manually.

This breaks the terminal-first workflow I rely on for development, debugging, WSL/SSH-style work, and automation.

Current workflow:

• Launch claude in terminal (Windows native/PowerShell, no Desktop app).
• Need Claude to test GUI apps, navigate UIs, verify Electron/SwiftUI builds, or interact with non-CLI tools.
• CLI lacks computer-use MCP server, Claude can't control screen/apps.
• Forced to switch to Desktop app (GUI), breaking terminal-only dev flow (tmux, SSH, CI/scripts).

Docs confirm: "Computer use in the CLI is not available on Linux or Windows. On Windows, use Desktop instead."

This impacts terminal-heavy developers, WSL users, and anyone relying on automation or remote workflows.

Proposed Solution

Enable computer-use MCP server in CLI on Windows (matching macOS).

Ideal UX (same as macOS):

• Run /mcp -> See computer-use (disabled).
• Select -> "Enable" -> Persists per-project.
• Grant Windows accessibility/screen permissions on first use.
• Prompt appears: "Claude wants to use your computer..." -> Allow.
• Claude can then perform actions like launching apps, clicking UI, typing, and validating results.

This should use the same underlying engine as the Desktop app, simply exposed in the CLI. It should work alongside PowerShell/Bash tools seamlessly.

Alternative Solutions

I can use the Desktop app, but that breaks my terminal-only workflow. WSL or remote machines add extra friction, and manual screenshot/scripts workarounds are slow and unreliable.

Priority

High - Significant impact on productivity

Feature Category

MCP server integration

Use Case Example

I'm working on a Windows project in Claude Code CLI. Claude writes code and builds the app. I ask it to launch the app, click through the UI, and verify the result. On macOS, this is possible in CLI; on Windows, I have to switch to Desktop or do it manually. Windows CLI support would keep the whole loop inside the terminal.

Additional Context

Related docs currently say computer use in the CLI is macOS-only, while Desktop supports macOS and Windows. The closest existing issue is broader than Windows and is already closed as not planned, so this request is specifically for Windows CLI parity.

https://code.claude.com/docs/en/computer-use > "Let Claude use your computer from the CLI"

(Reopening as a fresh issue per the stale-bot request on #54833.)