cua-driver

Operate one exact target, observe its state, act once, and verify the user's postcondition.

Act

Goal	Tool or command	Read when needed
Check installation and capabilities	`cua-driver --version`, `status`, `doctor`, `describe <tool>`; MCP `tools/list`	Runtime
Find or open the requested app	`list_apps`, `list_windows`, `launch_app`	Current platform guide below
Observe one window	`get_window_state({pid, window_id})`	Workflow
Act on a control	`click` / `type_text` with a fresh `element_token` and exact window target	Workflow
Use pixels when semantics cannot reach it	Fresh target screenshot, then `x,y` on the same target	Workflow
Verify the outcome	`verify_state({pid, window_id, expect})` or a fresh snapshot read by the agent	Workflow
Operate the authorized desktop	`get_desktop_state` → input with `target:{kind:"desktop",display_id:"primary"}` → `get_desktop_state`	Workflow, Linux on Wayland
Drive supported browser page content	`get_browser_state` → typed browser action → fresh state	Browser
Record an explicitly requested run	`start_recording` → actions → `stop_recording`; verify artifacts	Recording
Finish	Stop after proof; `end_session` for this run, not `cua-driver stop` on a shared service	Runtime