peekaboo

# Peekaboo - drive, observe, and critique macOS apps The job is not just "is this clickable?" Verify that the workflow works and that every meaningful state looks intentional. Invoke `peekaboo` directly. Build orchestration belongs to the project's task runner; UI observation and driving belong here. **No external AI keys, and never pixels in your own context.** You are the LLM, but do not `view` screenshots yourself: every image you load is re-sent on every later turn and blows up the context window. Save each screenshot with `--path`, then hand its path to a **separate sub-agent running your same model** — one sub-agent per image — which opens it and returns a short text report. Do not call `peekaboo agent`, `peekaboo analyze`, or any `--analyze` mode. Deterministic CLI commands, parsed JSON, visible postconditions, retained artifacts, and delegated visual reads are the verification contract. ## When to invoke - After modifying a SwiftUI/AppKit view or interaction. - When asked to show, inspect, click through, screenshot, or critique a native Mac app. - When debugging a native UI failure or validating a user journey. - Before claiming a native macOS UI feature complete. - Skip purely backend work, Electron/web apps, and iOS simulator flows. ## Prerequisites ```bash peekaboo --version # require >= 3.4 peekaboo permissions status --all-sources --json ``` Use the latest stable Peekaboo on macOS 15.0+. Install it when missing: ```bash br...