Files
openclaw/docs/platforms/mac/peekaboo.md

66 lines
2.1 KiB
Markdown
Raw Normal View History

---
2026-01-08 23:06:56 +01:00
summary: "PeekabooBridge integration for macOS UI automation"
read_when:
2026-01-30 03:15:10 +01:00
- Hosting PeekabooBridge in OpenClaw.app
2026-01-18 07:47:01 +00:00
- Integrating Peekaboo via Swift Package Manager
2025-12-13 23:02:04 +00:00
- Changing PeekabooBridge protocol/paths
title: "Peekaboo Bridge"
---
2026-01-31 21:13:13 +09:00
2026-01-08 23:06:56 +01:00
# Peekaboo Bridge (macOS UI automation)
2026-01-30 03:15:10 +01:00
OpenClaw can host **PeekabooBridge** as a local, permissionaware UI automation
2026-01-08 23:06:56 +01:00
broker. This lets the `peekaboo` CLI drive UI automation while reusing the
macOS apps TCC permissions.
## What this is (and isnt)
2026-01-30 03:15:10 +01:00
- **Host**: OpenClaw.app can act as a PeekabooBridge host.
- **Client**: use the `peekaboo` CLI (no separate `openclaw ui ...` surface).
- **UI**: visual overlays stay in Peekaboo.app; OpenClaw is a thin broker host.
2026-01-08 23:06:56 +01:00
## Enable the bridge
In the macOS app:
2026-01-31 21:13:13 +09:00
2026-01-08 23:06:56 +01:00
- Settings → **Enable Peekaboo Bridge**
2026-01-30 03:15:10 +01:00
When enabled, OpenClaw starts a local UNIX socket server. If disabled, the host
2026-01-08 23:06:56 +01:00
is stopped and `peekaboo` will fall back to other available hosts.
## Client discovery order
Peekaboo clients typically try hosts in this order:
1. Peekaboo.app (full UX)
2. Claude.app (if installed)
2026-01-30 03:15:10 +01:00
3. OpenClaw.app (thin broker)
2026-01-08 23:06:56 +01:00
Use `peekaboo bridge status --verbose` to see which host is active and which
socket path is in use. You can override with:
```bash
export PEEKABOO_BRIDGE_SOCKET=/path/to/bridge.sock
```
## Security & permissions
2026-01-13 07:15:57 +00:00
- The bridge validates **caller code signatures**; an allowlist of TeamIDs is
2026-01-30 03:15:10 +01:00
enforced (Peekaboo host TeamID + OpenClaw app TeamID).
2026-01-08 23:06:56 +01:00
- Requests time out after ~10 seconds.
- If required permissions are missing, the bridge returns a clear error message
rather than launching System Settings.
## Snapshot behavior (automation)
Snapshots are stored in memory and expire automatically after a short window.
If you need longer retention, recapture from the client.
## Troubleshooting
- If `peekaboo` reports “bridge client is not authorized”, ensure the client is
properly signed or run the host with `PEEKABOO_ALLOW_UNSIGNED_SOCKET_CLIENTS=1`
in **debug** mode only.
2026-01-30 03:15:10 +01:00
- If no hosts are found, open one of the host apps (Peekaboo.app or OpenClaw.app)
2026-01-08 23:06:56 +01:00
and confirm permissions are granted.