cua-driver

name	cua-driver
description	Use when a task needs to control a native macOS desktop app that has no dedicated MCP or web UI — DaVinci Resolve, Pro Tools/Logic, Finder, Maps, System Settings, or any other native app — via screenshot-and-click automation, or when the user asks to see or operate their actual desktop.

cua-driver — native macOS GUI automation

Backs the mcp__computer-use__* tools. "Cua Driver" (com.trycua.driver) is the background service (LSUIElement, no dock icon) that lets Claude take screenshots of the user's desktop and drive it with mouse/keyboard, the same way a person would.

When to use this vs. the other browser/automation skills

Route by app type, not by habit — see browser-routing for the web-surface decision tree. This skill only owns the native desktop lane:

Target	Tool
Dedicated MCP exists for the app (Slack, Gmail, Linear, Calendar, etc.)	Use that MCP — faster, precise, API-backed
Web app, no dedicated MCP	claude-in-chrome (DOM-aware, faster than pixel clicking)
Native desktop app (DaVinci Resolve, Pro Tools, Logic, Finder, Maps, Notes, Photos, System Settings, any third-party native app)	cua-driver — this is the right tool, don't decline just because there's no app-specific MCP
Cross-app workflow spanning several native apps	cua-driver

Referenced by video-colorist (DaVinci Resolve LUT generation, calibrated-monitor spot checks) and video-sound-designer (Pro Tools/Logic mixes) for exactly this reason.

Access flow