computer-uselisted

# Computer Use Reads and drives applications through the OS accessibility tree - UI Automation on Windows, AXUIElement on macOS. Separate from Claude Code's built-in `computer-use` server; on Windows it is the only screen-control path. ## Load the tools One search loads the loop, and run it again after a compaction (the schemas drop, this skill stays): ``` ToolSearch select:computer_apps,computer_snapshot,computer_grant,computer_run,computer_click ``` A second search when a task needs them: `computer_type`, `computer_key`, `computer_scroll`, `computer_wait_for`, `computer_launch`. A third for `computer_task`, `computer_focus`, `computer_close_window`, `computer_clipboard`, `computer_screenshot`. ## The loop 1. `computer_apps` - find the window. Note its `hwnd` and tier. If the app is not running, `computer_launch { app: "notepad" }` starts it and returns the new window's handle. 2. `computer_snapshot { hwnd }` - read it once. Every element gets an index that stays valid for as long as that control exists. Reading never needs a grant and never disturbs anyone. 3. `computer_grant { hwnd }` - once per app per session, only to act. 4. `computer_run { hwnd, steps: [...] }` - do the whole next stretch in one call: every click, type, key, scroll and wait you can already name from what you just read. It runs them in order, stops at the first failure, and ends with what changed. 5. Read that closing delta. Only if the run stopped, or the delta is not what