# Host Computer Use Linux

Host Linux guidance for `computer_use_remote` when results report Linux, Wayland, X11...

- Repository: https://github.com/agent0ai/agent-zero (19630 stars)
- Category: DevOps
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add agent0ai/agent-zero --skill host-computer-use-linux -g -a claude-code -y`
Codex: `npx skills add agent0ai/agent-zero --skill host-computer-use-linux -g -a codex -y`
Cursor: `npx skills add agent0ai/agent-zero --skill host-computer-use-linux -g -a cursor -y`
Gemini CLI: `npx skills add agent0ai/agent-zero --skill host-computer-use-linux -g -a gemini-cli -y`

## Description

Host Linux guidance for `computer_use_remote` when results report Linux, Wayland, X11, or AT-SPI features. Covers verified focus, AT-SPI targeting, XWayland app limitations, remote desktop viewers, and screenshot verification; excludes the internal Docker/Xpra desktop.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Host Computer Use - Linux

Use this after `host-computer-use` when the connected A0 CLI or Launcher gateway reports a Linux computer-use backend. Start with the needed `list_windows` or `capture` observation; the shared tool starts a missing chat session automatically. Use `status` only when you need to inspect authorization or capabilities.

Do not use this skill for macOS, Windows, Xpra, Docker, browser-only tasks, or the internal Agent Zero Desktop. If the backend is not Linux or does not advertise AT-SPI support, skip Linux structural actions and follow the generic host computer-use rules.

For an X11/XWayland app or remote desktop viewer with an incomplete accessibility tree, read [X11 and viewer workflows](references/x11-viewers.md). Use its host-shell techniques only while Computer Use is enabled and authorized and host code execution is independently enabled. A backend limitation is not a permission denial.

## Linux AT-SPI Targeting

Linux backends can advertise structural AT-SPI features:

- `atspi-tree-snapshot`
- `atspi-structural-targeting`
- `atspi-element-action`
- `atspi-set-value`

When these features are present, prefer structural targeting over pixel clicks for named buttons, menu items, text fields, dialogs, toolbar items, tab strips, and application windows.

If the backend also advertises `native-window-list`, `window-state`, `element-index-targeting`, or `background-dispatch`, prefer the generic background loop from `host-computer-use`: `list_windows` -> `get_window_state` -> `element_action`. If those features are absent, use the AT-SPI snapshot/action flow below.

Use `ax_snapshot` to inspect the Linux AT-SPI tree:

```json
{
  "tool_name": "computer_use_remote",
  "tool_args": {
    "action": "ax_snapshot",
    "window_id": "<window_id from list_windows>",
    "max_depth": 4,
    "max_nodes": 200
  }
}
```

The rest: https://github.com/agent0ai/agent-zero/blob/HEAD/plugins/_a0_connector/skills/host-computer-use-linux/SKILL.md