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. 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:

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