Claude Code's /mcp Computer Use: Test Your Local Apps Directly from the CLI

What Changed — The /mcp Command for macOS

Anthropic has released a "Computer Use" feature in Claude Code, now available in research preview for Pro and Max users on macOS. This isn't just a general AI feature—it's specifically integrated into the Claude Code CLI via the /mcp command.

Unlike traditional AI that only generates code, Claude can now open your compiled applications, interact with their graphical interfaces, and test what it built. It works on anything you can open on your Mac: a compiled SwiftUI app, a local Electron build, or any GUI tool that doesn't have a CLI interface.

What It Means For Claude Code Users

This transforms Claude Code from a coding assistant into a testing and automation agent. Previously, you'd ask Claude to write code, then manually test it. Now, you can tell Claude to "build and test the SwiftUI app" and it can:

1. Compile your code
2. Launch the application
3. Click through the UI to verify functionality
4. Report back with screenshots or logs

This is particularly valuable for:

• Local GUI Testing: Test Electron apps, native macOS apps, or any local build without writing automated UI tests
• Workflow Automation: Automate repetitive GUI tasks during development (filling forms in local admin panels, etc.)
• Rapid Prototyping: Build and immediately test UI changes without leaving the terminal

How To Enable and Use It Right Now

Enable computer use by running:

claude code /mcp

Once enabled, you can give Claude instructions like:

"Build the Electron app in the current directory, open it, and test that the login button works."

Or be more specific:

"Open the compiled SwiftUI app at ./build/MyApp.app, click the 'Settings' tab, change the theme to dark mode, and take a screenshot of the result."

Safety and Limitations

The feature includes safeguards: Claude will ask for approval before performing sensitive actions. It's currently macOS-only and requires Pro or Max plans. This follows Anthropic's pattern of releasing powerful features first to Claude Code users before broader availability—similar to how code execution capabilities debuted in Claude Code before reaching the web interface.

The Bigger Picture: Claude Code as an Agent Platform

This isn't just about clicking buttons. It's about Claude Code evolving into a full-stack development agent. With file system access, terminal control, and now GUI interaction, Claude Code can handle complete development workflows:

1. Write code
2. Build/compile
3. Launch application
4. Test functionality
5. Debug based on results

All from a single conversation in your terminal.