Host Computer Use - Windows

Use this after host-computer-use when the connected A0 CLI reports the Windows computer-use backend.

Do not use this skill for Linux, macOS, Xpra, Docker, or browser-only tasks. If the backend is not Windows or does not advertise UI Automation support, skip UIA actions and follow the generic host computer-use rules.

Windows UIA Targeting

Windows backends can advertise structural UI Automation features:

• uia-tree-snapshot
• uia-structural-targeting
• uia-element-action
• uia-window-management
• native-window-list
• window-state
• element-index-targeting
• background-dispatch
• foreground-dispatch-fallback

When these features are present, prefer background structural targeting over pixel clicks for named controls such as buttons, menu items, text fields, dialogs, toolbar items, browser address bars, composer fields, and list rows.

Preferred loop:

1. Use list_windows to find the target native window.
2. Use get_window_state with the target pid and/or window_id.
3. Use element_action with the returned element_index and dispatch: "background".
4. If the backend reports background_unavailable, switch to dispatch: "auto" or dispatch: "foreground" only when foreground control is acceptable.

Example:

{
  "tool_name": "computer_use_remote",
  "tool_args": {
    "action": "element_action",
    "window_id": "uia-hwnd:123456",
    "element_index": 7,
    "operation": "invoke",
    "dispatch": "background"
  }
}

Use uia_snapshot to inspect the bounded Windows UI Automation tree when the newer window-state loop is not available:

{
  "tool_name": "computer_use_remote",
  "tool_args": {
    "action": "uia_snapshot",
    "max_depth": 4,
    "max_nodes": 200
  }
}