Peekaboo 🫣 — Mac automation that sees the screen and does the clicks.

Peekaboo is a macOS CLI and menu-bar app for screen capture, accessibility inspection, and native UI automation. Use it directly, let its agent plan multi-step work, or expose the same toolset to MCP clients.

Install

The released CLI and app require macOS 15 or later.

CLI with Homebrew

brew install openclaw/tap/peekaboo

MCP package with npm

The npm package requires Node.js 22 or later and includes the CLI plus its MCP launcher.

npx -y @steipete/peekaboo --version

See MCP setup to connect it to Codex, Claude Code, Cursor, or another MCP client.

Mac app

Download the signed DMG from the latest GitHub release. The menu-bar app provides permission onboarding, visual feedback, and agent sessions; install the CLI separately when you also need peekaboo on PATH.

For source builds and alternative install details, see the installation guide.

Quick start

Check the permissions available to Peekaboo, then take a screenshot:

peekaboo permissions status
peekaboo see --no-elements --mode screen --path /tmp/peekaboo-screen.png

Screen capture requires Screen Recording permission. Accessibility permission enables UI inspection and control; the permissions guide covers setup and the additional permission used for synthetic input.

Inspect a running app to get a structured UI map with opaque element IDs:

peekaboo see --app Finder --json

That is the core loop: observe the current screen, choose an element from the result, and act on it.

What's new in 4.9.3

Peekaboo 4.9.3 is a fix release. Manual peekaboo daemon start now waits as long as automatic startup and reports the real authentication or probe failure instead of a generic "did not become ready" timeout, agent tool results stay readable when they contain backslashes or newlines, and the peekaboo-mcp wrapper exits with an error after fatal failures instead of looking healthy. 4.9.2 shipped Peekaboo.app as a universal app for Intel Macs; see the changelog for both releases.

Automate an app

List Safari's windows, copy the intended window_id (12345 below), then keep the entire interaction pinned to that exact window:

peekaboo window list --app Safari --json
peekaboo click "Address and search bar" --app Safari --window-id 12345
peekaboo type "github.com/openclaw/Peekaboo" --app Safari --window-id 12345
peekaboo press Return --app Safari --window-id 12345

Targeted semantic and typed CLI input uses background delivery when Peekaboo can resolve the process, so the app does not have to become frontmost. Raw CLI press chords can also stay background with an exact window selector. The CLI also accepts a fresh exact non-dialog snapshot; that snapshot is required by background-only Agent/MCP policy. App/PID-only and targetless chords require explicit foreground consent, as do window-selector-only Agent/MCP chords. Prefer a semantic action such as menu click when one exists. See the automation guide for element IDs, coordinates, snapshots, waits, and input behavior.

Agent and MCP

The agent combines the same observation and action tools into a natural-language run:

peekaboo agent "Open Safari, go to github.com, and search for Peekaboo" --allow-foreground