Skip to content

list.md

Latest commit

 

History

History
43 lines (35 loc) · 2.78 KB

list.md

File metadata and controls

43 lines (35 loc) · 2.78 KB
Raw
summary Enumerate apps, windows, screens, and permissions via peekaboo list
read_when
inspecting what Peekaboo can currently target
scripting toolchains that need structured app/window inventory

peekaboo list

peekaboo list is a container command that fans out into focused inventory subcommands. Each subcommand returns human-readable tables by default and emits the same structure in JSON when --json-output is set, so agents can choose whichever format fits their control loop.

Subcommands

Subcommand What it does Notable options
apps (default) Enumerates every running GUI app with bundle ID, PID, and focus status. None – but it enforces screen-recording permission before scanning.
windows Lists the windows owned by a specific process with optional bounds/ID metadata. `--app <name
menubar Dumps every status-item title/index so you can target them via menubar click. Supports --json-output for scripts piping into jq.
screens Shows connected displays, resolution, scaling, and whether they are main/secondary. None.
permissions Mirrors peekaboo permissions status for quick entitlement checks. None.

Implementation notes

  • The root command does nothing; Commander dispatches straight to the subcommand so peekaboo list defaults to list apps.
  • apps and windows call requireScreenRecordingPermission before crawling AX so macOS doesn’t silently strip metadata.
  • windows accepts either user-friendly names or PID:#### tokens and normalizes --include-details values by lowercasing + replacing - with _, so both --include-details offscreen,bounds and off_screen work.
  • Menu bar listing is powered by the same MenuServiceBridge used by peekaboo menubar, so indices reported here line up with what menubar click --index expects.
  • Screen inventory uses services.screens.listScreens() and returns a UnifiedToolOutput<ScreenListData> payload, which is why JSON mode includes refresh timestamps and display UUIDs.

Examples

# Default invocation: list every app currently visible to AX
polter peekaboo -- list

# Inspect all Chrome windows including their bounds + element IDs
polter peekaboo -- list windows --app "Google Chrome" --include-details bounds,ids

# Pipe the current display layout into jq for scripting
polter peekaboo -- list screens --json-output | jq '.data.screens[] | {name, size: .frame}'

Troubleshooting

  • Verify Screen Recording + Accessibility permissions (peekaboo permissions status).
  • Confirm your target (app/window/selector) with peekaboo list/peekaboo see before rerunning.
  • Re-run with --json-output or --verbose to surface detailed errors.