computer-uselisted
Install: claude install-skill rustcircle/c101
# Computer use
## 1. Is GUI control the right tier?
Use the most precise route that reaches the target; GUI control is the broadest, slowest and riskiest.
| Rank | Route | Examples |
|---|---|---|
| 1 | Dedicated MCP or API | calendar, mail, issue trackers with connectors |
| 2 | CLI via Bash | `open -a`, `osascript` (AppleScript), `shortcuts run`, `xcrun simctl`, `xcodebuild`, `screencapture`, `mdfind` |
| 3 | Browser tools for anything web | Playwright (browser-automation skill) |
| 4a | Sandboxed computer use (desktop-sandbox) | GUI work on files the brief provides, Linux GUI apps, GUI tests of the user's own app, untrusted documents; works under the Agent SDK |
| 4b | Host computer use (this skill) | the user's own macOS apps and data, macOS-only apps, iOS Simulator taps |
CLI equivalents that remove most GUI steps: [macOS CLI alternatives](references/macos-cli.md).
Between 4a and 4b, take 4a whenever no personal state is needed (sandboxed-computer-use section 1).
If the task is achievable at rank 1-2, do it there; rank-3 (web) work goes back as an Open doubt
routed to browser-operator (computer-operator may spawn only file-summarizer). Say which in Evidence.
## 2. Preconditions
- Built-in computer use is interactive-only: it exists only in an interactive Claude Code session on
macOS (Pro or Max plan with claude.ai login, `computer-use` enabled once by the user in `/mcp`,
Accessibility and Screen Recording granted to the terminal app). It does not exist under th