computer-use

# Computer Use Use this skill when the task should operate through Orca's desktop computer-use surface rather than native Codex computer tools, raw AppleScript, ad hoc screenshots, or direct app internals. ## Preconditions - Prefer the public `orca computer ...` command. - In this Orca worktree, use `./config/scripts/orca-dev computer ...` when testing the local dev runtime. - Prefer `--json` for agent-driven calls. Screenshot image bytes are omitted from JSON and written to `screenshot.path` when present. - Do not push, submit forms, send messages, buy items, delete data, or change account settings unless the user explicitly asked for that specific action. - If an app contains sensitive content, read only what the user requested and avoid unnecessary screenshots or logs. Check runtime availability first: ```bash orca status --json orca computer capabilities --json ``` For local development against this worktree: ```bash ./config/scripts/orca-dev status --json ``` ## Core Workflow Use a snapshot-act-snapshot loop: 1. Discover apps: ```bash orca computer list-apps --json ``` 2. Get a fresh state for the target app: ```bash orca computer get-app-state --app com.spotify.client --json ``` 3. Choose an element from that state. 4. Perform one action: ```bash orca computer click --app com.spotify.client --element-index 42 --json ``` 5. Inspect the action result before deciding whether to act again. Actions return a fresh state: ```bash orca computer click --app com...