# Host Computer Use

Beta desktop control through the connected A0 CLI host.

- Repository: https://github.com/agent0ai/agent-zero (19630 stars)
- Category: Design
- 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 -g -a claude-code -y`
Codex: `npx skills add agent0ai/agent-zero --skill host-computer-use -g -a codex -y`
Cursor: `npx skills add agent0ai/agent-zero --skill host-computer-use -g -a cursor -y`
Gemini CLI: `npx skills add agent0ai/agent-zero --skill host-computer-use -g -a gemini-cli -y`

## Description

Beta desktop control through the connected A0 CLI host. Use for the user's host/local computer screenshots, screen inspection, menus, native app UI, OS-level clicking, scrolling, typing, or checking computer_use_remote status. Use instead of linux-desktop for host/local machine control. Do not use for ordinary browser navigation; host browser requests should use the browser tool.

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

# Host Computer Use

This skill unlocks the beta `computer_use_remote` tool for connected local desktop control through A0 CLI or a Launcher host gateway. Prefer native background-safe computer use when the connected backend advertises window and element-index features.

## When to Use

Load this skill before using `computer_use_remote` for local desktop and native UI tasks on the connected machine. Use it for the user's real host screen, not the internal Agent Zero Desktop.

If the task is browser-only and the user is flexible, prefer direct browser tooling because it is usually more reliable and token-efficient than screenshot-driven desktop control.

If the task needs shell execution on the CLI host, load `host-code-execution` separately rather than treating desktop control and shell execution as one affordance.

## Host vs Docker Desktop Boundary

This skill controls the user's connected host/local computer through A0 CLI. It is not the built-in Linux Desktop/Xpra skill.

Never switch to `linux-desktop`, the Agent Zero Desktop/Xpra surface, `desktopctl.sh`, `code_execution_tool`, or Docker/server shell commands as a fallback for host screen actions such as screenshots, clicking, typing, desktop state changes, or checking visible host UI. Those paths only see the internal Agent Zero runtime. If `computer_use_remote` is unavailable, disabled, or needs re-arming, stop and ask the user to run `/computer-use on` in the A0 Launcher chat when using Launcher Host access, or in A0 CLI otherwise, and approve the platform permission prompt.

## Browser Boundary

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