host-computer-use-linux

Guides structural AT-SPI targeting and Wayland input handling for Linux remote computer use.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Controlling a remote Linux desktop through computer_use_remote is unreliable when relying on pixel clicks alone, especially under Wayland where focus and input routing behave differently. This Skill provides backend-specific guidance for using AT-SPI structural targeting, verifying actions with screenshots, and handling Linux-specific permission and focus failures.

Core Features & Use Cases

  • AT-SPI Structural Targeting: Use ax_snapshot to inspect the accessibility tree and ax_action to press, focus, or set values on named buttons, menus, and text fields instead of guessing coordinates.
  • Wayland Input Handling: Apply target-guarded text injection, verified window focus via element_action, and screenshot proof after every state-changing action.
  • Permission and Fallback Rules: Detect errors like COMPUTER_USE_AX_UNAVAILABLE or COMPUTER_USE_REARM_REQUIRED and stop for user re-arming, with a defined fallback order from app-native tooling to keyboard paths to coordinate clicks.
  • Use Case: After host-computer-use reports a Linux/Wayland backend with AT-SPI features, use this Skill to click a dialog's OK button by role and title, then confirm the result with a fresh screenshot before typing into the focused window.

Quick Start

After the connected A0 CLI reports a Linux Wayland backend with AT-SPI features, load this skill and use ax_snapshot followed by ax_action to operate the target window, verifying each step with a screenshot.

Frequently Asked Questions about host-computer-use-linux

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

FAQPage Schema
How do I click buttons on a remote Linux desktop without coordinates?

Use AT-SPI structural targeting: call ax_snapshot to inspect the accessibility tree, then ax_action with a semantic target like role plus title to press the button. This is preferred over pixel clicks whenever the backend advertises atspi-structural-targeting.

How do I type text into a Linux window over Wayland remotely?

Pass the verified active window_id to the type action, since Linux text injection is target-guarded. If the tool returns COMPUTER_USE_WINDOW_REQUIRED or COMPUTER_USE_TARGET_NOT_FOCUSED, do not type globally; re-verify focus first.

When should I use this Linux skill instead of generic host computer use?

Load it only after status or start_session reports backend_family linux, backend_id wayland, or AT-SPI features. Do not use it for macOS, Windows, Xpra, Docker, browser-only tasks, or the internal Agent Zero Desktop.

Why does my Linux remote action fail with COMPUTER_USE_REARM_REQUIRED?

This error means the desktop accessibility or session state needs user intervention. Stop immediately and ask the user to re-arm or fix the Linux session; do not bypass it with server screenshots, Docker commands, or code execution.

What if the AT-SPI tree is too shallow to find my target element?

Some apps expose shallow trees until their own accessibility support is enabled. Fall back in this order: app-native or browser tooling, reliable keyboard paths, then normalized coordinate clicks from a fresh screenshot.