Overview of Computer Use
Claude’s “Computer Use” feature allows users to execute tasks requiring graphical user interface (GUI) interaction through the command line. This functionality is available as a research preview on macOS, requiring a Pro or Max plan and Claude Code v2.1.85 or later. It is not accessible via Team or Enterprise plans and necessitates an interactive session rather than non-interactive mode with the -p flag.
What Computer Use Can Do
Computer Use automates tasks that typically require manual interaction with a GUI. This includes building native applications, validating software builds, conducting end-to-end UI testing, debugging visual or layout issues, and interacting with tools without CLI access. For example, Claude can compile a Swift app, launch it, and verify its functionality by clicking through controls, all within the same conversation thread.
When Computer Use Applies
Claude prioritizes precise tools before resorting to Computer Use. If an application has an MCP server, that is used first. For shell commands, Bash is employed. Browser-based tasks leverage a Chrome extension if configured. Computer Use is reserved for scenarios where no other method applies, such as native apps, simulators, or proprietary software without APIs.
Enabling Computer Use
To activate the feature, users must enable the “computer-use” MCP server within an interactive Claude Code session. This involves granting macOS permissions for Accessibility and Screen Recording. A prompt appears during the first use to approve these settings, with links to adjust them in System Settings. Restarting Claude Code may be required after granting Screen Recording access.
Approving Apps Per Session
Computer Use does not grant full access to all apps on a machine. When Claude needs control of a specific application, a prompt appears in the terminal asking for approval. Users can allow or deny access per session, with warnings for apps that would provide broad permissions like shell access or system settings changes. The level of control varies by app category: browsers are view-only, terminals and IDEs are click-only, while others receive full access.
How Claude Works on Your Screen
During a session, Computer Use locks the machine, hiding other apps to focus on approved ones. A macOS notification alerts users that Claude is in use, with an option to stop the process via Esc or Ctrl+C. After completion, hidden apps are restored automatically. The terminal remains visible and excluded from screenshots, ensuring Claude cannot access its output.
Safety and Trust Boundary
Unlike sandboxed tools like Bash, Computer Use operates on the user’s actual desktop with approved app access. While Claude monitors actions for potential prompt injection, it does not enforce strict configurations. Built-in safeguards include per-app approval, warnings for high-risk apps, terminal exclusion from screenshots, and a global escape key to terminate sessions immediately.
Example Workflows
Common use cases include validating native builds by compiling and testing an app, reproducing layout bugs by resizing windows and taking screenshots, or testing simulator flows without external tools. These workflows demonstrate how Computer Use integrates with coding tasks to streamline development processes.
