Skip to main content
OpenClaw can host PeekabooBridge as a local, permission-aware UI automation broker (PeekabooBridgeHostCoordinator, backed by the steipete/Peekaboo Swift package). This lets the peekaboo CLI drive UI automation while reusing the macOS app’s TCC permissions.

​
What this is (and is not)

  • Host: OpenClaw.app can act as a PeekabooBridge host.
  • Client: the peekaboo CLI (there is no separate openclaw ui ... surface).
  • UI: visual overlays stay in Peekaboo.app; OpenClaw is a thin broker host.

​
Relationship to other desktop-control paths

OpenClaw has three desktop-control paths that intentionally stay separate:
  • PeekabooBridge host: OpenClaw.app hosts the local PeekabooBridge socket. The peekaboo CLI is the client and uses OpenClaw.app’s macOS permissions for screenshots, clicks, menus, dialogs, Dock actions, and window management.
  • Codex Computer Use: the bundled codex plugin checks and can install Codex’s computer-use MCP plugin (extensions/codex/src/app-server/computer-use.ts), then lets Codex own native desktop-control tool calls during Codex-mode turns. OpenClaw does not proxy those actions through PeekabooBridge.
  • Direct cua-driver MCP: OpenClaw can register TryCua’s upstream cua-driver mcp server as a normal MCP server, giving agents the CUA driver’s own schemas and pid/window/element-index workflow without routing through the Codex marketplace or the PeekabooBridge socket.
Use Peekaboo for the broad macOS automation surface via OpenClaw.app’s permission-aware bridge host. Use Codex Computer Use when a Codex-mode agent should rely on Codex’s native plugin. Use direct cua-driver mcp to expose the CUA driver to any OpenClaw-managed runtime as a normal MCP server.

​
Enable the bridge

In the macOS app: Settings -> Enable Peekaboo Bridge. When enabled, OpenClaw starts a local UNIX socket server at ~/Library/Application Support/OpenClaw/<socket-name>. If disabled, the host stops and peekaboo falls back to other available hosts. The coordinator also maintains legacy socket symlinks (clawdbot, clawdis, moltbot under Application Support) pointing at the current socket for older peekaboo installs.

​
Client discovery order

Peekaboo clients typically try hosts in this order:
  1. Peekaboo.app (full UX)
  2. Claude.app (if installed)
  3. OpenClaw.app (thin broker)
Use peekaboo bridge status --verbose to see which host is active and which socket path is in use. Override with: 
export PEEKABOO_BRIDGE_SOCKET=/path/to/bridge.sock

​
Security and permissions

  • The bridge validates caller code signatures; an allowlist of TeamIDs is enforced (Peekaboo host TeamID plus the running app’s own TeamID).
  • Prefer the signed bridge/app identity over a generic node runtime for Accessibility. Granting Accessibility to node lets any package launched by that Node executable inherit GUI automation access; see macOS permissions.
  • Requests time out after 10 seconds (requestTimeoutSec: 10).
  • 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 with a 10-minute validity window and a cap of 50 snapshots (InMemorySnapshotManager); artifacts are not deleted on cleanup. If you need longer retention, re-capture 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.
  • If no hosts are found, open one of the host apps (Peekaboo.app or OpenClaw.app) and confirm permissions are granted.