host-computer-use-macos

Guides macOS GUI automation via Accessibility-tree targeting and screenshot verification.

19.1k|3.8k|Updated Jun 10, 2024
One-click install
npx skills add https://github.com/agent0ai/agent-zero --skill host-computer-use-macos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: host-computer-use-macos
Source: https://github.com/agent0ai/agent-zero/tree/main/plugins/_a0_connector/skills/host-computer-use-macos
Command: npx skills add https://github.com/agent0ai/agent-zero --skill host-computer-use-macos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Controlling a macOS desktop remotely is error-prone when relying on blind pixel clicks. This Skill provides backend-specific guidance for driving macOS through the computer_use_remote tool using structural Accessibility-tree targeting, window actions, and screenshot verification.

Core Features & Use Cases

  • AX Structural Targeting: Inspect the frontmost app's Accessibility tree with ax_snapshot and act on named controls with ax_action (press, focus, set_value) instead of fragile coordinate clicks.
  • Window Management: Handle macOS window actions such as hide (Command+H) and minimize (Command+M), with mandatory screenshot verification after each attempt.
  • Permission Handling: Detect and correctly respond to macOS Screen Recording, Accessibility, and Input Monitoring permission failures, including COMPUTER_USE_REARM_REQUIRED states.
  • Use Case: After connecting to a macOS host via the A0 CLI, use this Skill to click a dialog's OK button by role and title, verify the result from the attached screenshot, and recover gracefully if the target is ambiguous or missing.

Quick Start

Load this skill after the host computer-use status reports a macOS backend, then take an AX snapshot of the frontmost app and press the target button by role and title.

Frequently Asked Questions about host-computer-use-macos

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I click a button on macOS using the Accessibility tree?

Take an ax_snapshot of the frontmost app to inspect element roles, titles, and paths, then call ax_action with a semantic target such as role AXButton and title OK using the press operation. Verify the result from the screenshot attached to the tool response.

When should I use AX targeting instead of coordinate clicks on macOS?

Prefer AX structural targeting whenever the backend advertises accessibility-tree-snapshot or accessibility-element-click features and the control has a stable title, role, or identifier. Fall back to coordinates only when the element is missing from the AX tree.

Does this skill work for Linux, Windows, or browser automation?

No. It applies only when the connected backend reports macOS with Accessibility-tree support. For Linux, Windows, Xpra, Docker, or browser-only tasks, follow the generic host computer-use rules instead.

Why does computer_use_remote return COMPUTER_USE_REARM_REQUIRED on macOS?

macOS Screen Recording, Accessibility, or Input Monitoring permissions have lapsed or been revoked. Stop immediately and ask the user to run /computer-use on in the A0 Launcher chat or A0 CLI and approve the macOS prompt; do not bypass with screenshots or Docker fallbacks.

How do I verify a macOS window action actually succeeded?

Treat shortcuts like Command+H and Command+M as attempts, not proof. Inspect the fresh screenshot attached after the action; if the target window is still visible, report the attempt failed or switch strategy.