atmos-desktop-uselisted

# Atmos Desktop Use Local desktop capture + control via `atmos desktop-use`. **No MCP.** Brand: **Desktop Use** / **Atmos Desktop Use** only. Not this skill: Device Preview phone → `atmos-device-preview`. Details: [`references/cli.md`](references/cli.md). ## Prerequisites 1. `atmos` on `PATH`. 2. Engine installed + **Accessibility** + **Screen Recording** for **Atmos Desktop Use** (Settings → Desktop Use). Agents cannot complete TCC. ## Decision tree | Intent | Commands | |--------|----------| | Ready? | `status` + `doctor` | | List windows | `drive verify` (**not** `drive windows`) | | Full-display screenshot | `drive screenshot --out …` (preferred for click loops) | | Frontmost window only | `capture --out …` | | Click / type / full desktop shell | `drive click|type|double-click|scroll|hotkey|…` (Phase 1–2; see cli.md) | | **Page / Chrome DOM** | **`atmos browser-use`** (separate product — not Desktop Use) | | Install engine | `driver ensure` | ## Critical click rules (read this — most failures are here) ### 1) Coordinate space (Retina trap) `drive screenshot` returns a **native PNG** that is often **2×** logical screen size (e.g. screen 1512×982, PNG 3024×1964). | Source of (x, y) | Flag | Example | |------------------|------|---------| | Pixel you read on the **drive screenshot PNG** | default `--coord-space png` | button at image (200, 322) → `--x 200 --y 322` | | `drive verify` bounds / AX `position` / System Events | `--coord-space points` | AX says (100, 16