peekaboo screen

screen list reports every connected display with its stable display ID, global logical bounds, visible work-area bounds, scale factor, and primary state. Bare peekaboo screen defaults to screen list.

#Examples

# Human-readable display inventory
peekaboo screen list

# Coordinate-mapping fields for automation
peekaboo screen list --json \
  | jq '.data.screens[] | {id: .displayID, bounds, visibleBounds, scale: .scaleFactor, main: .isPrimary}'

bounds and position use the same upper-left-origin global logical coordinate space as click --global. Multiply dimensions by scaleFactor when comparing them with physical-pixel captures. A Retina display can therefore report logical bounds of 1944×1274, scale 2, and a 3888×2548 pixel capture.

visibleBounds uses that same logical coordinate space and includes x, y, width, and height, excluding space reserved by the menu bar and Dock. Its origin can differ from bounds, including when the Dock is on the left. The existing visibleArea width/height fields remain unchanged. Human output adds Visible Position when the work area differs from the full display. window maximize targets the greatest-overlap display's visible bounds; an app can constrain its window, so still verify the actual result rather than treating this inventory as proof of a resize.

For browser pages whose accessibility tree contains no actionable web descendants, pair this inventory with peekaboo window list --app <browser> --json, capture the selected exact window with peekaboo see --window-id <id> --no-elements --json, then use the fresh receipt:

peekaboo click --window-id "$WINDOW_ID" --snapshot "$SNAPSHOT_ID" --at x,y \
  --foreground --input-strategy synthOnly