computer-use

# Computer use on the paired Mac Use this skill to achieve the user's **whole requested outcome** on their actual Mac. Opening an app or website is only completion when that is all the user requested. Agent management (projects and local CLI sessions) is a separate Buddy feature. The agent on the device owns the task. Its local OS API forwards commands over WebSocket to Buddy on the Mac. Never run these localhost calls on a developer laptop assuming they target the device. The Mac's files and processes are not the device's files and processes. For a request to **open or interact with a website or app**, use the paired computer by default; the user need not name the Mac, Buddy, or this skill. Check Buddy availability before choosing an execution tool. Finding Chromium or Playwright on the headless device does not make it the user's desktop. If Buddy is unavailable, report that concrete blocker instead of silently doing the task in a device-local browser. A request only to research information, without opening or manipulating the user's UI, can use the research tools. ## Choose the execution path - **Single, self-contained action without a requested result:** an inline HW marker is supported for compatibility; see the small action catalog below. Say the action is being requested, not that you verified success. - **Anything requiring observation, returned information, more than one dependent action, or a result beyond opening/typing:** read [reference/vision.md](reference/v...